Platform/Features/Input Number: Difference between revisions
m (clearing in prep for migration to new feature page format) |
mNo edit summary |
||
Line 1: | Line 1: | ||
{{FeatureStatus | |||
|Feature name=<input type='number'> | |||
|Feature stage=Development | |||
|Feature status=In progress | |||
|Feature health=OK | |||
|Feature status note=Content patches wrote and mostly reviewed. Layout patches TBD. | |||
}} | |||
{{FeatureTeam | |||
|Feature feature manager=Mounir Lamouri | |||
|Feature lead engineer=Mounir Lamouri | |||
|Feature accessibility lead=David Bolter | |||
|Feature qa lead=Simona Badau | |||
|Feature ux lead=Alex Limi | |||
}} | |||
{{FeaturePageBody | |||
|Feature open issues and risks=* Few specifications details (''Mounir Lamouri'') | |||
* User eXperience details (there are currently no plans) (''Alexander Limi'') | |||
* Accessibility plans ({{Bug|559761}}) (''David Bolter'') | |||
|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. | |||
|Feature requirements=* Follow specifications (except if on purpose) | |||
* Have a decent native and localized UI | |||
* Being able to style the element | |||
* Accessible | |||
|Feature non-goals=We do not want to have the ideal implementation especially for the UX. This could be improved later. | |||
|Feature functional spec=HTML spec: http://www.whatwg.org/specs/web-apps/current-work/multipage/number-state.html#number-state | |||
|Feature qa review=* Conformance tests (against specs) | |||
* Rendering tests for layout | |||
* Trying to have all bits of the patches tested | |||
|Feature implementation notes=* Feature tracking bug: {{bug|344616}} | |||
}} | |||
{{FeatureInfo | |||
|Feature priority=P1 | |||
|Feature roadmap=Platform | |||
|Feature list=Platform | |||
|Feature engineering team=Content | |||
}} | |||
{{FeatureTeamStatus | |||
|Feature products status=tbd | |||
|Feature engineering status=tbd | |||
|Feature security status=tbd | |||
|Feature privacy status=tbd | |||
|Feature localization status=tbd | |||
|Feature accessibility status=tbd | |||
|Feature qa status=tbd | |||
|Feature ux status=tbd | |||
|Feature product marketing status=tbd | |||
}} |
Revision as of 14:03, 12 July 2011
Status
<input type='number'> | |
Stage | Development |
Status | In progress |
Release target | ` |
Health | OK |
Status note | Content patches wrote and mostly reviewed. Layout patches TBD. |
{{#set:Feature name=<input type='number'>
|Feature stage=Development |Feature status=In progress |Feature version=` |Feature health=OK |Feature status note=Content patches wrote and mostly reviewed. Layout patches TBD. }}
Team
Product manager | ` |
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 | ` |
{{#set:Feature product manager=`
|Feature feature manager=Mounir Lamouri |Feature lead engineer=Mounir Lamouri |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=David Bolter |Feature qa lead=Simona Badau |Feature ux lead=Alex Limi |Feature product marketing lead=` |Feature operations lead=` |Feature 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
` {{#set:Feature open issues and risks=* Few specifications details (Mounir Lamouri)
- User eXperience details (there are currently no plans) (Alexander Limi)
- Accessibility plans (bug 559761) (David Bolter)
|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. |Feature users and use cases=` |Feature dependencies=` |Feature requirements=* Follow specifications (except if on purpose)
- Have a decent native and localized UI
- Being able to style the element
- Accessible
|Feature non-goals=We do not want to have the ideal implementation especially for the UX. This could be improved later. |Feature functional spec=HTML spec: http://www.whatwg.org/specs/web-apps/current-work/multipage/number-state.html#number-state |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=* Conformance tests (against specs)
- Rendering tests for layout
- Trying to have all bits of the patches tested
|Feature operations review=` |Feature implementation notes=* Feature tracking bug: bug 344616 |Feature landing criteria=` }}
Feature details
Priority | P1 |
Rank | 999 |
Theme / Goal | ` |
Roadmap | Platform |
Secondary roadmap | ` |
Feature list | Platform |
Project | ` |
Engineering team | Content |
{{#set:Feature priority=P1
|Feature rank=999 |Feature theme=` |Feature roadmap=Platform |Feature secondary roadmap=` |Feature list=Platform |Feature project=` |Feature engineering team=Content }}
Team status notes
status | notes | |
Products | tbd | ` |
Engineering | tbd | ` |
Security | tbd | ` |
Privacy | tbd | ` |
Localization | tbd | ` |
Accessibility | tbd | ` |
Quality assurance | tbd | ` |
User experience | tbd | ` |
Product marketing | tbd | ` |
Operations | ` | ` |
{{#set:Feature products status=tbd
|Feature products notes=` |Feature engineering status=tbd |Feature engineering notes=` |Feature security status=tbd |Feature security health=` |Feature security notes=` |Feature privacy status=tbd |Feature privacy notes=` |Feature localization status=tbd |Feature localization notes=` |Feature accessibility status=tbd |Feature accessibility notes=` |Feature qa status=tbd |Feature qa notes=` |Feature ux status=tbd |Feature ux notes=` |Feature product marketing status=tbd |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}