Platform/Features/Progress Element: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (clearing in prep for migration to new feature page format)
mNo edit summary
Line 1: Line 1:
{{FeatureStatus
|Feature name=<progress>
|Feature stage=Landed
|Feature version=Firefox 6
|Feature health=OK
|Feature status note=Landed and ready to be shipped.
}}
{{FeatureTeam
|Feature feature manager=Mounir Lamouri
|Feature lead engineer=Mounir Lamouri
|Feature accessibility lead=David Bolter
|Feature qa lead=Vlad Ghetiu
}}
{{FeaturePageBody
|Feature open issues and risks=* Should we ship with a nice default UI (when non-native)? ({{bug|644361}}) (''Mounir Lamouri'')
|Feature overview=Implementation of the <progress> element, a form widget to show a progression.


Goal: 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 good native UI
* Being able to style the element
* Accessible
|Feature functional spec=HTML spec: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html#the-progress-element
|Feature qa review=* Conformance tests (against specs)
* Rendering tests for layout
* Trying to have all bits of the patches tested
}}
{{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 13:46, 12 July 2011

Please use "Edit with form" above to edit this page.

Status

<progress>
Stage Landed
Status `
Release target Firefox 6
Health OK
Status note Landed and ready to be shipped.

{{#set:Feature name=<progress>

|Feature stage=Landed |Feature status=` |Feature version=Firefox 6 |Feature health=OK |Feature status note=Landed and ready to be shipped. }}

Team

Product manager `
Directly Responsible Individual Mounir Lamouri
Lead engineer Mounir Lamouri
Security lead `
Privacy lead `
Localization lead `
Accessibility lead David Bolter
QA lead Vlad Ghetiu
UX lead `
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=Vlad Ghetiu |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}

Open issues/risks

  • Should we ship with a nice default UI (when non-native)? (bug 644361) (Mounir Lamouri)

Stage 1: Definition

1. Feature overview

Implementation of the <progress> element, a form widget to show a progression.

Goal: 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 good native UI
  • Being able to style the element
  • Accessible

Non-goals

`

Stage 2: Design

5. Functional specification

HTML spec: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html#the-progress-element

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

`

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=* Should we ship with a nice default UI (when non-native)? (bug 644361) (Mounir Lamouri) |Feature overview=Implementation of the <progress> element, a form widget to show a progression.

Goal: 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 good native UI
  • Being able to style the element
  • Accessible

|Feature non-goals=` |Feature functional spec=HTML spec: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html#the-progress-element |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 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=` }}