Platform/Features/Progress Element

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

Status

<progress>
Stage	Complete
Status	Complete
Release target	Firefox 6
Health	OK
Status note	Shipped.

{{#set:Feature name=<progress>

|Feature stage=Complete |Feature status=Complete |Feature version=Firefox 6 |Feature health=OK |Feature status note=Shipped. }}

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	Vlad Ghetiu
UX lead	`
Product marketing lead	`
Operations lead	`
Additional members	`

{{#set:Feature product manager=Chris Blizzard

|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

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	DOM

{{#set:Feature priority=P1

|Feature rank=999 |Feature theme=` |Feature roadmap=Platform |Feature secondary roadmap=` |Feature list=Platform |Feature project=` |Feature engineering team=DOM }}

Team status notes

	status	notes
Products	`	`
Engineering	`	`
Security	pass	`
Privacy	priv-review-unnecessary	`
Localization	`	`
Accessibility	`	`
Quality assurance	Ready to land in Firefox 6	`
User experience	`	`
Product marketing	`	`
Operations	`	`

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=pass |Feature security health=` |Feature security notes=` |Feature privacy status=priv-review-unnecessary |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=Ready to land in Firefox 6 |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}