Enable watcher for webextension toolboxes
Categories
(DevTools :: General, task, P3)
Tracking
(firefox96 fixed)
Tracking | Status | |
---|---|---|
firefox96 | --- | fixed |
People
(Reporter: jdescottes, Assigned: ochameau)
References
(Blocks 3 open bugs)
Details
(Whiteboard: dt-perf-stability-triage)
Attachments
(3 files, 2 obsolete files)
The watcher is currently enabled for the content toolbox (localTab) and the MultiProcess Browser Toolbox. We should also start the watcher for webextension toolboxes.
Assignee | ||
Comment 2•5 years ago
|
||
Doesn't work out of the box:
https://treeherder.mozilla.org/jobs?repo=try&revision=d2df12f3a33fa934b8959a3e9050f73e3e4bc7b5
Assignee | ||
Comment 3•5 years ago
|
||
Updated•5 years ago
|
Assignee | ||
Comment 4•5 years ago
|
||
Assignee | ||
Comment 5•5 years ago
|
||
Assignee | ||
Comment 6•5 years ago
|
||
Fix issues with webextension spawning a special browser element with children browser element having distinct browserId.
This mess up with the browserId filtering done in the content process...
All/Many addons are running in the same process and the root browser element is not bound to any one in particular??
Updated•5 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 8•4 years ago
|
||
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 9•4 years ago
|
||
Without this, the webconsole fails to execute anything after reloading the add-on document.
Can reproduce by running location.reload()
in the console.
Comment 10•4 years ago
|
||
Comment 11•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/7950d8e5bc99
https://hg.mozilla.org/mozilla-central/rev/162a9da3f9b2
Updated•4 years ago
|
Description
•