Mobile/Archive/Reflow on zoom: Difference between revisions

Mobile/Archive/Reflow on zoom (view source)

Revision as of 17:07, 21 July 2010

7 bytes removed , 21 July 2010

→‎Summary

Madhava

Confirmed users

1,492

edits

@@ Line 6: / Line 6: @@
 * easier zooming (pinching) will help with the subset of readability problems that are just due to getting the right zoom-level
 * in many (most?) cases, though, the problem is with the design/layout of webpages themselves - they do not become easier to read through simple magnification, because by the time the text is big enough, the column of text is wider than the viewport.  As a result, all solutions (that I know of) to the readability problem require "adapting" the page design intended by the site author.  Three variants are:
+# Android-style text reflow.  Ben and Brad have a prototype of this in an add-on called Easy Reading.  Last I checked, it would reflow on zooming in but not back to the original when zooming out;  Ben and Brad - has this come further?  We'd talked about prototyping this as a feature in the add-on.  Pros for this approach: it definitely makes reader easier, and android users are used to it.  Cons: it changes a web-author's intended page layout (though, as I mentioned, I think that any solution to this problem is going to require this to some degree). Because of this last bit, it's controversial, but I think we should try it.
-## Android-style text reflow.  Ben and Brad have a prototype of this in an add-on called Easy Reading.  Last I checked, it would reflow on zooming in but not back to the original when zooming out;  Ben and Brad - has this come further?  We'd talked about prototyping this as a feature in the add-on.  Pros for this approach: it definitely makes reader easier, and android users are used to it.  Cons: it changes a web-author's intended page layout (though, as I mentioned, I think that any solution to this problem is going to require this to some degree). Because of this last bit, it's controversial, but I think we should try it.
+# Full-on page layout replacement, like Fabrice's Readability add-on.  This works really well, but it's too invasive to be our standard "make the page basically readable" functionality.  It's a great additional feature to have, either as an add-on or built-in.
+# Being clever with size of type.  We haven't explored the details of this very much, but we should start.  What I mean by this is increasing the size of type when we can tell that it would be most useful, but not doing it when it would just really break the overall layout.  For example, we might use a default smaller size when fully zoomed out, but use a larger size when the user zooms in to read an article; or have a minimum fontsize when the current element is 100% of the width of the webpage.  In a sense, this is trying to get at the advantages of the android model without the obvious changes in layout.
-## Full-on page layout replacement, like Fabrice's Readability add-on.  This works really well, but it's too invasive to be our standard "make the page basically readable" functionality.  It's a great additional feature to have, either as an add-on or built-in.
-## Being clever with size of type.  We haven't explored the details of this very much, but we should start.  What I mean by this is increasing the size of type when we can tell that it would be most useful, but not doing it when it would just really break the overall layout.  For example, we might use a default smaller size when fully zoomed out, but use a larger size when the user zooms in to read an article; or have a minimum fontsize when the current element is 100% of the width of the webpage.  In a sense, this is trying to get at the advantages of the android model without the obvious changes in layout.
 == Current Status ==