{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/wcag21/issues/77","repository_url":"https://api.github.com/repos/w3c/wcag21","labels_url":"https://api.github.com/repos/w3c/wcag21/issues/77/labels{/name}","comments_url":"https://api.github.com/repos/w3c/wcag21/issues/77/comments","events_url":"https://api.github.com/repos/w3c/wcag21/issues/77/events","html_url":"https://github.com/w3c/wcag21/issues/77","id":192957384,"number":77,"title":"Resize Content","user":{"login":"allanj-uaag","id":7329327,"avatar_url":"https://avatars.githubusercontent.com/u/7329327?v=3","gravatar_id":"","url":"https://api.github.com/users/allanj-uaag","html_url":"https://github.com/allanj-uaag","followers_url":"https://api.github.com/users/allanj-uaag/followers","following_url":"https://api.github.com/users/allanj-uaag/following{/other_user}","gists_url":"https://api.github.com/users/allanj-uaag/gists{/gist_id}","starred_url":"https://api.github.com/users/allanj-uaag/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/allanj-uaag/subscriptions","organizations_url":"https://api.github.com/users/allanj-uaag/orgs","repos_url":"https://api.github.com/users/allanj-uaag/repos","events_url":"https://api.github.com/users/allanj-uaag/events{/privacy}","received_events_url":"https://api.github.com/users/allanj-uaag/received_events","type":"User","site_admin":false},"labels":[{"id":443163710,"url":"https://api.github.com/repos/w3c/wcag21/labels/LVTF","name":"LVTF","color":"f9d0c4","default":false},{"id":412540552,"url":"https://api.github.com/repos/w3c/wcag21/labels/Ready%20for%20WG%20Review","name":"Ready for WG Review","color":"128A0C","default":false}],"state":"open","locked":false,"assignee":{"login":"alastc","id":216630,"avatar_url":"https://avatars.githubusercontent.com/u/216630?v=3","gravatar_id":"","url":"https://api.github.com/users/alastc","html_url":"https://github.com/alastc","followers_url":"https://api.github.com/users/alastc/followers","following_url":"https://api.github.com/users/alastc/following{/other_user}","gists_url":"https://api.github.com/users/alastc/gists{/gist_id}","starred_url":"https://api.github.com/users/alastc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alastc/subscriptions","organizations_url":"https://api.github.com/users/alastc/orgs","repos_url":"https://api.github.com/users/alastc/repos","events_url":"https://api.github.com/users/alastc/events{/privacy}","received_events_url":"https://api.github.com/users/alastc/received_events","type":"User","site_admin":false},"assignees":[{"login":"alastc","id":216630,"avatar_url":"https://avatars.githubusercontent.com/u/216630?v=3","gravatar_id":"","url":"https://api.github.com/users/alastc","html_url":"https://github.com/alastc","followers_url":"https://api.github.com/users/alastc/followers","following_url":"https://api.github.com/users/alastc/following{/other_user}","gists_url":"https://api.github.com/users/alastc/gists{/gist_id}","starred_url":"https://api.github.com/users/alastc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alastc/subscriptions","organizations_url":"https://api.github.com/users/alastc/orgs","repos_url":"https://api.github.com/users/alastc/repos","events_url":"https://api.github.com/users/alastc/events{/privacy}","received_events_url":"https://api.github.com/users/alastc/received_events","type":"User","site_admin":false}],"milestone":null,"comments":25,"created_at":"2016-12-01T20:44:17Z","updated_at":"2017-01-23T13:37:27Z","closed_at":null,"body":"<h2>SC Shortname</h2>\r\n<p>Resize content </p>\r\n<p> (Was: \"Size (all content)\", but trying to align and extend 1.4.4 Resize text.) </p>\r\n<h2>SC Text</h2>\r\n<p>The content of the Web page can be increased to 400% without loss of content or functionality, without two dimensional scrolling, with following the exceptions: </p>\r\n<ol>\r\n  <li>If the spatial layout of some the content is essential to that contents use, that part of the content is exempt.</li>\r\n  <li> If the user-agent fits the layout to the viewport and does not provide a means of reflowing content, two dimensional scrolling is exempt. </li>\r\n</ol>\r\n<h2>Suggested Priority Level</h2>\r\n<p>Level A </p>\r\n<h2>Related Glossary additions or changes</h2>\r\n<p>None. </p>\r\n<h2>What Principle and Guideline the SC falls within.</h2>\r\n<p>Principle 1, Guideline <a href=\"https://www.w3.org/TR/WCAG20/#visual-audio-contrast-scale\"> 1.4.4 Resize text</a> </p>\r\n<h2>Description</h2>\r\n<p>Zoom functions preserve all spatial relationships on the page and all functionality continues to be available. \r\n  \r\n  Simply put: a person can make everything bigger or smaller as  needed.\r\n  \r\n  If the user needs to increase content more than 400%, then <a href=\"https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Reflow_to_Single_Column\"> reflow</a> would be necessary. </p>\r\n<h2>Benefits</h2>\r\n<blockquote> Some people need to increase the size of all interface content in order to perceive information. Although increasing size is most common, some people with tunnel vision and good visual acuity may prefer to decrease the size so they can see more information at a time.\r\n  \r\n  Source: <a href=\"http://w3c.github.io/low-vision-a11y-tf/requirements.html#size-of-all-elements\"> Accessibility Requirements for People with Low Vision, Section 3.3.5: Size of All Content</a> </blockquote>\r\n<h2>Testability</h2>\r\n<ol>\r\n  <li> Display content in a user agent.</li>\r\n  <li>Increase zoom to 400% </li>\r\n  <li> Check whether all content scales and is perceivable with no loss of content or functionality (e.g. boxes do not overlap, controls are not obscured or separated from their labels, etc.). </li>\r\n  <li> If horizontal scrolling is present, check that the content would not make sense without the scrolling. </li>\r\n</ol>\r\n<h4>Expected Results </h4>\r\n<ul>\r\n  <li> Check # 3 is true. </li>\r\n  <li> Check # 4 is true. </li>\r\n</ul>\r\n<h2>Techniques</h2>\r\n<h4>All existing techniques for Proposed New SC: \"Size (all content)\"\r\n  </h3>\r\n</h4>\r\n<ol>\r\n  <li><a href=\"https://www.w3.org/TR/WCAG20-TECHS/G146\"> G146: Using liquid layout</a> and ''AND'' using measurements that are relative to other measurements in the content by using one or more of the following techniques:\r\n    <ul>\r\n      <li><a href=\"https://www.w3.org/TR/WCAG20-TECHS/C12 https://www.w3.org/TR/WCAG20-TECHS/C12\"> C12: Using percent for font sizes (CSS)</a> OR </li>\r\n      <li><a href=\"https://www.w3.org/TR/WCAG20-TECHS/C13\"> C13: Using named font sizes (CSS)</a> OR </li>\r\n      <li><a href=\"https://www.w3.org/TR/WCAG20-TECHS/C14\"> C14: Using em units for font sizes (CSS)</a> OR </li>\r\n      <li><a href=\"https://www.w3.org/TR/WCAG20-TECHS/C24\"> C24: Using percentage values in CSS for container sizes (CSS)</a> OR </li>\r\n      <li><a href=\"https://www.w3.org/TR/WCAG20-TECHS/FLASH33\"> FLASH33: Using relative values for Flash object dimensions (Flash)</a> </li>\r\n      <li><a href=\"https://www.w3.org/TR/WCAG20-TECHS/SCR34\"> SCR34: Calculating size and position in a way that scales with text size (Scripting)</a> OR </li>\r\n    </ul>\r\n  </li>\r\n  <li><a href=\"https://www.w3.org/TR/WCAG20-TECHS/G206\"> G206: Providing options within the content to switch to a layout that does not require the user to scroll horizontally to read a line of text</a> </li>\r\n</ol>\r\n<h4>New Techniques</h4>\r\n<ol>\r\n  <li> Using fluid grids. Ref: <a href=\"http://alistapart.com/article/fluidgrids\"> fluid grids</a> </li>\r\n  <li> Using em based media queries. Ref: <a href=\"http://blog.cloudfour.com/the-ems-have-it-proportional-media-queries-ftw/\"> em based media queries</a> </li>\r\n  <li> Using responsive images. Ref:  HTML <a href=\"https://w3c.github.io/html/semantics-embedded-content.html#the-picture-element\"> picture element</a> and <a href=\"https://w3c.github.io/html/semantics-embedded-content.html#ref-for-element-attrdef-img-srcset-1\"> srcset attribute</a> </li>\r\n  <li> @@ Consider a failure technique on fixed sized containers and fixed position content?? </li>\r\n  <li> @@ Consider a failure technique on \"Interfering with a user agent's ability to zoom\" i.e., author using: maximum-scale or minimum-scale or user-scalable=no or user-scalable=0 in the meta element ?? @@ Note: In <a href=\"https://lists.w3.org/Archives/Public/w3c-wai-gl/2016AprJun/0502.html\"> Pinch zoom thread on the WCAG list</a> people did not seem to be in favor of this as a failure.</li>\r\n  <li> @@ (HTML) Consider failure for preformatted text or excluding this as an exception to no two dimensional scrolling. </li>\r\n</ol>\r\n<h2>Related Information</h2>\r\n<h3>Actions</h3>\r\n<ul>\r\n  <li> <a href=\"https://www.w3.org/WAI/GL/low-vision-a11y-tf/track/actions/73\"> ACTION-73: Write sc - size of all elements</a> - on Laura Carlson, August 25, 2016 </li>\r\n  <li><a href=\"https://www.w3.org/WAI/GL/low-vision-a11y-tf/track/actions/82\"> ACTION-82: Update user needs/requirements with change size of all elements->content</a> - on Shawn Henry, September 1, 2016 </li>\r\n</ul>\r\n<h3>Articles</h3>\r\n<h4>Zoom Articles</h4>\r\n<ul>\r\n  <li> <a href=\"http://adrianroselli.com/2015/10/dont-disable-zoom.html\"> Don't Disable Zoom</a> - Adrian Roselli </li>\r\n  <li> <a href=\"http://jkg3.com/Journal/don-t-disable-pinch-to-zoom\"> Don't disable pinch to zoom</a> - Jamie Knight </li>\r\n  <li> <a href=\"http://stackoverflow.com/questions/6397748/whats-the-point-of-meta-viewport-user-scalable-no-in-the-google-maps-api\"> What's the point of 'meta viewport user-scalable=no' in the Google Maps API</a> - Stack Overflow </li>\r\n  <li> <a href=\"http://alastairc.ac/2013/08/browser-zoom-great-for-accessibility/\"> Browser zoom great for accessibility</a> - Alastair Campbell</li>\r\n  <li> <a href=\"https://alastairc.ac/2015/10/zoom-for-fixed-and-responsive-sites/\"> Zoom for Fixed and Responsive Sites</a> - Alastair Campbell </li>\r\n  <li> <a href=\"http://www.slideshare.net Why Browser Zoom Sucks for Low Vision Users (slide deck)</a> Denis Boudreau</li>\r\n  <li>  <a href=\"https://blog.codinghorror.com/the-two-types-of-browser-zoom/\"> The Two Types of Browser Zoom</a> - Jeff Atwood </li>\r\n</ul>\r\n<h4>Responsive Images Articles</h4>\r\n<ul>\r\n  <li> <a href=\"http://www.html5rocks.com/en/tutorials/responsive/picture-element/\"> Built-in Browser Support for Responsive Images</a> - Pearl Chen </li>\r\n  <li> <a href=\"http://www.ssbbartgroup.com/blog/what-does-responsive-web-design-have-to-do-with-accessibility/\"> What Does Responsive Web Design Have to Do with Accessibility?</a> - Jonathan Avila </li>\r\n  <li> <a href=\"http://www.brucelawson.co.uk/2012/responsive-web-design-preserving-images-aspect-ratio/\"> Responsive Web Design: Preserving Images' Aspect Ratio</a> - Bruce Lawson</li>\r\n  <li> <a href=\"https://www.youtube.com/watch?v=bPwTnc-pwps\"> Bruce Lawson picture and friends HTML responsive images (Video)</a> - Bruce Lawson </li>\r\n  <li> <a href=\"https://www.sitepoint.com/improving-responsive-images-picture-element/\"> Improving Responsive Images with the Picture Element</a> - Annarita Tranfici</li>\r\n  <li> <a href=\"https://www.smashingmagazine.com/2014/05/responsive-images-done-right-guide-picture-srcset/\"> Responsive Images Done Right: A Guide To\r\n    <picture>\r\n    And srcset</a> - Eric Portis </li>\r\n  <li> <a href=\"http://alistapart.com/blog/post/bringing-responsive-images-to-browsers\"> Bringing Responsive Images to Browsers</a> - Mat Marquis </li>\r\n</ul>\r\n<h3>Email</h3>\r\n<ul>\r\n  <li> <a href=\"https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2016Oct/thread.html#msg47\"> Resize Content, Size of All Interface and Resize Text. (Thread)</a> - Wayne Dick, 18 October  2016 </li>\r\n  <li><a href=\"https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2016Oct/0035.html\"> Sizing SCs - post informal meeting</a> - Alastair Campbell, 6 October 2016 </li>\r\n  <li><a href=\"https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2016Oct/thread.html#msg1\"> Combining the sizing SCs Thread</a> - Alastair Campbell, 3 October 2016 </li>\r\n  <li><a href=\"https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2016Oct/thread.html#msg15\"> Re: Combining SCs Thread</a> - Alastair Campbell, 3 October 2016</li>\r\n  <li> <a href=\"https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2016Oct/thread.html#msg1\">3 Re: Sizing SCs Thread</a> - Alastair Campbell, 3 October 2016 </li>\r\n  <li> <a href=\"https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2016Aug/0038.html\"> lvtf-ACTION-73: Write SC - size of all elements</a> - LVTF List </li>\r\n  <li> <a href=\"https://lists.w3.org/Archives/Public/w3c-wai-gl/2016JulSep/0006.html\"> Thread: Jonathan's concern: Zoom in responsive drops content</a> - WCAG WG List </li>\r\n  <li> <a href=\"https://lists.w3.org/Archives/Public/w3c-wai-gl/2015JanMar/0041.html\"> Thread: Enabling Zoom on Mobile Devices</a> - WCAG WG List </li>\r\n  <li> <a href=\"https://lists.w3.org/Archives/Public/w3c-wai-gl/2016AprJun/0502.html\"> Thread: Pinch zoom</a> - WCAG WG List <a href=\"http://webaim.org/discussion/mail_thread?thread=7336 Thread: Any official clarification on Text-only zoom and RWD?</a> - WebAIM</li>\r\n  <li>  <a href=\"http://webaim.org/discussion/mail_thread?thread=7004\"> Thread: Browser zooming sufficient for WCAG 1.4.4 (resize text)</a> - WebAIM </li>\r\n</ul>\r\n<h3>GitHub</h3>\r\n<ul>\r\n  <li> <a href=\"https://github.com/w3c/wcag21/issues/12\"> Size (all content) (LV) #12</a> - WCAG Github Issue 12, Raised by Jim Allan, September 15 2016 </li>\r\n  <li> <a href=\"https://github.com/w3c/low-vision-SC/issues/5\"> WCAG 1.4.8 item 5 200%</a> Raised by Jim Allan, 16 June 2016 </li>\r\n  <li> <a href=\"https://github.com/w3c/wai-tutorials/issues/293\">Reference to 200% zoom implies WCAG requires text zoom only</a> - WAI Tutorial GitHub Issue 293,  raised by David MacDonald, 31 March 2015 </li>\r\n  <li> <a href=\"https://github.com/w3c/html/issues/602\"> Proposal: devs SHOULD NOT use content=\"user-scalable=no | maximum-scale=1.0 \" on meta</a> HTML WG GitHub Issue 602,  raised by Steve Faulkner, 28 September 2016 </li>\r\n</ul>\r\n<h3>Minutes</h3>\r\n<ul>\r\n  <li> <a href=\"https://www.w3.org/2016/12/01-lvtf-minutes.html#item05\"> 1 December 2016 LVTF Minutes</a> </li>\r\n  <li> <a href=\"https://www.w3.org/2016/10/13-lvtf-minutes.html\"> 13 October 2016 LVTF Minutes</a> </li>\r\n  <li> <a href=\"https://www.w3.org/2016/09/29-lvtf-minutes.html\"> 06 October 2016 LVTF Minutes (Informal Meeting)</a> </li>\r\n  <li> <a href=\"https://www.w3.org/2016/09/29-lvtf-minutes.htm\">l 29 September 2016 LVTF Minutes </a> </li>\r\n  <li> <a href=\"https://www.w3.org/2016/09/15-lvtf-minutes.html#item04\"> 15 September 2016 LVTF Minutes</a> </li>\r\n  <li> <a href=\"https://www.w3.org/2016/09/01-lvtf-minutes.html#item05\"> 01 September 2016 LVTF Minutes</a> </li>\r\n  <li> <a href=\"https://www.w3.org/2016/07/14-lvtf-minutes.html#item01\"> 14 Jul 2016 LVTF Minutes </a> </li>\r\n  <li> <a href=\"https://www.w3.org/2016/05/12-lvtf-minutes.html#resolution01\"> 2 May 2016 LVTF Minutes 1</a> <a href=\"https://www.w3.org/2016/01/20-lvtf-minutes.html#item01\"> 20 Jan 2016 LVTF Minutes</a> </li>\r\n</ul>\r\n<h3>Resolutions</h3>\r\n<ul>\r\n  <li> <a href=\"https://www.w3.org/2016/12/01-lvtf-minutes.html#resolution04\"> Ready for WCAG</a> - 1 December 2016 </li>\r\n</ul>\r\n<h3>Tools</h3>\r\n<ul>\r\n  <li> <a href=\"https://addons.mozilla.org/en-US/android/addon/always-zoom/\"> Always Zoom</a> - Matt Brubeck </li>\r\n  <li><a href=\"https://chrome.google.com/webstore/detail/zoom/lajondecmobodlejlcjllhojikagldgd?hl=en\"> Zoom - Chrome Extension</a> </li>\r\n  <li><a href=\"https://chrome.google.com/webstore/detail/zoomwheel/kdfgigbjonaniokmpfflpflkhahhbaej?hl=en\"> zoomWheel</a> - Chrome Web Store </li>\r\n  <li><a href=\"https://support.google.com/chrome/answer/96810?hl=en\"> Change text, image, and video sizes (zoom)</a> - Chrome Help </li>\r\n  <li><a href=\"https://support.mozilla.org/en-US/kb/font-size-and-zoom-increase-size-of-web-pages\"> Font size and zoom - increase the size of web pages (Firefox)</a> - Mozilla Support </li>\r\n</ul>\r\n<h3>TPAC 2016</h3>\r\n<ul>\r\n  <li> <a href=\"https://www.w3.org/2016/09/19-wai-wcag-minutes.html\"> TPAC Minutes</a> - September 19, 2016\r\n    <ul>\r\n      <li> Jim: https://github.com/w3c/wcag21/issues/12 </li>\r\n      <li> Jim: Size of all content. </li>\r\n      <li> Kathy: This is required up to 200% </li>\r\n      <li> laura: Look at the test:\r\n        <ul>\r\n          <li> laura: 1. Display content in a user agent. </li>\r\n          <li> laura: 2. Increase zoom to the maximum. </li>\r\n          <li> laura: 3. Decrease zoom to the minimum. </li>\r\n          <li> laura: 4. Check whether all content scales and is perceivable with no loss of content or functionality (e.g. boxes do not overlap, controls are not obscured or separated from their labels, etc.).</li>\r\n        </ul>\r\n      </li>\r\n      <li> Jim: Wanted to elevate the importance, and add a bullet point. </li>\r\n      <li> MichaelC, you wanted to worry about intersection with layout wrt small viewport issues etc.</li>\r\n      <li> MichaelC: Wonder if we can realistically that say you can resize everything, whilst not clipping.</li>\r\n      <li> AC: I'd urge everyone to look at the work David and I did, and expansion of 1.4.4</li>\r\n      <li> Joshue, you wanted to say this sounds like truly responsive design.</li>\r\n      <li> Jim: AC to you have a link to the expansion of 1.4.4</li>\r\n      <li> Josh: Not sure of the difference between that and some of the others. There are a lot of variables, spacial relationships can be temporary.</li>\r\n      <li> JF: It says that we're adding a new bullet to something that is about blocks of text (only). Also, going from triple-A to A would get serious pushback.</li>\r\n      <li> AC: I'd say the change to 1.4.4 would change that too. </li>\r\n      <li> JF: Maybe it needs to be a new guideline or a new SC. </li>\r\n      <li> Kathy: Researching for the mobile work, something that came out was that there are differences in content. Reading on a smaller screen (paragraphs) wanted to increase text size, but not the menus. Magnify when needed. Be careful that we write or change, there are differences in the content. Users with low vision have done videos on youtube.</li>\r\n      <li> AC: Just to add, when David and I worked on the Zooming SC, it is a noticable hole how this is handled</li>\r\n      <li> AC: You cant in a page do the same things on a web page and a mobile device. </li>\r\n      <li> KW: Depends on how media queries are set up. </li>\r\n    </ul>\r\n  </li>\r\n  <li> <a href=\"https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2016Sep/0062.html\"> Jim's TPAC notes</a> - 27 September 2016\r\n    <ol>\r\n   <li>   seems more like 1.4.4.</li> \r\n      <li> worry about browser capability.</li>\r\n      <li> SC wording does not reflect the description - Zoom functions preserve all spatial relationships on the page and all functionality continues to be available. </li>\r\n      <li> perhaps making content truly responsive - tho this seems a technique.</li>\r\n        <li>zooming images is not in 1.4.8</li>\r\n      <li> AAA to A is too big of a jump.</li>\r\n       <li> may need a new guideline or SC to expand these concepts </li>\r\n      <li> different user preferences depending on what part of content they were interacting with. May only want 1 part of content magnified. have to be careful of very broad SC. User needs - user experience, different size screens. Text size vs zoom ... all are variable depending on situation. SCs apply to all situations. </li>\r\n      <li> youtube videos of lowvision folks explaining issues - useful research.</li>\r\n      <li> 1 px fonts. stroke width to color contrast ratio. </li>\r\n    </ol>\r\n  </li>\r\n</ul>\r\n<h3>Wiki Pages</h3>\r\n<ul>\r\n  <li> <a href=\"https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/User_stories_-_use_cases#Size_Limitations\"> Use cases</a> - LVTF Wiki </li>\r\n  <li> <a href=\"https://www.w3.org/WAI/GL/wiki/Possible_wording_from_Jason/David_for_LVTF_re:_zoom_without_horizontal_scroll\"> Possible wording from Jason/David for LVTF re: zoom without horizontal scroll</a> - WCAG WG Wiki </li>\r\n  <li> <a href=\"http://www.infovis-wiki.net/index.php?title=Semantic_Zoom\"> Semantic Zoom</a> - InfoVis Wiki </li>\r\n  <li> <a href=\"http://www.infovis-wiki.net/index.php?title=Zoom\"> Zoom</a> - InfoVis Wiki </li>\r\n</ul>\r\n"},"comment":{"url":"https://api.github.com/repos/w3c/wcag21/issues/comments/274489550","html_url":"https://github.com/w3c/wcag21/issues/77#issuecomment-274489550","issue_url":"https://api.github.com/repos/w3c/wcag21/issues/77","id":274489550,"user":{"login":"detlevhfischer","id":9989439,"avatar_url":"https://avatars.githubusercontent.com/u/9989439?v=3","gravatar_id":"","url":"https://api.github.com/users/detlevhfischer","html_url":"https://github.com/detlevhfischer","followers_url":"https://api.github.com/users/detlevhfischer/followers","following_url":"https://api.github.com/users/detlevhfischer/following{/other_user}","gists_url":"https://api.github.com/users/detlevhfischer/gists{/gist_id}","starred_url":"https://api.github.com/users/detlevhfischer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/detlevhfischer/subscriptions","organizations_url":"https://api.github.com/users/detlevhfischer/orgs","repos_url":"https://api.github.com/users/detlevhfischer/repos","events_url":"https://api.github.com/users/detlevhfischer/events{/privacy}","received_events_url":"https://api.github.com/users/detlevhfischer/received_events","type":"User","site_admin":false},"created_at":"2017-01-23T13:37:26Z","updated_at":"2017-01-23T13:37:26Z","body":"@alastc \r\n> > \"...there are situations where LV users indeed shrink rather than increase content - so to cover those cases, resize seems more neutral.\"\r\n>  \"That is true, but not to 400%.\"\r\n\r\n400% is just an upper limit, and the need may rarely arise to size down (more modestly). That's why I still think _resize_ is the better (more generic) term, even though in most cases it is indeed = _increase_. But I'll leave it at that.\r\n\r\n>  \"Would it be ok to outline that in the understanding?\" \r\n\r\nYes, fine!"}}
{"actor":{"display_login":"detlevhfischer"}}