Expose watcherTraits in target actors
Categories
(DevTools :: Style Editor, task)
Tracking
(Fission Milestone:Future, firefox102 fixed)
Tracking | Status | |
---|---|---|
firefox102 | --- | fixed |
People
(Reporter: nchevobbe, Assigned: nchevobbe)
References
Details
Attachments
(1 file, 1 obsolete file)
(deleted),
text/x-phabricator-request
|
Details |
In Bug 1685268, we're going to introduce a temporary solution to check if a watcher has support for stylesheet resources. When Bug 1644397 lands we should be able to refactor that by exercising addDataEntry
instead (when the pref we're setting in Bug 1644397 is set to true).
Updated•3 years ago
|
Updated•3 years ago
|
Assignee | ||
Comment 1•3 years ago
|
||
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•2 years ago
|
Assignee | ||
Comment 2•2 years ago
|
||
The situation changed since last year. We now pass around a sessionContext
object to the content processes, so we can put the watcherTraits there.
Assignee | ||
Comment 3•2 years ago
|
||
This allows us to simplify and fix hasStyleSheetWatcherSupportForTarget
.
In the browser toolbox, since we're in a "all" session context type, TargetActorRegistry.getTargetActors
would only return an array of a single element, the parent process target.
In case of window global targets, in the browser toolbox context, we wouldn't
find the target we're looking for, which was making hasStyleSheetWatcherSupportForTarget
return false.
We can now simply look into the sessionContext watcherTraits property.
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Pushed by nchevobbe@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ea32c4c1d987 [devtools] Add supported targets and resources to session context. r=bomsy,ochameau.
Comment 5•2 years ago
|
||
bugherder |
Description
•