Fennec/Features/readability: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
(at risk for Firefox 6 or 7, needs to be retargeted) |
||
| Line 8: | Line 8: | ||
<section begin="status" /> | <section begin="status" /> | ||
| [[Fennec/Features/readability|Text Readability]] | | [[Fennec/Features/readability|Text Readability]] | ||
| {{ | | {{StatusAtRisk|status=Needs a team; needs to land early in release cycle}} | ||
| 2011-07-01 | | 2011-07-01 | ||
| Thomas Arend | | Thomas Arend | ||
| Line 17: | Line 17: | ||
Optimize zoom, reflow, and font sizes for best text readability. | Optimize zoom, reflow, and font sizes for best text readability. | ||
== Team | == Team == | ||
== Release Requirements == | == Release Requirements == | ||
== Next Steps == | == Next Steps == | ||
| Line 32: | Line 30: | ||
We need to choose a high-level approach. The table below lists a few that we have considered; there may be other options, or some combination. | We need to choose a high-level approach. The table below lists a few that we have considered; there may be other options, or some combination. | ||
Whichever approach we choose will probably require iteration and tuning, so we should plan to enable it on mozilla-central at the | Whichever approach we choose will probably require iteration and tuning, so we should plan to enable it on mozilla-central at the ''start'' of a development cycle. (This means that if we start development work during the Firefox 6 cycle, we should probably plan on shipping the feature no sooner than the start of the Firefox 7 cycle.) | ||
{| border="1" cellspacing="0" | {| border="1" cellspacing="0" | ||
Revision as of 13:22, 1 May 2011
| Feature | Status | ETA | Owner |
| Text Readability | Needs a team; needs to land early in release cycle | 2011-07-01 | Thomas Arend |
Summary
Optimize zoom, reflow, and font sizes for best text readability.
Team
Release Requirements
Next Steps
- UX direction on high-level approach (see below).
- Need an owner, implementation plan, and estimates for chosen approach.
Open Issues
We need to choose a high-level approach. The table below lists a few that we have considered; there may be other options, or some combination.
Whichever approach we choose will probably require iteration and tuning, so we should plan to enable it on mozilla-central at the start of a development cycle. (This means that if we start development work during the Firefox 6 cycle, we should probably plan on shipping the feature no sooner than the start of the Firefox 7 cycle.)
| Approach | Pros | Cons |
|---|---|---|
| Fennec 4.0 style - On double tap, change minimum font size based on width of tapped element (bug 611555). |
|
|
| Android style - On zoom, re-wrap text based on the zoom level (bug 578179). |
|
|
| iPhone style - Set a minimum font size per element based on its text width (bug 627842). |
|
|
Related Bugs & Dependencies
- bug 578179 - Option to wrap text to screen width rather than container width
- bug 611555 - should reflow on zoom [see dependencies for related bugs]
- bug 627842 - Allow minimum font size based on size of frame
- bug 598736 - Use higher-quality image scaling. (Affects readability of text in IMG elements.)
Designs
Test Plans
Goals/Use Cases
Non-Goals
Other Documentation
Legend (remove if you like)
| Healthy: feature is progressing as expected. | |
| Blocked: feature is currently blocked. | |
| At Risk: feature is at risk of missing its targeted release. | |
| ETA | Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date. |