Closed Bug 1574343 Opened 4 years ago Closed 4 years ago

Improve process labels and icons


(DevTools :: Debugger, enhancement, P1)



(firefox70 fixed)

Firefox 70
Tracking Status
firefox70 --- fixed


(Reporter: jlast, Assigned: jlast)


(Blocks 1 open bug)


(Whiteboard: dt-fission-m1)


(3 files)

We currently show Processes as if they are workers in the sources tree and as if they are threads in the Threads pane. Neither case is it ideal :).

  • We should show a better label, perhaps based off of a title or url.
  • We should use a different icon, perhaps based off a favicon or other metadata we have.

We could also just do something generic like "Content Process 2" with a gear or something if we do not want to invest too much into heuristics.

Here's what we currently have in the browser toolbox if you enable the browsertoolbox fission pref.

I'm curious what others think would some good heuristics for a process label and icon in the sources tree?

Flags: needinfo?(ystartsev)
Flags: needinfo?(spenades)
Flags: needinfo?(poirot.alex)
Flags: needinfo?(odvarko)
Flags: needinfo?(hkirschner)
Priority: -- → P2
Blocks: dbg-fission
No longer blocks: dbg-watchpoints

Whatever decisions we make for the process label and icon should also apply for the threads pane

Summary: Improve the Source Tree's Process label and icon → Improve process labels and icons
Whiteboard: dt-fission

You could potentially use the content process id -- we don't have any other identifying information for those processes... So for example "Content Process <id>". Regarding the icons -- I think talking to Victoria would be the best idea

Flags: needinfo?(ystartsev)
Assignee: nobody → jlaster
Priority: P2 → P1
Pushed by
Improve process labels and icons. r=davidwalsh,yulia
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 70
Flags: needinfo?(spenades)
Flags: needinfo?(poirot.alex)
Flags: needinfo?(odvarko)

clearing ni

Flags: needinfo?(hkirschner)
Whiteboard: dt-fission → dt-fission dt-fission-m1
Whiteboard: dt-fission dt-fission-m1 → dt-fission-m1
You need to log in before you can comment on or make changes to this bug.