Confirmed users
2,023
edits
Fennec/Features/readability: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 71: | Line 71: | ||
So, the approach is to: | So, the approach is to: | ||
# On page load, inflate the font size of the "body" part of the page. As on iOS, this requires some heuristics so that areas of the page where font inflation would break the page layout (anything in a table, sidebar areas, etc.) do not get inflated. The inflation that does take place should increase the body font size such that, when that area is zoomed to fit by pinch-zooming, the font is at a good baseline readable size. This size may not be quite as large as our optimal size. | # On page load, inflate the font size of the "body" part of the page. As on iOS, this requires some heuristics so that areas of the page where font inflation would break the page layout (anything in a table, sidebar areas, etc.) do not get inflated. The inflation that does take place should increase the body font size such that, when that area is zoomed to fit by pinch-zooming, the font is at a good baseline readable size. This size may not be quite as large as our optimal size. | ||
# On double-tap of a particular area, the browser should further inflate the font size of that particular area if necessary to get to our optimal reading size. I think (someone correct me) that this involves some reflow. This would not happen on pinch zoom -- just on doubletap, because then we know exactly what block a user is trying to read. | # If step 1 does not get us to where we want to be, we will pursue step 2 which will apply a more aggressive metric on double tap | ||
# Zooming back out, either by double-tap or pinch, would return the page to its initial font-inflated state (i.e. what the page looked like on load) | ## On double-tap of a particular area, the browser should further inflate the font size of that particular area if necessary to get to our optimal reading size. I think (someone correct me) that this involves some reflow. This would not happen on pinch zoom -- just on doubletap, because then we know exactly what block a user is trying to read. | ||
# Double-tap zooming to a further-in nested area would further apply the aggressive inflation to that area to ensure its readability | ## Zooming back out, either by double-tap or pinch, would return the page to its initial font-inflated state (i.e. what the page looked like on load) | ||
## Double-tap zooming to a further-in nested area would further apply the aggressive inflation to that area to ensure its readability | |||