|Release target||Firefox 14|
|Status note||The discoverable UI has landed.|
|Product manager||Kevin Dangoor|
|Directly Responsible Individual||Kevin Dangoor|
|Lead engineer||Heather Arthur|
|QA lead||Ioana Budnar|
|Product marketing lead||`|
Stage 1: Definition
1. Feature overview
This feature provides the ability to set pseudo-classes for use in inspecting styles. For example, CSS styles that are applied on "hover" will naturally go away when you switch to the Page Inspector, because you're no longer hovering over the page element you're trying to examine. This feature gives users a mechanism for making "hover" and other pseudo-classes sticky while you're using the tools.
2. Users & use cases
Anyone doing web design uses this feature.
Examine Hover Styles
It's common to set styles that appear only on hover, so the user needs a way to dig into those styles, see how they're being applied and possibly tweak them using the editing capabilities of other parts of the tools suite.
- user must be able to toggle any of the four commonly supported pseudo-
- this is an element-centric change, so all element-oriented tools (eg, Style Inspector) should follow along
- the selected state is locked in until the user is done with the tools (returns focus to the page)
- support for changing additional pseudo-classes
Stage 2: Design
5. Functional specification
6. User experience design
Some discussion of putting this functionality in the Infobar occurred on dev-apps-firefox. DevTools/Features/RichInfobar was created along those lines, but broken up and replaced by this page and DevTools/Features/EasyAttributeEditing.
Stage 3: Planning
7. Implementation plan
Implementation is going on in bug 707740.
Quality Assurance review
Stage 4: Development
Stage 5: Release
10. Landing criteria
|Theme / Goal||`|
Team status notes
|Quality assurance||Signed off||Test Plan|