Clicking "extension settings" in post-install popup breaks Customize tab and keyboard shortcuts
Categories
(Toolkit :: Add-ons Manager, defect, P1)
Tracking
()
People
(Reporter: hiroshi, Assigned: rpl)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [addons-jira])
Attachments
(3 files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-release+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-esr140+
|
Details | Review |
Changeset 5d0ea29d0b97 appends an empty fragment (#) to the current window's URL. This breaks several pieces of code that assume the window URL remains unchanged.
Steps to reproduce
- Install an extension (e.g. https://addons.mozilla.org/en-US/firefox/addon/firefox-color/).
- When the post-install popup panel appears, click the "extension settings" link.
- Open the Customize tab (The Application Menu [≡] > More Tools > Customize Toolbar…).
Actual results
Toolbar palette items are not appear in the Customize tab. The Browser Console shows the following error:
CustomizeMode: Error: buildWidget was called for a non-browser window!
buildWidgetNode moz-src:///browser/components/customizableui/CustomizableUI.sys.mjs:2495
WidgetGroupWrapper_forWindow moz-src:///browser/components/customizableui/CustomizableUI.sys.mjs:7080
#makePaletteItem moz-src:///browser/components/customizableui/CustomizeMode.sys.mjs:1082
#populatePalette moz-src:///browser/components/customizableui/CustomizeMode.sys.mjs:1047
enter moz-src:///browser/components/customizableui/CustomizeMode.sys.mjs:527
CustomizeMode.sys.mjs:1069
Expected results
Toolbar palette items appear correctly in the Customize tab, and no errors are logged.
Regression changeset
https://hg-edge.mozilla.org/mozilla-central/rev/5d0ea29d0b973a91d958d08d856d56230a86fd4e
| Reporter | ||
Comment 1•7 months ago
|
||
Additional symptoms and reproduction steps.
Steps to reproduce
- Follow Steps 1–2 from Comment 0.
- Press one of the following shortcut keys:
Ctrl+LCtrl+KAlt+Home
Actual results
-
Ctrl+L: Nothing appears to happen visually. The Browser Console shows the following error:
Uncaught InternalError: too much recursion openLocation chrome://browser/content/browser.js:1328 openLocation chrome://browser/content/browser.js:1338 ⋮ openLocation chrome://browser/content/browser.js:1338 browser.js:1328:7 -
Ctrl+K: Nothing appears to happen visually. The Browser Console shows the following error:
Uncaught InternalError: too much recursion webSearch moz-src:///browser/components/search/SearchUIUtils.sys.mjs:274 webSearch moz-src:///browser/components/search/SearchUIUtils.sys.mjs:281 ⋮ webSearch moz-src:///browser/components/search/SearchUIUtils.sys.mjs:281 SearchUIUtils.sys.mjs:274:7 -
Alt+Home: The home page opens in a new window.
Expected results
- Ctrl+L: Focus moves to the URL bar.
- Ctrl+K: Focus moves to the URL bar or the search bar (if visible).
- Alt+Home: The home page opens in the current tab.
Comment 2•7 months ago
|
||
I managed to reproduce the issue on macOS 13 using Nightly 144.0a1.
Comment 3•6 months ago
|
||
:wdurand, are you able to take a look? I expect the click handler should call preventDefault or whatever.
Metadata for https://searchfox.org/firefox-main/source/browser/base/content/browser-addons.js says this goes in add-ons manager code.
bug 1866923 for an example of how these checks break things. We should fix the checks, but there are a lot of them so that may be more work than we can do quickly.
Updated•6 months ago
|
Comment 4•6 months ago
|
||
Set release status flags based on info from the regressing bug 1964764
Updated•6 months ago
|
| Assignee | ||
Comment 5•6 months ago
|
||
Assigned to myself and P1-ed it.
We should also consider uplifting to ESR.
Updated•6 months ago
|
| Assignee | ||
Comment 6•6 months ago
|
||
Comment 8•6 months ago
|
||
| bugherder | ||
Comment 9•6 months ago
|
||
The patch landed in nightly and beta is affected.
:rpl, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox143towontfix.
For more information, please visit BugBot documentation.
Comment 10•6 months ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined: After a user have clicked on the "extension settings" link part of the add-on post install dialog, the customize tab feature and some keyboard shortcuts (See Bug 1983869 comment 1) do not work anymore in the same Firefox browser window. and there may be some other features that may also break due to the assumption that the browser window url is always strictly matching the original value (as briefly mentioned in Bug 1983869 comment 3).
Only the specific Firefox browser window should be broken, while the issue should not affect other existing or newly opened Firefox browser windows.
- Code covered by automated testing: yes
- Fix verified in Nightly: no
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: STR from Bug 1983869 comment 0.
- Risk associated with taking this patch: low
- Explanation of risk level: The fix is small, well understood and should not have any additional side-effect. The fix is also covered explicitly by an additional assertion added to the automated tests.
- String changes made/needed: No
- Is Android affected?: no
| Assignee | ||
Comment 11•6 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D264085
Comment 12•6 months ago
|
||
firefox-esr140 Uplift Approval Request
- User impact if declined: - After a user have clicked on the "extension settings" link part of the add-on post install dialog, the customize tab feature and some keyboard shortcuts (See Bug 1983869 comment 1) do not work anymore in the same Firefox browser window. and there may be some other features that may also break due to the assumption that the browser window url is always strictly matching the original value (as briefly mentioned in Bug 1983869 comment 3).
Only the specific Firefox browser window should be affected, while the issue should not affect other existing or newly opened Firefox browser windows.
- Code covered by automated testing: yes
- Fix verified in Nightly: no
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: STR from Bug 1983869 comment 0.
- Risk associated with taking this patch: low
- Explanation of risk level: The fix is small, well understood and should not have any additional side-effect. The fix is also covered explicitly by an additional assertion added to the automated tests.
- String changes made/needed: No
- Is Android affected?: no
| Assignee | ||
Comment 13•6 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D264085
| Assignee | ||
Updated•6 months ago
|
Updated•6 months ago
|
Comment 14•6 months ago
|
||
Updated•6 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
Comment 15•6 months ago
|
||
| uplift | ||
Comment 16•6 months ago
|
||
Verified as Fixed. Tested on the latest ESR (140.4.0esr/20250919030717 from https://treeherder.mozilla.org/jobs?repo=mozilla-esr140&revision=6054969e2149f90b801edd9179f681a7cf6039d0) under Windows 11 and Ubuntu 24.04 LTS using the STR from Comment 0 and Comment 1.
The toolbar palette items are displayed in the Customize tab and shortcuts work as expected.
Updated•6 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
Comment 17•6 months ago
|
||
| uplift | ||
Comment 18•6 months ago
|
||
Verified as Fixed. Tested on the latest Release (143.0.3/20250925195835 from https://treeherder.mozilla.org/jobs?repo=mozilla-release&revision=532de6796f942901e3943d4d241b84bcaf670ae7 as the builds there contain the fixes for this bug as well, as per the pushlog accessed via about:buildconfig) under Windows 11 and Ubuntu 24.04 LTS using the STR from Comment 0 and Comment 1.
The toolbar palette items are displayed in the Customize tab and shortcuts work as expected.
Description
•