Closed Bug 1547660 Opened 1 year ago Closed 1 year ago

[remote-dbg-next] Tabs should be the first category displayed for remote runtimes

Categories

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

defect

Tracking

(firefox68 verified)

VERIFIED FIXED
Firefox 68
Tracking Status
firefox68 --- verified

People

(Reporter: jdescottes, Assigned: ogasidlo)

References

(Blocks 1 open bug)

Details

(Whiteboard: [remote-debugging-reserve])

Attachments

(1 file)

When connecting to a remote runtime, Tabs should be the main focus. Right now the categories are displayed in the following order:

  • Temporary Extensions (hidden on remote runtimes)
  • Extensions
  • Tabs (hidden on local runtimes, behind a pref)
  • Service Workers
  • Shared Workers
  • Other Workers

Tabs should be the first item in this list.

The order is hardcoded at RuntimePage.js#174-182. Updating this component should be enough + running the tests to see if anything fails.

In theory we want this behavior only for remote runtimes, but since Tabs are hidden by default for local runtimes, no need make the order based on the connection type, we can just put Tabs first all the time.

Assignee: nobody → ogasidlo
Status: NEW → ASSIGNED
Priority: -- → P1

Move tabs as first category in "this firefox" + remote runtime display

Whiteboard: [remote-debugging-reserve]
Pushed by ogasidlo@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5d8653071324
Move tabs as first category displayed + fix tests r=jdescottes
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 68

Verified as fixed on Firefox Nightly 68.0a1 (2019-05-15) on Windows 10 x 64, Mac OS X 10.14 and on Ubuntu 18.04 x64.

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.