Make copyRule in the ChangesView fission compatible
Categories
(DevTools :: Inspector: Changes, enhancement, P1)
Tracking
(Fission Milestone:M4, firefox72 fixed)
| Tracking | Status | |
|---|---|---|
| firefox72 | --- | fixed |
People
(Reporter: pbro, Assigned: gl)
References
(Blocks 1 open bug)
Details
(Whiteboard: dt-fission-reserve)
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
With Fission, and when bug 1568837 is fixed, we will be able to make CSS changes on nodes that may below to frames that run out of the main content process.
When that happens, we need the Changes panel to keep on tracking all of the changes, no matter which process they happen in.
Today, the panel receives events from an actor when any new change happens.
So, in theory, the required modification here is to start listening to events from multiple actors, one per each of the target that we care about.
|
||
Updated•5 years ago
|
|
Reporter | |
Updated•5 years ago
|
|
|
||
Updated•5 years ago
|
|
Assignee | |
Comment 1•5 years ago
|
||
|
|
||
Updated•5 years ago
|
|
|
Assignee | |
Updated•5 years ago
|
Pushed by gluong@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f16fe4737029 Make copyRule in the ChangesView fission compatible. r=rcaliman
|
||
Comment 3•5 years ago
|
||
| bugherder | ||
|
|
||
Comment 4•5 years ago
|
||
| bugherder landing | ||
|
||
Comment 5•5 years ago
|
||
Retroactively moving fixed bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to an appropriate Fission Milestone.
This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:
0ee3c76a-bc79-4eb2-8d12-05dc0b68e732
Description
•