Platform/Features/Progress Element: Difference between revisions
Jump to navigation
Jump to search
(create page) |
(be clear that patches are reviewed) |
||
| Line 8: | Line 8: | ||
<section begin="status" /> | <section begin="status" /> | ||
| <progress> | | <progress> | ||
| {{StatusHealthy|status=Patches ready except vertical progress bars.}} | | {{StatusHealthy|status=Patches ready and reviewed except vertical progress bars.}} | ||
| 2011-05-30 | | 2011-05-30 | ||
| Mounir Lamouri | | Mounir Lamouri | ||
Revision as of 14:53, 6 May 2011
| Feature | Status | ETA | Owner |
| <progress> | Patches ready and reviewed except vertical progress bars. | 2011-05-30 | Mounir Lamouri |
Summary
Implementation of the <progress> element, a form widget to show a progression.
Team
Who's working on this?
Team
- Feature Manager: Mounir Lamouri
- Developer: Mounir Lamouri
- Product Manager:
- Accessibility: David Bolter
Release Requirements
- Follow specifications (except if on purpose)
- Have a good native UI
- Being able to style the element
- Accessible
Steps
- Review specifications
- Implement the content part
- Implement the layout part
- Use native style on GTK (GNU/Linux), MacOS X and Windows (XP to 7)
- Author styling
- Make sure the element is accessible
- Implement the vertical progress bar (layout + native style)
- Nice default UI
Open Issues
- Accessibility plans (bug 559773) (David Bolter)
- What to do with vertical progress bars? Should we have this to ship? (bug 638540) (Mounir Lamouri)
- Should we ship with a nice default UI (when non-native)? (bug 644361) (Mounir Lamouri)
Designs
Test Plans
- Conformance tests (against specs)
- Rendering tests for layout
- Trying to have all bits of the patches tested
Goals
Have an implementation that can be used by authors as soon as it is released.