DevTools/Features/ReadableDebug

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

Status

Readable Debugging (Prettify JavaScript)
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

JavaScript code on a production server is generally going to be minified. This makes it very difficult to debug (and this is especially true given that our JavaScript engine does not presently give column numbers in errors).

For this feature, we would provide the user with a way to prettify the JavaScript.

2. Users & use cases

`

3. Dependencies

`

4. Requirements

`

Non-goals

`

Stage 2: Design

5. Functional specification

If sourcemaps are available, those should be used rather than prettifying the code.

User can choose to prettify the code
User can set breakpoints against the prettified code
The choice to prettify a given script should be remembered between reloads
Breakpoints should be reapplied against the prettified code

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	Unprioritized
Rank	999
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	`	`