Fix the use of both `toolbarbutton-1` and `subviewbutton` CSS classes in extension widgets
Categories
(WebExtensions :: Frontend, task, P3)
Tracking
(firefox112 fixed)
| Tracking | Status | |
|---|---|---|
| firefox112 | --- | fixed |
People
(Reporter: willdurand, Assigned: willdurand)
References
(Blocks 1 open bug)
Details
(Whiteboard: [addons-jira])
Attachments
(5 files)
In Bug 1798324, we updated the style of the extension (CUI) widgets to match the Unified Extensions UI. These widgets are "custom" widgets and have two buttons. One of them is the primary (or action) button, also known as "view button" for the widgets of type "custom".
The view button in a custom widget is placed in the toolbar when the widget is pinned. We use the .toolbarbutton-1 class on this button for that reason. In addition, we use .subviewbutton on this same button when the widget is placed in a panel (unified extensions panel in most cases). See: https://searchfox.org/mozilla-central/rev/219df29d0fb5d8928ae41bba4a605046de411cf0/browser/components/extensions/parent/ext-browserAction.js#229-233
We should not use these two CSS classes on the same button. There were a few ideas in https://phabricator.services.mozilla.com/D161036.
Updated•3 years ago
|
Updated•3 years ago
|
| Assignee | ||
Comment 1•3 years ago
|
||
Updated•3 years ago
|
| Assignee | ||
Comment 2•3 years ago
|
||
Fixing this bug would also fix a minor difference between CUI widgets and custom elements in the panel: when -moz-window-inactive is set, toolbar buttons have an opacity of 0.5, which essentially makes them less visible. That is not the case for the custom elements (at the bottom of the list) as seen in the screenshot.
Updated•3 years ago
|
Comment 4•3 years ago
|
||
Backed out changeset ab00cf793f29 (bug 1800417) for causing failures at browser_unified_extensions_overflowable_toolbar.js.
Backout: https://hg.mozilla.org/integration/autoland/rev/4c85944d11f569aea754ebbec96cdce3a3b4b652
Failure log: https://treeherder.mozilla.org/logviewer?job_id=403965999&repo=autoland&lineNumber=38794
| Assignee | ||
Comment 5•3 years ago
|
||
I am still trying to fix Bug 1798683 to unlock the patch for this bug..
Comment 7•3 years ago
•
|
||
Meant to back out bug 1798683
Will reland this.
Sorry
Updated•3 years ago
|
Comment 9•3 years ago
|
||
This is the actual culprit. Backfills confirm it
Backed out for causing bc failures in browser/components/extensions/test/browser/browser_unified_extensions_overflowable_toolbar.js
Backout link: https://hg.mozilla.org/integration/autoland/rev/883042d84c6a74e474c0fcb4be8cb93fe3909b77
| Assignee | ||
Comment 11•3 years ago
|
||
:mconley I am not able to land this patch because of an obscure bug on Linux, that I cannot reproduce myself. I can consistently reproduce on Try, though and the screenshot (attached here) reminds me of Bug 1798973, which we couldn't reproduce either. Could you please take a look?
Comment 12•3 years ago
|
||
Here's a try push for that test directory on the same platform with some added profiler markers and profiling enabled. Let's see if we can deduce what's happening here: https://treeherder.mozilla.org/jobs?repo=try&revision=94d9461452a2703e07a8af18bf8aa0a4159dcc0a
Will leave needinfo for now while I wait for the build to complete.
Comment 13•3 years ago
|
||
So the issue seems to be that the OverflowableToolbar reports itself as not being enabled at the time that the resize event occurs:
https://share.firefox.dev/40H2Iy3
Looking into why that might be...
Comment 14•3 years ago
|
||
Another try push with more logging to see if we can find where the OverflowableToolbar is being disabled: https://treeherder.mozilla.org/jobs?repo=try&revision=4b7cb913a8d350f7fd44289399d1a08bfb0dbd5b
Comment 15•3 years ago
|
||
The problem was that a previous test (browser_unified_extensions_cui.js) had fired an event on the toolbox that disabled the OverflowableToolbar for all windows to simulate entering customize mode, and then didn't fire the event to simulate exiting it again.
This seems to fix the test for me: https://hg.mozilla.org/try/rev/962d9ce798e71a42203d8376ccc5b1bd59344680
Try push: https://treeherder.mozilla.org/jobs?repo=try&revision=a4b09b4711717be1d53b06fb5766d329adcbc53f
Comment 16•3 years ago
|
||
Comment 17•3 years ago
|
||
Backed out changeset d26e7747cf69 (Bug 1800417) for bc failures on browser_unified_extensions_overflowable_toolbar.js.
Backout link
Push with failures <--> bc7
Failure Log
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Comment 18•3 years ago
|
||
| Assignee | ||
Updated•3 years ago
|
Comment 19•3 years ago
|
||
Comment 20•3 years ago
|
||
Comment 21•3 years ago
|
||
Backed out for causing mochitest failures in browser_unified_extensions_overflowable_toolbar.js
- Backout link
- Push with failures
- Failure Log
- Failure line: TEST-UNEXPECTED-FAIL | browser/components/extensions/test/browser/browser_unified_extensions_overflowable_toolbar.js | Test timed out -
Comment 22•3 years ago
|
||
| bugherder | ||
| Assignee | ||
Comment 23•3 years ago
|
||
Depends on D162712
Depends on D162712
Comment 24•3 years ago
|
||
Comment 25•3 years ago
|
||
| bugherder | ||
| Assignee | ||
Updated•3 years ago
|
Comment 26•3 years ago
|
||
This bug caused the default extension icon (i.e. for an extension without an icon) to change from white to black in dark mode.
I can provide more details or file a bug if needed, but I don't have time to at this exact moment; I just mozregressioned this and thought I'd leave a note.
Comment 27•3 years ago
|
||
(In reply to Justin Peter from comment #26)
This bug caused the default extension icon (i.e. for an extension without an icon) to change from white to black in dark mode.
I can provide more details or file a bug if needed, but I don't have time to at this exact moment; I just mozregressioned this and thought I'd leave a note.
Thanks, should be fixed in bug 1817865.
Comment 28•3 years ago
|
||
Comment 29•3 years ago
|
||
| bugherder | ||
Description
•