DevTools/Features/PseudoClassLock

< DevTools‎ | Features
Revision as of 15:47, 19 October 2011 by Kdangoor (talk | contribs) (Created page with "{{FeatureStatus |Feature name=Pseudo-Class Lock |Feature stage=Design |Feature health=OK }} {{FeatureTeam |Feature product manager=Kevin Dangoor |Feature feature manager=Kevin Da...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Please use "Edit with form" above to edit this page.

Status

Pseudo-Class Lock
Stage Design
Status `
Release target `
Health OK
Status note `

{{#set:Feature name=Pseudo-Class Lock

|Feature stage=Design |Feature status=` |Feature version=` |Feature health=OK |Feature status note=` }}

Team

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

{{#set:Feature product manager=Kevin Dangoor

|Feature feature manager=Kevin Dangoor |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature 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
  1. this is an element-centric change, so all element-oriented tools (eg, Style Inspector) should follow along
  2. the selected state is locked in until the user is done with the tools (returns focus to the page)

Optional:

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

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

`

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

`

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=` |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. |Feature users and 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. |Feature dependencies=` |Feature requirements=# user must be able to toggle any of the four commonly supported pseudo-

    • active
    • focus
    • hover
    • visited
  1. this is an element-centric change, so all element-oriented tools (eg, Style Inspector) should follow along
  2. the selected state is locked in until the user is done with the tools (returns focus to the page)

Optional:

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

|Feature non-goals=` |Feature functional spec=` |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}

Feature details

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

{{#set:Feature priority=P1

|Feature rank=6 |Feature theme=` |Feature roadmap=Developer Tools |Feature secondary roadmap=` |Feature list=Desktop |Feature project=` |Feature engineering team=DevTools }}

Team status notes

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

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}