Test-case reducer add-on is blank on Nightly
Categories
(DevTools :: General, defect)
Tracking
(firefox-esr128 unaffected, firefox135 unaffected, firefox136 unaffected, firefox137 fixed)
Tracking | Status | |
---|---|---|
firefox-esr128 | --- | unaffected |
firefox135 | --- | unaffected |
firefox136 | --- | unaffected |
firefox137 | --- | fixed |
People
(Reporter: emilio, Assigned: emilio)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
STR
- Install https://addons.mozilla.org/en-US/firefox/addon/testcase-reducer/
- Go to any site like wikipedia.
- Inspect a node.
- Click on the test-case reducer add-on.
What happened?
Blank panel.
What should have happened?
The extension panel shows up.
Assignee | ||
Updated•6 months ago
|
Comment 1•6 months ago
|
||
Set release status flags based on info from the regressing bug 1943543
Assignee | ||
Comment 2•6 months ago
|
||
Might be a Core
issue since switching the deck to display: none and back "fixes" the issue...
Assignee | ||
Comment 3•6 months ago
|
||
I think this is wrong: It only propagates to same-browsing-context-tree children, but not to top descendants...
Assignee | ||
Updated•6 months ago
|
Assignee | ||
Comment 4•6 months ago
|
||
Updated•6 months ago
|
Comment 5•6 months ago
|
||
Toggling its visibility before loading the inner html document workaround
the platform issue around "IsUnderHiddenEmbedderElement".
Comment 6•6 months ago
|
||
I'm also attaching a really simple workaround in devtools, which simply reverts a small change I did in the regressor.
Just in case we can't get the BrowsingContext fix landed shortly.
Assignee | ||
Updated•6 months ago
|
Comment 7•6 months ago
|
||
Thanks emilio for jumping on fixing the BrowsingContext code. I pushed the devtools workaround to fix webextension addons in the next nightly.
Updated•6 months ago
|
Comment 10•6 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/b4d063601888
https://hg.mozilla.org/mozilla-central/rev/88f8b983d30d
Assignee | ||
Comment 11•6 months ago
|
||
Do you want to remove the DevTools workaround?
Description
•