Closed Bug 1547660 Opened 5 years ago Closed 5 years ago

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

Categories

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

Product:
DevTools
Component:
about:debugging
Type:
defect

Tracking

(firefox68 verified)

Status:
VERIFIED FIXED
Milestone:
Firefox 68
Tracking Flags:
Tracking Status
firefox68 --- verified

People

(Reporter: jdescottes, Assigned: ogasidlo)

References

(Blocks 1 open bug)

Details

(Whiteboard: [remote-debugging-reserve])

Attachments

(1 file)

Bug 1547660 - Move tabs as first category displayed + fix tests
47 bytes, text/x-phabricator-request
Details | Review

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
Blocks: remote-debugging-ng-m2
No longer blocks: remote-debugging-ng

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

https://hg.mozilla.org/mozilla-central/rev/5d8653071324

Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox68: --- → fixed
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
status-firefox68: fixed → verified
You need to log in before you can comment on or make changes to this bug.