Closed Bug 1512658 Opened 7 years ago Closed 7 years ago

[remote-dbg-next] UX: Runtime page worker debug target

Categories

(DevTools :: about:debugging, enhancement, P1)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jdescottes, Unassigned)

References

(Blocks 1 open bug)

Details

Goal of this bug is to finalize the design of worker debug targets, and especially service workers. We have three subcategories of workers: - service workers - shared workers (https://developer.mozilla.org/en-US/docs/Web/API/SharedWorker) - other workers (regular web workers) For shared and other workers, the debug target is extremely simple: +------+------------------------------+----------------+ | | | | | icon | worker url | Inspect button | | | | | +------+------------------------------+----------------+ Note that the icon is always the same for all workers. For service workers we have much more information to display: - the state of the worker (currently displayed in a color coded badge containing either stopped, registering or running) - the action buttons are either : - just a Start button, if the worker is not running - a Push and an Inspect button if the worker is running - there is an Unregister link - fetch status: whether the service worker is listening to fetch events or not - scope
Priority: -- → P2

We don't have recent mockups for the service worker targets.

The overall design should be similar to the temporary extensions design visible at
https://mozilla.invisionapp.com/share/4PQDY0Z7GN3#/screens/346852729

The properties for service workers should be:

  • scope
  • state
  • fetch

The Inspect button should be the main card action.
The addition buttons displayed below the properties should be: start, push, unregister

Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Priority: P2 → P1
You need to log in before you can comment on or make changes to this bug.