From MozillaWiki
Jump to: navigation, search
Please use "Edit with form" above to edit this page.


Style Doctor
Stage Development
Status `
Release target `
Health OK
Status note need a test page to try out the rules+results


Product manager Kevin Dangoor
Directly Responsible Individual Kevin Dangoor
Lead engineer Joe Walker
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead `
UX lead `
Product marketing lead `
Operations lead `
Additional members `

Open issues/risks

  • can this work with multiple selected nodes?

Stage 1: Definition

1. Feature overview

The goal of the Style Doctor is to answer the question "why doesn't this look the way I expected it to?" as quickly as possible.

CSS rule precedence is complex and little understood and the Style Doctor will help users get their layouts working 'and' help them learn precedence at the same time.

2. Users & use cases

Some relevant discussion in "CSS developer tools" thread on dev-apps-firefox

3. Dependencies


4. Requirements

  • integrates with nodes selected via the Highlighter, GCLI or other means
  • can provide answers for a "substantial" set of node/rule combos. Problems of the sort:
    • selector didn't match or was overridden
    • error in CSS (some errors require the context of a node)
    • layout problems (Shaver's list: too indented, not indented enough, too narrow, too wide, not aligned with something else, etc.)



Stage 2: Design

5. Functional specification


6. User experience design


Stage 3: Planning

7. Implementation plan

  • test page with examples that test each rule
  • need the same thing working as a traditional addon
  • enough rules to produce interesting results (perhaps ~15)
    • click around and get a sensible answer for many cases
    • those selectors don't match
    • everything is actually fine, the rule did apply

8. Reviews

Security review


Privacy review


Localization review




Quality Assurance review


Operations review


Stage 4: Development

9. Implementation

Stage 5: Release

10. Landing criteria


Feature details

Priority P3
Rank 6
Theme / Goal `
Roadmap Developer Tools
Secondary roadmap `
Feature list Desktop
Project `
Engineering team DevTools

Team status notes

  status notes
Products ` `
Engineering ` `
Security ` `
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance ` `
User experience ` `
Product marketing ` `
Operations ` `