Fennec/Features/visualrefresh: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 44: Line 44:
** {{bug|641906}} - Use system theme colors in nsLookAndFeel on Android
** {{bug|641906}} - Use system theme colors in nsLookAndFeel on Android
* Design changes
* Design changes
** {{bug|653134}} - Create Fennec Gingerbread theme
** {{bug|653136}} - Create Fennec Honeycomb theme


== Designs ==
== Designs ==

Revision as of 15:53, 27 April 2011

Feature Status ETA Owner
Visual Refresh (Gingerbread, Honeycomb) Concept YYYY-MM-DD Owner Name

Summary

Succinct summary of what this feature is all about.

Team

Who's working on this?

  • Feature Manager: tbd
  • Lead Developer:
  • Product Manager:
  • QA:
  • UX: Ian Barlow
  • Security:


Release Requirements

Complete checklist of items that need to be satisfied before we can call this feature "done".

Next Steps

  • Assemble a "widget sheet" for froyo/gingerbread/honeycomb -- visuals only is fine

Open Issues

Unanswered questions, things that need to be explored, decisions that still need to be made, etc. Again, including the name of who's responsible for each item can be useful.

Related Bugs & Dependencies

  • Infrastructural changes
    • bug 650388 - Add media queries to support styling various Android themes
    • bug 649820 - Change browser CSS based on Android OS version
    • bug 641906 - Use system theme colors in nsLookAndFeel on Android
  • Design changes

Designs

Any and all mockups, design specs, tech specs, etc. Either inline or linked to.

Use Cases

Test Plans

Any and all test plans and strategies. Either inline or linked to.

Goals

Non-Goals

Things we are specifically not doing or building as part of this feature.

Other Documentation

Can include things like:

  • Competitive landscape
  • Research & references
  • Whatever else is useful to the project.

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.