Platform/Features/Input Number: Difference between revisions
Jump to navigation
Jump to search
(→Related Bugs & Dependencies: bug number was wrong) |
m (there is no such thing as june 31st) |
||
Line 9: | Line 9: | ||
| <input type='number'> | | <input type='number'> | ||
| {{StatusHealthy|status=Content patches wrote and mostly reviewed. Layout patches TBD.}} | | {{StatusHealthy|status=Content patches wrote and mostly reviewed. Layout patches TBD.}} | ||
| 2011-06- | | 2011-06-30 | ||
| Mounir Lamouri | | Mounir Lamouri | ||
<section end="status" /> | <section end="status" /> |
Revision as of 17:09, 20 April 2011
Feature | Status | ETA | Owner |
<input type='number'> | Content patches wrote and mostly reviewed. Layout patches TBD. | 2011-06-30 | Mounir Lamouri |
Summary
Implementation of <input type='number'>, a form field to select a number.
See http://www.whatwg.org/specs/web-apps/current-work/multipage/number-state.html#number-state
Team
- Feature Manager: Mounir Lamouri
- Developer: Mounir Lamouri
- Product Manager:
- UX: Alexander Limi
- Accessibility: David Bolter
Release Requirements
- Follow specifications (except if on purpose)
- Have a decent native and localized 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
- Improve UX
- Localization/Internationalization
- Make sure the element is accessible
Open Issues
- Few specifications details (Mounir Lamouri)
- User eXperience details (there are currently no plans) (Alexander Limi)
- Accessibility plans (David Bolter)
Related Bugs & Dependencies
Feature tracking bug: bug 344616
Designs
HTML spec: http://www.whatwg.org/specs/web-apps/current-work/multipage/number-state.html#number-state
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.
Non-Goals
We do not want to have the ideal implementation especially for the UX. This could be improved later.