DevTools/Features/RulesView

From MozillaWiki
< DevTools‎ | Features
Revision as of 19:41, 5 October 2011 by Kdangoor (talk | contribs) (Created page with "{{FeatureStatus |Feature name=CSS Rules View |Feature stage=Draft |Feature version=Firefox 10 |Feature health=OK }} {{FeatureTeam |Feature product manager=Kevin Dangoor |Feature ...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Please use "Edit with form" above to edit this page.

Status

CSS Rules View
Stage Draft
Status `
Release target Firefox 10
Health OK
Status note `

{{#set:Feature name=CSS Rules View

|Feature stage=Draft |Feature status=` |Feature version=Firefox 10 |Feature health=OK |Feature status note=` }}

Team

Product manager Kevin Dangoor
Directly Responsible Individual Dave Camp
Lead engineer Dave Camp
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=Dave Camp |Feature lead engineer=Dave Camp |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

The Style Inspector provides a new view of CSS that is a hybrid between a computed styles view and the traditional rules-oriented view. While this view is useful and will become more useful over time, there are use cases for which the traditional rules-based view is better.

2. Users & use cases

All web developers use this view at one time or other.

Exploring the Hierarchy of Styles on an Element

When picking up a page from someone else (either a third party or an earlier developer within an organization) the rules view helps discover the organization of the stylesheets.

3. Dependencies

`

4. Requirements

  • Collection of rules that apply to the element selected by the Page Inspector
  • Sorted from most specific to least specific
  • Integrates with the Style Inspector

Desired, but not required for shipping:

  • Ability to edit values
  • Ability to toggle property/value pairs
  • Integration with the Style Editor
  • Media query support

Non-goals

`

Stage 2: Design

5. Functional specification

Media Queries

There was a straightforward suggestion for WebKit that would make sense for this tool as well.

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=The Style Inspector provides a new view of CSS that is a hybrid between a computed styles view and the traditional rules-oriented view. While this view is useful and will become more useful over time, there are use cases for which the traditional rules-based view is better. |Feature users and use cases=All web developers use this view at one time or other.

Exploring the Hierarchy of Styles on an Element

When picking up a page from someone else (either a third party or an earlier developer within an organization) the rules view helps discover the organization of the stylesheets. |Feature dependencies=` |Feature requirements=* Collection of rules that apply to the element selected by the Page Inspector

  • Sorted from most specific to least specific
  • Integrates with the Style Inspector

Desired, but not required for shipping:

  • Ability to edit values
  • Ability to toggle property/value pairs
  • Integration with the Style Editor
  • Media query support

|Feature non-goals=` |Feature functional spec===== Media Queries ====

There was a straightforward suggestion for WebKit that would make sense for this tool as well. |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 Unprioritized
Rank 999
Theme / Goal `
Roadmap Developer Tools
Secondary roadmap `
Feature list Desktop
Project `
Engineering team DevTools

{{#set:Feature priority=Unprioritized

|Feature rank=999 |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=` }}