DevTools/Features/CSSDoctor: Difference between revisions

Revision as of 13:42, 9 May 2011

Feature	Status	ETA	Owner
Style Doctor	Work out plan from prototype to release	2011-05-13	Kevin Dangoor

Summary

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.

Team

Have ideas on solving this problem well? Do you know the dark, secret rules of CSS? Join us on #devtools on irc.mozilla.org, dev-apps-firefox or in our weekly devtools call and help out!

Feature Manager: Kevin Dangoor (irc: kdangoor)
Lead Developer: Joe Walker (irc: jwalker)
Product Manager: Kevin Dangoor (irc: kdangoor)
QA: TBD
UX: TBD
Security: TBD

Release Requirements

integrates with nodes selected via the Highlighter, GCLI or other means
can provide answers for a "substantial" set of node/rule combos.

Next Steps

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

Open Issues

can this work with multiple selected nodes?

Related Bugs & Dependencies

http://mozilla.github.com/devtools/2011/status.html#cssdoctor

Designs

(I believe Joe has some writeups we can add here...)

Use Cases

TBD

Test Plans

TBD

Goals/Use Cases

TBD

Non-Goals

TBD

@@ Line 39: / Line 39: @@
 == Next Steps ==
-* integrate prototype code in Firefox
+* test page with examples that test each rule
-* scope out the remaining work/file bugs
+* need the same thing working as a traditional addon
+* enough rules to produce interesting results
+** click around and get a sensible answer for many cases
+** those selectors don't match
+** everything is actually fine, the rule did apply
 == Open Issues ==