Closed
Bug 1585096
Opened 5 years ago
Closed 4 years ago
Clean up the code path separation caused by the devtools.responsive.browserUI.enabled pref
Categories
(DevTools :: Responsive Design Mode, task, P3)
DevTools
Responsive Design Mode
Tracking
(firefox80 fixed)
RESOLVED
FIXED
Firefox 80
| Tracking | Status | |
|---|---|---|
| firefox80 | --- | fixed |
People
(Reporter: gl, Assigned: mtigley)
References
(Blocks 2 open bugs)
Details
(Whiteboard: fission-rdm-reserve)
Attachments
(3 files)
No description provided.
|
||
Updated•5 years ago
|
Blocks: dt-rdm-fission
|
|
||
Updated•5 years ago
|
Priority: P3 → P2
|
||
Updated•5 years ago
|
Whiteboard: fission-rdm-mvp
|
|
||
Updated•5 years ago
|
Priority: P2 → P3
Whiteboard: fission-rdm-mvp → fission-rdm-reserve
|
Assignee | |
Updated•4 years ago
|
Assignee: nobody → mtigley
Status: NEW → ASSIGNED
|
|
Assignee | |
Updated•4 years ago
|
Summary: Clean up the code path separation caused by the devtools.responsive.browserUI.enabled pref in ui.js → Clean up the code path separation caused by the devtools.responsive.browserUI.enabled pref
|
|
Assignee | |
Comment 1•4 years ago
|
||
|
|
Assignee | |
Comment 2•4 years ago
|
||
Depends on D82557
|
|
Assignee | |
Comment 3•4 years ago
|
||
Depends on D82558
Pushed by mtigley@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6f2a450ccf51 Cleanup code path separation caused by browserUI pref in index.js, manager.js, and ui.js r=gl https://hg.mozilla.org/integration/autoland/rev/eaacbe5e997a Cleanup code path separation in RDM's React components. r=gl https://hg.mozilla.org/integration/autoland/rev/51c34a326c00 Cleanup code path separation in RDM's screenshot action. r=gl
|
||
Comment 5•4 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/6f2a450ccf51
https://hg.mozilla.org/mozilla-central/rev/eaacbe5e997a
https://hg.mozilla.org/mozilla-central/rev/51c34a326c00
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox80:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 80
You need to log in
before you can comment on or make changes to this bug.
Description
•