Platform/Features/Input Number
From MozillaWiki
Please use "Edit with form" above to edit this page.
Status
| <input type='number'> | |
| Stage | On hold |
| Status | In progress |
| Release target | Undetermined |
| Health | Blocked |
| Status note | Content patches wrote and mostly reviewed. Layout patches TBD. On hold until I find some free cycles to get back to it. |
Team
| Product manager | Chris Blizzard |
| Directly Responsible Individual | Mounir Lamouri |
| Lead engineer | Mounir Lamouri |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | David Bolter |
| QA lead | Simona Badau |
| UX lead | Alex Limi |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
Open issues/risks
- Few specifications details (Mounir Lamouri)
- User eXperience details (there are currently no plans) (Alexander Limi)
- Accessibility plans (bug 559761) (David Bolter)
Stage 1: Definition
1. Feature overview
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
Goals: Have an implementation that can be used by authors as soon as it is released.
2. Users & use cases
`
3. Dependencies
`
4. Requirements
- Follow specifications (except if on purpose)
- Have a decent native and localized UI
- Being able to style the element
- Accessible
Non-goals
We do not want to have the ideal implementation especially for the UX. This could be improved later.
Stage 2: Design
5. Functional specification
HTML spec: http://www.whatwg.org/specs/web-apps/current-work/multipage/number-state.html#number-state
6. User experience design
`
Stage 3: Planning
7. Implementation plan
`
8. Reviews
Security review
`
Privacy review
`
Localization review
`
Accessibility
`
Quality Assurance review
- Conformance tests (against specs)
- Rendering tests for layout
- Trying to have all bits of the patches tested
Operations review
`
Stage 4: Development
9. Implementation
- Feature tracking bug: bug 344616
Stage 5: Release
10. Landing criteria
`
Feature details
| Priority | P3 |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | Platform |
| Secondary roadmap | ` |
| Feature list | Platform |
| Project | ` |
| Engineering team | DOM |
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | sec-review-unnecessary | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | ` |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
