Platform/Features/Progress Element: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (remove the redundant team section)
No edit summary
 
(13 intermediate revisions by 7 users not shown)
Line 1: Line 1:
{| class="fullwidth-table"
{{FeatureStatus
|-
|Feature name=<progress>
| style="font-weight: bold; background: #DDD;" | Feature
|Feature stage=Complete
| style="font-weight: bold; background: #DDD;" | Status
|Feature status=Complete
| style="font-weight: bold; background: #DDD;" | ETA
|Feature version=Firefox 6
| style="font-weight: bold; background: #DDD;" | Owner
|Feature health=OK
|-
|Feature status note=Shipped.
<section begin="status" />
}}
| <progress>
{{FeatureTeam
| {{StatusHealthy|status=Patches ready and reviewed except vertical progress bars.}}
|Feature product manager=Chris Blizzard
| 2011-05-30
|Feature feature manager=Mounir Lamouri
| Mounir Lamouri
|Feature lead engineer=Mounir Lamouri
<section end="status" />
|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.


== Summary ==
Goal: Have an implementation that can be used by authors as soon as it is released.
Implementation of the <progress> element, a form widget to show a progression.
|Feature requirements=* Follow specifications (except if on purpose)
 
See http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html#the-progress-element
 
== Team ==
* '''Feature Manager''': ''Mounir Lamouri''
* '''Developer''': ''Mounir Lamouri''
* '''Product Manager''':
* '''Accessibility''': ''David Bolter''
 
== Release Requirements ==
* Follow specifications (except if on purpose)
* Have a good native UI
* Have a good native UI
* Being able to style the element
* Being able to style the element
* Accessible
* Accessible
 
|Feature functional spec=HTML spec: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html#the-progress-element
== Steps ==
|Feature qa review=* Conformance tests (against specs)
* 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
* Make sure the element is accessible
* Implement the vertical progress bar (layout + native style)
* Nice default UI
 
== Open Issues ==
* Accessibility plans ({{Bug|559773}}) (''David Bolter'')
* What to do with vertical progress bars? Should we have this to ship? ({{bug|638540}}) (''Mounir Lamouri'')
* Should we ship with a nice default UI (when non-native)? ({{bug|644361}}) (''Mounir Lamouri'')
 
== Designs ==
HTML spec: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html#the-progress-element
 
== Test Plans ==
* Conformance tests (against specs)
* Rendering tests for layout
* Rendering tests for layout
* Trying to have all bits of the patches tested
* Trying to have all bits of the patches tested
 
}}
== Goals ==
{{FeatureInfo
Have an implementation that can be used by authors as soon as it is released.
|Feature priority=P1
 
|Feature roadmap=Platform
[[Category:Features]]
|Feature list=Platform
[[Category:Platform]]
|Feature engineering team=DOM
}}
{{FeatureTeamStatus
|Feature security status=pass
|Feature privacy status=priv-review-unnecessary
|Feature qa status=Ready to land in Firefox 6
}}

Latest revision as of 19:20, 8 December 2011

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

|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 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=` }}