DevTools/Features/ChangesView

Please use "Edit with form" above to edit this page.

Status

Changes View
Stage	Definition
Status	`
Release target	`
Health	OK
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	`

Open issues/risks

`

Stage 1: Definition

1. Feature overview

Browser developer tools allow users to make changes that give them immediate feedback, without reloads. Where possible, as with CSS, users should be able to just save their changes. Sometimes, however, that's not practical:

Changes to minified CSS and need to reapply those changes
They use LESS or SASS and need to apply their changes to a non-CSS language
Changes to HTML that came from some template language on the server

For cases like these, having a view that enumerates the changes that the user made to the page through the tools will help the user make any manual adjustments that they need to in their source code.

2. Users & use cases

`

3. Dependencies

`

4. Requirements

`

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

`

Feature details

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

Team status notes

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