Support group in registerWindowActor
Categories
(Core :: DOM: Content Processes, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox76 | --- | fixed |
People
(Reporter: enndeakin, Assigned: enndeakin)
References
Details
Attachments
(2 files)
This is used by some actors defined in BrowserGlue.
Comment 1•5 years ago
|
||
The priority flag is not set for this bug.
:jimm, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•5 years ago
|
Assignee | ||
Comment 2•5 years ago
|
||
Bug 1610141 describes one case where this is needed. There are others I've found while porting some actors.
Legacy actors support a group flag which limits the actors from being applied to browser elements that don't have a matching 'messagemanagergroup'. Some specific groups that need to be distinguished:
- 'browsers' - the main browser elements in the window
- 'sidebar' - content loaded in a sidebar. Some actors should not apply here that would apply in other places.
- 'extensions' - content loaded in an extension.
- 'test' - the findbar, for example, is currently tested within some chrome tests that embed <browser type="content">. The actor would need to be created here.
Assignee | ||
Comment 3•5 years ago
|
||
Updated•5 years ago
|
Assignee | ||
Comment 4•5 years ago
|
||
Depends on D68780
Comment 7•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/986051b690e9
https://hg.mozilla.org/mozilla-central/rev/bb7b5139b10b
Comment 8•5 years ago
|
||
Is there a metabug to audit the existing actors that were converted and might benefit from having this property added? The page style actor from bug 1595370 is definitely one, but I bet there are others.
Assignee | ||
Updated•4 years ago
|
Description
•