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


Pseudo-Class Lock
Stage Complete
Status In progress
Release target Firefox 14
Health OK
Status note The discoverable UI has landed.


Product manager Kevin Dangoor
Directly Responsible Individual Kevin Dangoor
Lead engineer Heather Arthur
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead Ioana Budnar
UX lead `
Product marketing lead `
Operations lead `
Additional members `

Open issues/risks


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.

3. Dependencies


4. Requirements

  1. user must be able to toggle any of the four commonly supported pseudo-
    • active
    • focus
    • hover
    • visited
  2. this is an element-centric change, so all element-oriented tools (eg, Style Inspector) should follow along
  3. the selected state is locked in until the user is done with the tools (returns focus to the page)


  1. support for changing additional pseudo-classes
    • link
    • enabled
    • disabled
    • valid
    • invalid
    • checked



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.

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 P1
Rank 1
Theme / Goal `
Roadmap Developer Tools
Secondary roadmap `
Feature list Desktop
Project `
Engineering team DevTools

Team status notes

  status notes
Products ` `
Engineering ` `
Security sec-review-unnecessary `
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance Signed off Test Plan
User experience ` `
Product marketing ` `
Operations ` `