DevTools auto-responder

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


DevTools Auto-responder
Stage Feature Inbox
Status `
Release target `
Health OK
Status note `


Product manager `
Directly Responsible Individual `
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

As a web developer, I often find myself wanting to inject a new version of a JS or CSS file into a remote web site I'm currently debugging. The auto-responder (or request filter) would play the role of intercepting requests matching some regexp and redirecting to a configured file on disk.

2. Users & use cases

Users of this feature are web developers working on web sites/apps. The main use case is that of debugging an issue in production for example, or more specifically, testing a fix directly in the environment where it was found. Indeed, finding the cause of the bug, then working out a fix and then testing it locally may sometimes not be enough, actually testing in target environment can help.

I actually use Fiddler a lot and I'm a fan of their auto-responder feature and custom rules, but it would make my life easier if I could directly, say, right click on a request URL (from the console, or from the net tab, when there'll be one), and choose from the menu "respond with ..." and then browse to a file.

3. Dependencies


4. Requirements




Stage 2: Design

5. Functional specification


6. User experience design


Stage 3: Planning

7. Implementation plan


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 Unprioritized
Rank 999
Theme / Goal `
Roadmap `
Secondary roadmap `
Feature list `
Project `
Engineering team `

Team status notes

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