Issue_id
stringlengths 7
7
| Summary
stringlengths 10
255
| Description
stringlengths 12
2.29k
| Description_all
stringlengths 51
2.34k
| Priority
stringclasses 5
values | Status
stringclasses 6
values | Resolution
stringclasses 9
values | Created
stringdate 2020-01-02 13:46:45
2025-03-05 20:35:25
| Resolved
stringdate 2020-01-14 02:57:17
2025-03-05 21:47:22
| token_count
int16 12
511
| Priority_label
int16 1
5
|
|---|---|---|---|---|---|---|---|---|---|---|
1940329
|
Custom search engines don't work when keyword.enabled is set to false
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:135.0) Gecko/20100101 Firefox/135.0
Steps to reproduce:
1. Install a custom search engine (such as the OpenSearch plugins offered by MediaWiki installations).
2. Set keyword.enabled to false.
3. Try to make a search using this engine, either by an assigned shortcut or the search icon in the address bar.
Actual results:
The search term is interpreted as a hostname or an IP address.
Expected results:
The search term should be passed on to the selected search engine.
The default search engines still work with this setting, as did custom search engines prior to Firefox 135. As I understand it, it should only disable searching by default when no engine is selected.
|
Custom search engines don't work when keyword.enabled is set to false User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:135.0) Gecko/20100101 Firefox/135.0
Steps to reproduce:
1. Install a custom search engine (such as the OpenSearch plugins offered by MediaWiki installations).
2. Set keyword.enabled to false.
3. Try to make a search using this engine, either by an assigned shortcut or the search icon in the address bar.
Actual results:
The search term is interpreted as a hostname or an IP address.
Expected results:
The search term should be passed on to the selected search engine.
The default search engines still work with this setting, as did custom search engines prior to Firefox 135. As I understand it, it should only disable searching by default when no engine is selected.
|
P3
|
VERIFIED
|
FIXED
|
2025-01-07 21:40:14+00:00
|
2025-02-03 13:08:19+00:00
| 198
| 3
|
1940334
|
Browser tabs do not follow the correct HCM styles
|
## Prerequisites:
Found in Nightly 136.0a1 (2025-01-07)
Turn on Night Sky HCM in Windows
## STR:
1. Follow prerequisites above
2. Open Firefox Nightly
## Expected / Actual:
The Desktop Anatomy, specifically the browser tabs, should follow the HCM styling found in the [High Contrast Mode file](https://www.figma.com/design/VHRA9hZ54oJqKKJwPd6FWa/High-Contrast-Mode?node-id=1366-29&p=f&t=ZkZTWocXU3uIxoLn-0) in Figma. At this time, the styling does not match in Nightly.
|
Browser tabs do not follow the correct HCM styles ## Prerequisites:
Found in Nightly 136.0a1 (2025-01-07)
Turn on Night Sky HCM in Windows
## STR:
1. Follow prerequisites above
2. Open Firefox Nightly
## Expected / Actual:
The Desktop Anatomy, specifically the browser tabs, should follow the HCM styling found in the [High Contrast Mode file](https://www.figma.com/design/VHRA9hZ54oJqKKJwPd6FWa/High-Contrast-Mode?node-id=1366-29&p=f&t=ZkZTWocXU3uIxoLn-0) in Figma. At this time, the styling does not match in Nightly.
|
P3
|
NEW
|
2025-01-07 22:01:36+00:00
|
2025-01-14 19:55:21+00:00
| 177
| 3
|
|
1940444
|
Uncaught TypeError: can't access property "pinned", middleTab is undefined when attemtping to drag multiple discontinuous tabs while there's a collapsed tab group
|
STR:
- Add a tab group and collapse it
- Add at least three tabs
- Attempt to drag two of those tabs that aren't directly adjacent
->
```
Uncaught TypeError: can't access property "pinned", middleTab is undefined
addAnimationData chrome://browser/content/tabbrowser/tabs.js:2596
#moveTogetherSelectedTabs chrome://browser/content/tabbrowser/tabs.js:2630
startTabDrag chrome://browser/content/tabbrowser/tabs.js:716
on_dragstart chrome://browser/content/tabbrowser/tabs.js:655
handleEvent chrome://browser/content/tabbrowser/tabs.js:2749
```
|
Uncaught TypeError: can't access property "pinned", middleTab is undefined when attemtping to drag multiple discontinuous tabs while there's a collapsed tab group STR:
- Add a tab group and collapse it
- Add at least three tabs
- Attempt to drag two of those tabs that aren't directly adjacent
->
```
Uncaught TypeError: can't access property "pinned", middleTab is undefined
addAnimationData chrome://browser/content/tabbrowser/tabs.js:2596
#moveTogetherSelectedTabs chrome://browser/content/tabbrowser/tabs.js:2630
startTabDrag chrome://browser/content/tabbrowser/tabs.js:716
on_dragstart chrome://browser/content/tabbrowser/tabs.js:655
handleEvent chrome://browser/content/tabbrowser/tabs.js:2749
```
|
P1
|
RESOLVED
|
FIXED
|
2025-01-08 14:20:40+00:00
|
2025-01-09 04:20:52+00:00
| 241
| 1
|
1940496
|
The autoplay indicator label can sometimes persist after loading a new page in a tab
|
I loaded searchfox on top of a youtube tab. The autoplay text stayed in the tab title. See attached screenshot.
|
The autoplay indicator label can sometimes persist after loading a new page in a tab I loaded searchfox on top of a youtube tab. The autoplay text stayed in the tab title. See attached screenshot.
|
P3
|
NEW
|
2025-01-08 16:17:29+00:00
|
2025-01-24 17:21:35+00:00
| 45
| 3
|
|
1940510
|
New tab page shortcuts use page title instead of configured title after bug 1868060
|
After bug 1868060, the titles I have configured on my new tab page shortcuts are completely ignored, and the original page title is used instead.
|
New tab page shortcuts use page title instead of configured title after bug 1868060 After bug 1868060, the titles I have configured on my new tab page shortcuts are completely ignored, and the original page title is used instead.
|
P2
|
RESOLVED
|
FIXED
|
2025-01-08 16:57:33+00:00
|
2025-01-23 18:15:31+00:00
| 52
| 2
|
1940533
|
controls on web pages no longer work with latest update. Right mouse, open link in new tab does not work. How do I roll back to previous version?
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
Any right mouse click, opens different longer list of options, and no option works properly. Cannot open link in new tab and stay in current tab, especially in mail.yahoo.com
Actual results:
nothing happens, no tab opens. Have to click on link which takes me to new tab, and then click back to yahoo.mail.
Expected results:
new tab opens, stay in current tab with yahoo mail.
|
controls on web pages no longer work with latest update. Right mouse, open link in new tab does not work. How do I roll back to previous version? User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
Any right mouse click, opens different longer list of options, and no option works properly. Cannot open link in new tab and stay in current tab, especially in mail.yahoo.com
Actual results:
nothing happens, no tab opens. Have to click on link which takes me to new tab, and then click back to yahoo.mail.
Expected results:
new tab opens, stay in current tab with yahoo mail.
|
P1
|
RESOLVED
|
FIXED
|
2025-01-08 18:00:05+00:00
|
2025-02-10 12:25:53+00:00
| 163
| 1
|
1940545
|
Unnamed tab groups have empty tooltip value on tab label hover
|
See screenshot for example.
Expected result:
Tooltip should say "Unnamed group" (the same string we use elsewhere to describe the group).
Actual result:
The tooltip appears but is empty.
|
Unnamed tab groups have empty tooltip value on tab label hover See screenshot for example.
Expected result:
Tooltip should say "Unnamed group" (the same string we use elsewhere to describe the group).
Actual result:
The tooltip appears but is empty.
|
P3
|
VERIFIED
|
FIXED
|
2025-01-08 18:43:22+00:00
|
2025-02-11 06:50:59+00:00
| 56
| 3
|
1940558
|
The add shortcuts option in new tab is not shown under specific conditions.
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
Firefox should either be freshly installed or a new profile should be created.
Remove the default shortcuts already present.
Uncheck the option to show sponsored shortcuts while leaving the option to show shortcuts checked.
Actual results:
The add shortcuts option in new tab is missing when show sponsored shortcuts option is unchecked. Its visibility seems to be dependent on the sponsored shortcuts option.
Expected results:
The add shortcuts button should not be missing in new tab unless that option has been unselected.
|
The add shortcuts option in new tab is not shown under specific conditions. User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
Firefox should either be freshly installed or a new profile should be created.
Remove the default shortcuts already present.
Uncheck the option to show sponsored shortcuts while leaving the option to show shortcuts checked.
Actual results:
The add shortcuts option in new tab is missing when show sponsored shortcuts option is unchecked. Its visibility seems to be dependent on the sponsored shortcuts option.
Expected results:
The add shortcuts button should not be missing in new tab unless that option has been unselected.
|
P2
|
NEW
|
2025-01-08 19:39:42+00:00
|
2025-01-31 18:10:38+00:00
| 177
| 2
|
|
1940583
|
Turning off "inactive tabs" setting doesn't appear correctly on other devices
|
This connect post https://connect.mozilla.org/t5/discussions/stop-moving-synced-tabs-to-inactive/m-p/82399#M31498 mentioned turning the "inactive tabs" setting off and syncing doesn't appear to move the tabs out of the "inactive tabs" folder when looking at remote tabs on other devices. I was able to reproduce this with iOS and :markh reproduced on Android as well.
Steps to reproduce:
1. Turn on inactive tabs feature
- On iOS: 3 line menu on bottom right -> Settings -> Tabs -> Inactive Tabs
2. Have some tabs be inactive and sync
3. Look at the remote tabs for this device on another device (desktop, android)
4. See the inactive tabs "folder" under the device name in synced tabs
5. Turn off the setting on the device used in steps 1-2 and sync
6. Check that the tabs are now listed and not nested under "inactive tabs"
- Inactive tabs still show
|
Turning off "inactive tabs" setting doesn't appear correctly on other devices This connect post https://connect.mozilla.org/t5/discussions/stop-moving-synced-tabs-to-inactive/m-p/82399#M31498 mentioned turning the "inactive tabs" setting off and syncing doesn't appear to move the tabs out of the "inactive tabs" folder when looking at remote tabs on other devices. I was able to reproduce this with iOS and :markh reproduced on Android as well.
Steps to reproduce:
1. Turn on inactive tabs feature
- On iOS: 3 line menu on bottom right -> Settings -> Tabs -> Inactive Tabs
2. Have some tabs be inactive and sync
3. Look at the remote tabs for this device on another device (desktop, android)
4. See the inactive tabs "folder" under the device name in synced tabs
5. Turn off the setting on the device used in steps 1-2 and sync
6. Check that the tabs are now listed and not nested under "inactive tabs"
- Inactive tabs still show
|
P2
|
NEW
|
2025-01-08 22:30:50+00:00
|
2025-01-08 22:32:02+00:00
| 248
| 2
|
|
1940591
|
Typing w does not prompt to search for wikipedia
|
Typing w will not match wikipedia, typing "e" will (if ebay is not enabled). This is because the code that matches engines was copied from the current autofill implementation that attempts to match the domain of the engine and not the engine name. The previous implementation had to ensure the muxer could deduplicate the hueristic result.
We do not need to worry about that with actions as the autofill result / hueristic are seperate from the actions and will not be considered duplicated either way. The match should match simply with the engine name for consistency / simplicitys sake.
|
Typing w does not prompt to search for wikipedia Typing w will not match wikipedia, typing "e" will (if ebay is not enabled). This is because the code that matches engines was copied from the current autofill implementation that attempts to match the domain of the engine and not the engine name. The previous implementation had to ensure the muxer could deduplicate the hueristic result.
We do not need to worry about that with actions as the autofill result / hueristic are seperate from the actions and will not be considered duplicated either way. The match should match simply with the engine name for consistency / simplicitys sake.
|
P2
|
VERIFIED
|
FIXED
|
2025-01-08 23:15:08+00:00
|
2025-02-24 12:34:33+00:00
| 137
| 2
|
1940645
|
Contextual Search ignores favicon on reddit
|
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:135.0) Gecko/20100101 Firefox/135.0
Steps to reproduce:
1. Open reddit.com
2. Focus Address Bar
3. Input any query
Actual results:
The Contextual Search button is displayed without the Reddit favicon. If the user adds Reddit to Firefox’s search engines, it will also appear there without the favicon
Expected results:
In other cases Contextual Search is able to display the favicon both on the button and in search engines list.
|
Contextual Search ignores favicon on reddit User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:135.0) Gecko/20100101 Firefox/135.0
Steps to reproduce:
1. Open reddit.com
2. Focus Address Bar
3. Input any query
Actual results:
The Contextual Search button is displayed without the Reddit favicon. If the user adds Reddit to Firefox’s search engines, it will also appear there without the favicon
Expected results:
In other cases Contextual Search is able to display the favicon both on the button and in search engines list.
|
P3
|
NEW
|
2025-01-09 03:14:01+00:00
|
2025-01-30 13:22:33+00:00
| 143
| 3
|
|
1940647
|
Fix alignment for onboarding messages ("keep closed" and survey) injected into shopping-container empty states
|
The empty states apply margins to center the text content and illustrations on the RC sidebar. One downside that I missed is how the [styling](https://searchfox.org/mozilla-central/rev/6b61714b224f8cdca1a48ef1c51edab027f2c09f/browser/components/shopping/content/shopping-container.css#83) affects other content. The components most impacted are the "keep closed" messages and user survey. We'll want to ensure that the messages are positioned at the very top of the sidebar.
I believe the messages are rendered for opted-in users, so we only need to worry about the empty states we implemented in shopping-container.mjs. We conditionally add a [class name](https://searchfox.org/mozilla-central/rev/6b61714b224f8cdca1a48ef1c51edab027f2c09f/browser/components/shopping/content/shopping-container.mjs#539) that determines whether or not we apply the styles.
|
Fix alignment for onboarding messages ("keep closed" and survey) injected into shopping-container empty states The empty states apply margins to center the text content and illustrations on the RC sidebar. One downside that I missed is how the [styling](https://searchfox.org/mozilla-central/rev/6b61714b224f8cdca1a48ef1c51edab027f2c09f/browser/components/shopping/content/shopping-container.css#83) affects other content. The components most impacted are the "keep closed" messages and user survey. We'll want to ensure that the messages are positioned at the very top of the sidebar.
I believe the messages are rendered for opted-in users, so we only need to worry about the empty states we implemented in shopping-container.mjs. We conditionally add a [class name](https://searchfox.org/mozilla-central/rev/6b61714b224f8cdca1a48ef1c51edab027f2c09f/browser/components/shopping/content/shopping-container.mjs#539) that determines whether or not we apply the styles.
|
P2
|
NEW
|
2025-01-09 03:24:12+00:00
|
2025-02-05 21:39:56+00:00
| 276
| 2
|
|
1940649
|
Intermittent browser/components/tabbrowser/test/browser/tabs/browser_multiselect_tabs_close_duplicate_tabs.js | single tracking bug
|
**Filed by:** sstanca [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=489325648&repo=mozilla-beta
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/CpRRLCEmTKKoEyvPvVHwuQ/runs/0/artifacts/public/logs/live_backing.log
---
```
[task 2025-01-09T03:42:16.520Z] 03:42:16 INFO - TEST-PASS | browser/components/tabbrowser/test/browser/tabs/browser_multiselect_tabs_close_duplicate_tabs.js | 1736394093193 > 1736393972627 -
[task 2025-01-09T03:42:16.520Z] 03:42:16 INFO - Buffered messages finished
[task 2025-01-09T03:42:16.520Z] 03:42:16 INFO - TEST-UNEXPECTED-FAIL | browser/components/tabbrowser/test/browser/tabs/browser_multiselect_tabs_close_duplicate_tabs.js | Test timed out -
[task 2025-01-09T03:42:16.521Z] 03:42:16 INFO - GECKO(753) | Completed ShutdownLeaks collections in process 753
[task 2025-01-09T03:42:16.521Z] 03:42:16 INFO - TEST-START | Shutdown
```
|
Intermittent browser/components/tabbrowser/test/browser/tabs/browser_multiselect_tabs_close_duplicate_tabs.js | single tracking bug **Filed by:** sstanca [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=489325648&repo=mozilla-beta
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/CpRRLCEmTKKoEyvPvVHwuQ/runs/0/artifacts/public/logs/live_backing.log
---
```
[task 2025-01-09T03:42:16.520Z] 03:42:16 INFO - TEST-PASS | browser/components/tabbrowser/test/browser/tabs/browser_multiselect_tabs_close_duplicate_tabs.js | 1736394093193 > 1736393972627 -
[task 2025-01-09T03:42:16.520Z] 03:42:16 INFO - Buffered messages finished
[task 2025-01-09T03:42:16.520Z] 03:42:16 INFO - TEST-UNEXPECTED-FAIL | browser/components/tabbrowser/test/browser/tabs/browser_multiselect_tabs_close_duplicate_tabs.js | Test timed out -
[task 2025-01-09T03:42:16.521Z] 03:42:16 INFO - GECKO(753) | Completed ShutdownLeaks collections in process 753
[task 2025-01-09T03:42:16.521Z] 03:42:16 INFO - TEST-START | Shutdown
```
|
P5
|
REOPENED
|
2025-01-09 03:44:00+00:00
|
2025-02-17 07:01:26+00:00
| 433
| 5
|
|
1940703
|
Adress bar action misses full word match
|
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
When entering action '>' in adress bar and entering 'print' while it is up 'prin' a suggestion 'Print page' is offered. However when entering 'print' there are no suggestions.
Actual results:
entered action 'print' into address bar, no suggestion found. I expect action 'Print page' to be available
Expected results:
when I enter action 'print' the suggestion should be 'Print page'
|
Adress bar action misses full word match User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
When entering action '>' in adress bar and entering 'print' while it is up 'prin' a suggestion 'Print page' is offered. However when entering 'print' there are no suggestions.
Actual results:
entered action 'print' into address bar, no suggestion found. I expect action 'Print page' to be available
Expected results:
when I enter action 'print' the suggestion should be 'Print page'
|
P2
|
NEW
|
2025-01-09 11:04:18+00:00
|
2025-01-20 16:26:31+00:00
| 140
| 2
|
|
1940707
|
Address bar actions suggestion are not matched in a natural way
|
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:135.0) Gecko/20100101 Firefox/135.0
Steps to reproduce:
When entering action in Address bar action do match. Exampl: Save as PDF is listed as a suggestion, typing 's', 'save' won't filter suggestions to 'Save as PDF' . Entering 'view page' won't filter the actions to 'View Page Source' initially shown as suggestion
Actual results:
Unable to find actions by enting their name, suggestions are initially visible
Expected results:
When entering 'save' I want to see all action suggestions containg the word 'save', e.g 'Save to PDF'. When entering 'view' I want to see all actions containg the word 'view'.
Action search completely misses the point: Initially the suggestions for action are there, when entering any word contained in the suggestion the output is random.
|
Address bar actions suggestion are not matched in a natural way User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:135.0) Gecko/20100101 Firefox/135.0
Steps to reproduce:
When entering action in Address bar action do match. Exampl: Save as PDF is listed as a suggestion, typing 's', 'save' won't filter suggestions to 'Save as PDF' . Entering 'view page' won't filter the actions to 'View Page Source' initially shown as suggestion
Actual results:
Unable to find actions by enting their name, suggestions are initially visible
Expected results:
When entering 'save' I want to see all action suggestions containg the word 'save', e.g 'Save to PDF'. When entering 'view' I want to see all actions containg the word 'view'.
Action search completely misses the point: Initially the suggestions for action are there, when entering any word contained in the suggestion the output is random.
|
P3
|
NEW
|
2025-01-09 11:17:27+00:00
|
2025-01-20 16:26:28+00:00
| 215
| 3
|
|
1940745
|
Reopening a closed tab group with Ctrl+Shift+T doesn't work, if Ctrl+Shift+T was pressed while another window was focused first
|
Steps to reproduce:
1. Open two windows.
2. In window A, create a tab group that has at least one tab with "real content" (i.e. not `about:blank`)
3. Right click the tab group label and select "Delete tab group"
4. Switch to window B and press Cmd+Shift+T
5. Switch back to window A and press Cmd+Shift+T again
Expected result:
The tab group reopens.
Actual result:
The tabs reopen ungrouped
Additional context:
On step 4, pressing Cmd+Shift+T in window B, the following console error appears: `JavaScript error: resource:///modules/sessionstore/SessionStore.sys.mjs, line 7888: NS_ERROR_ILLEGAL_VALUE: No saved tab group with specified id`.
|
Reopening a closed tab group with Ctrl+Shift+T doesn't work, if Ctrl+Shift+T was pressed while another window was focused first Steps to reproduce:
1. Open two windows.
2. In window A, create a tab group that has at least one tab with "real content" (i.e. not `about:blank`)
3. Right click the tab group label and select "Delete tab group"
4. Switch to window B and press Cmd+Shift+T
5. Switch back to window A and press Cmd+Shift+T again
Expected result:
The tab group reopens.
Actual result:
The tabs reopen ungrouped
Additional context:
On step 4, pressing Cmd+Shift+T in window B, the following console error appears: `JavaScript error: resource:///modules/sessionstore/SessionStore.sys.mjs, line 7888: NS_ERROR_ILLEGAL_VALUE: No saved tab group with specified id`.
|
P3
|
RESOLVED
|
WORKSFORME
|
2025-01-09 14:17:23+00:00
|
2025-02-04 17:19:14+00:00
| 216
| 3
|
1940752
|
Attempting to reopen a closed tab group from the "Reopen Closed Tab" tab context menu item does not work
|
Steps to reproduce:
1. Open some tabs and load sites in them (i.e. not `about:blank`)
2. Multi-select the tabs, right click, and select "Add Tabs to New Group". Close the tab group dialog by clicking "Done".
3. Right click the tab group label and click "Delete group"
4. Right click any other open tab, or the tab strip itself, and click "Reopen Closed Tabs"
Expected result:
All tabs reopen and are opened in their original group
Actual result:
Only one of the tabs in the original tab is re-opened, and it is ungrouped.
|
Attempting to reopen a closed tab group from the "Reopen Closed Tab" tab context menu item does not work Steps to reproduce:
1. Open some tabs and load sites in them (i.e. not `about:blank`)
2. Multi-select the tabs, right click, and select "Add Tabs to New Group". Close the tab group dialog by clicking "Done".
3. Right click the tab group label and click "Delete group"
4. Right click any other open tab, or the tab strip itself, and click "Reopen Closed Tabs"
Expected result:
All tabs reopen and are opened in their original group
Actual result:
Only one of the tabs in the original tab is re-opened, and it is ungrouped.
|
P2
|
VERIFIED
|
FIXED
|
2025-01-09 14:41:40+00:00
|
2025-02-14 10:28:02+00:00
| 166
| 2
|
1940793
|
"New tab" in group doesn't show up when reopening tab groups
|
**Steps to reproduce [can add screenshots or video recordings for reference]:**
1. Create a tab group with "New tab" in a group and include other tabs that isn't "New tab"
2. Save and close group
3. Reopen the tab group in the TOM menu
**Expected behavior [What should have happened?]:**
Tab group should reopen with all tabs visible that were last in the group (including New tab)
**Actual behavior [What actually happened?]:**
Opens tab group but leaves out "New tab"
Follow-up to this, if you create a tab group with ONLY "New tab" the tab group doesn't open at all
|
"New tab" in group doesn't show up when reopening tab groups **Steps to reproduce [can add screenshots or video recordings for reference]:**
1. Create a tab group with "New tab" in a group and include other tabs that isn't "New tab"
2. Save and close group
3. Reopen the tab group in the TOM menu
**Expected behavior [What should have happened?]:**
Tab group should reopen with all tabs visible that were last in the group (including New tab)
**Actual behavior [What actually happened?]:**
Opens tab group but leaves out "New tab"
Follow-up to this, if you create a tab group with ONLY "New tab" the tab group doesn't open at all
|
P2
|
NEW
|
2025-01-09 17:18:15+00:00
|
2025-01-15 16:28:27+00:00
| 168
| 2
|
|
1940878
|
Source title's color in DS sections is an inaccessible color when high contrast and light theme are toggled
|
Seems that if users have a setting of **preferred contrast** on their devices + they have light-theme toggled, the source titles of content cards are a white color instead of black.
On mac, enable the preferred contrast setting by:
- Going to settings
- Selecting 'Accessibility'
- Selecting 'Display'
- Toggling on 'Increase contrast'
Steps to reproduce:
1. Open a new tab page on Firefox
2. Click the devtools icon (if disabled, go to `about:config` and enable the `browser.newtabpage.activity-stream.asrouter.devtoolsEnabled` pref)
3. Enable the DS Sections toggle
4. Open a new tab
5. If light theme is toggled, notice the source title of the content cards is a white color on a white background, making it inaccessible.
Expected result:
Source title is an accessible color (i.e. black)
Actual result:
Source title's color is white on a white background, deeming it inaccessible
|
Source title's color in DS sections is an inaccessible color when high contrast and light theme are toggled Seems that if users have a setting of **preferred contrast** on their devices + they have light-theme toggled, the source titles of content cards are a white color instead of black.
On mac, enable the preferred contrast setting by:
- Going to settings
- Selecting 'Accessibility'
- Selecting 'Display'
- Toggling on 'Increase contrast'
Steps to reproduce:
1. Open a new tab page on Firefox
2. Click the devtools icon (if disabled, go to `about:config` and enable the `browser.newtabpage.activity-stream.asrouter.devtoolsEnabled` pref)
3. Enable the DS Sections toggle
4. Open a new tab
5. If light theme is toggled, notice the source title of the content cards is a white color on a white background, making it inaccessible.
Expected result:
Source title is an accessible color (i.e. black)
Actual result:
Source title's color is white on a white background, deeming it inaccessible
|
P2
|
RESOLVED
|
FIXED
|
2025-01-10 04:14:22+00:00
|
2025-01-13 09:38:21+00:00
| 241
| 2
|
1941112
|
Contextual Search Mode ignores text input if there is a saved search engine
|
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:135.0) Gecko/20100101 Firefox/135.0
Steps to reproduce:
1. Save Wikipedia to Firefox search engines
2. Open https://en.wikipedia.org/
3. Focus the address bar
4. Enter a search query
5. Click "Search with Wikipedia" (Contextual Search Mode button)
Actual results:
A clear address bar is displayed with the Wikipedia search engine chosen. User's query is removed.
Expected results:
Search results should be displayed for user query.
But this only happens on those sites if their search engines have not been saved to Firefox’s search engine list
Video:
https://drive.proton.me/urls/FVJ152BCTR#VZdNTo4SQ6Vd
|
Contextual Search Mode ignores text input if there is a saved search engine User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:135.0) Gecko/20100101 Firefox/135.0
Steps to reproduce:
1. Save Wikipedia to Firefox search engines
2. Open https://en.wikipedia.org/
3. Focus the address bar
4. Enter a search query
5. Click "Search with Wikipedia" (Contextual Search Mode button)
Actual results:
A clear address bar is displayed with the Wikipedia search engine chosen. User's query is removed.
Expected results:
Search results should be displayed for user query.
But this only happens on those sites if their search engines have not been saved to Firefox’s search engine list
Video:
https://drive.proton.me/urls/FVJ152BCTR#VZdNTo4SQ6Vd
|
P3
|
RESOLVED
|
DUPLICATE
|
2025-01-11 12:25:12+00:00
|
2025-01-22 10:03:02+00:00
| 200
| 3
|
1941177
|
Vertical tab spacing changes when the vertical tab bar is collapsed/expanded
|
STR:
1. Enable Vertical tabs
2. Open several tabs
3. Toggle collapse/expand vertical tabbar
AR:
Vertical tab spacing changes when the vertical tab bar is collapsed/expanded.
Screencast: https://youtu.be/wX9ra1KLst4
ER:
Vertical tab spacing should not change
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=c72899901f29c51caa57cb3b84518041a9952e18&tochange=3b597e62bd28015328688468f817ad50d4d42106
|
Vertical tab spacing changes when the vertical tab bar is collapsed/expanded STR:
1. Enable Vertical tabs
2. Open several tabs
3. Toggle collapse/expand vertical tabbar
AR:
Vertical tab spacing changes when the vertical tab bar is collapsed/expanded.
Screencast: https://youtu.be/wX9ra1KLst4
ER:
Vertical tab spacing should not change
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=c72899901f29c51caa57cb3b84518041a9952e18&tochange=3b597e62bd28015328688468f817ad50d4d42106
|
P3
|
RESOLVED
|
DUPLICATE
|
2025-01-12 09:01:21+00:00
|
2025-01-25 21:18:20+00:00
| 180
| 3
|
1941189
|
Vertical pinned tabs area shows scrollbar with 5 tabs
|
See attached screenshot
|
Vertical pinned tabs area shows scrollbar with 5 tabs See attached screenshot
|
P3
|
NEW
|
2025-01-12 11:53:52+00:00
|
2025-02-04 16:09:28+00:00
| 18
| 3
|
|
1941249
|
Follow/unfollow UI in cards sections are inaccessible with a dark background
|
Make sure to have the following prefs enabled to view the Follow/Unfollow button UI:
- `browser.newtabpage.activity-stream.discoverystream.sections.personalization.enabled`
- `browser.newtabpage.activity-stream.discoverystream.sections.cards.enabled`
- `browser.newtabpage.activity-stream.discoverystream.sections.enabled`
If a user has a dark background set on their about:home page, the follow/unfollow buttons are not easily seen compared to light backgrounds.
|
Follow/unfollow UI in cards sections are inaccessible with a dark background Make sure to have the following prefs enabled to view the Follow/Unfollow button UI:
- `browser.newtabpage.activity-stream.discoverystream.sections.personalization.enabled`
- `browser.newtabpage.activity-stream.discoverystream.sections.cards.enabled`
- `browser.newtabpage.activity-stream.discoverystream.sections.enabled`
If a user has a dark background set on their about:home page, the follow/unfollow buttons are not easily seen compared to light backgrounds.
|
P1
|
RESOLVED
|
FIXED
|
2025-01-13 03:58:26+00:00
|
2025-01-15 07:35:10+00:00
| 133
| 1
|
1941276
|
Action search behavior deviates from other special searches
|
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:135.0) Gecko/20100101 Firefox/135.0
Steps to reproduce:
1. Focus on the address bar.
2. Type > to start the action search.
3. Type query, "print" for example.
Actual results:
Default search is activated. To initiate action search, the user must press the spacebar after the ">" keyword.
Expected results:
Action search is activated, and the "print" button is displayed. This is expected behavior, as it occurs with other keyword.
In summary:
- Bookmark search (*) and tab search (%) do not require a space after the key symbol.
- Action search does require a space after the key symbol.
Particularly noteworthy is that if the user input is simply « print » without the keyword « > », they will encounter a secondary action button. However, this is not the case when keywords are used.
|
Action search behavior deviates from other special searches User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:135.0) Gecko/20100101 Firefox/135.0
Steps to reproduce:
1. Focus on the address bar.
2. Type > to start the action search.
3. Type query, "print" for example.
Actual results:
Default search is activated. To initiate action search, the user must press the spacebar after the ">" keyword.
Expected results:
Action search is activated, and the "print" button is displayed. This is expected behavior, as it occurs with other keyword.
In summary:
- Bookmark search (*) and tab search (%) do not require a space after the key symbol.
- Action search does require a space after the key symbol.
Particularly noteworthy is that if the user input is simply « print » without the keyword « > », they will encounter a secondary action button. However, this is not the case when keywords are used.
|
P3
|
NEW
|
2025-01-13 09:29:39+00:00
|
2025-01-27 16:32:17+00:00
| 222
| 3
|
|
1941324
|
Closing Settings does not go back to last tab when Settings already open
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
While the "Settings" tab was already open somewhere else, do
1. Click on "Settings" from the menu
2. Close the "Settings" tab
Actual results:
The focus did not go back to the tab from where I clicked on "Settings"
Expected results:
The focus went back to the tab from where I clicked "Settings"
|
Closing Settings does not go back to last tab when Settings already open User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
While the "Settings" tab was already open somewhere else, do
1. Click on "Settings" from the menu
2. Close the "Settings" tab
Actual results:
The focus did not go back to the tab from where I clicked on "Settings"
Expected results:
The focus went back to the tab from where I clicked "Settings"
|
P5
|
NEW
|
2025-01-13 13:14:17+00:00
|
2025-02-26 06:35:24+00:00
| 129
| 5
|
|
1941361
|
[Cards] Small card lose the contextual menu when saved to pocket
|
This was tested on Nightly 136.0a1 (2025-01-13) (64-bit)
Steps to reproduce:
1. Enable sections and the new cards UI to see small cards
2. Go to the contextual menu and click on "save to pocket"
3. Hover again the small card and the contextual menu is no longer visible.
|
[Cards] Small card lose the contextual menu when saved to pocket This was tested on Nightly 136.0a1 (2025-01-13) (64-bit)
Steps to reproduce:
1. Enable sections and the new cards UI to see small cards
2. Go to the contextual menu and click on "save to pocket"
3. Hover again the small card and the contextual menu is no longer visible.
|
P1
|
NEW
|
2025-01-13 15:47:34+00:00
|
2025-01-22 22:57:36+00:00
| 89
| 1
|
|
1941622
|
Closed window's closed tabs do not get saved by session restore if the window has no worth-saving tabs at time of close
|
Steps to reproduce (using a new profile):
1. In `about:config`, ensure `browser.sessionstore.closedTabsFromClosedWindows` is `true`
2. Open two windows
3. In window A, open a number of tabs with "worth-saving" content (i.e. a real website, not just `about:blank`)
4. Close all the tabs you just opened in window A, such that only one tab remains (the "New Tab" that was created when the window was first opened).
5. In the top menu, go to "History > Recently Closed Tabs". Observe the list of tabs you just closed.
6. Close window A. (Window B should still be open).
7. Reopen the "History" menu.
Expected result:
The list of tabs continues to appear in the "Recently Closed Tabs" menu.
Actual result:
No recently closed tabs exist and the "Recently Closed Tabs" menu item is disabled.
Notes:
My suspicion is that on window close, session store is checking if the window has any open "worth saving" tabs, and discarding it if it does not, even though that window may have "worth saving" *closed tabs* that should be saved.
|
Closed window's closed tabs do not get saved by session restore if the window has no worth-saving tabs at time of close Steps to reproduce (using a new profile):
1. In `about:config`, ensure `browser.sessionstore.closedTabsFromClosedWindows` is `true`
2. Open two windows
3. In window A, open a number of tabs with "worth-saving" content (i.e. a real website, not just `about:blank`)
4. Close all the tabs you just opened in window A, such that only one tab remains (the "New Tab" that was created when the window was first opened).
5. In the top menu, go to "History > Recently Closed Tabs". Observe the list of tabs you just closed.
6. Close window A. (Window B should still be open).
7. Reopen the "History" menu.
Expected result:
The list of tabs continues to appear in the "Recently Closed Tabs" menu.
Actual result:
No recently closed tabs exist and the "Recently Closed Tabs" menu item is disabled.
Notes:
My suspicion is that on window close, session store is checking if the window has any open "worth saving" tabs, and discarding it if it does not, even though that window may have "worth saving" *closed tabs* that should be saved.
|
P3
|
NEW
|
2025-01-14 17:28:56+00:00
|
2025-01-20 16:44:40+00:00
| 302
| 3
|
|
1941630
|
Firefox Menu button has vague accessible name of "Firefox"
|
### Prerequisites:
1. Ensure a screen reader is running, i.e. NVDA on WinOS
### STR:
1. In Firefox, locate and focus with keyboard the hamburger menu and observe the screen reader announcement
1. you'd need to press `Tab` key until you get to the last group of toolbar controls, by default in release starting with "Save to Pocket" button, then press `Right Arrow` key to move the focus through the tools to the hamburger menu
### Expected:
1. Menu button has a clear accessible name that concisely describes the functionality of this control, i.e. "Application menu" or "Firefox menu"
### Actual:
1. `Firefox` is the label of the menu button. It has a description `Open application menu` that is often skipped and should not be relied on to provide an accessible name and communicate the functionality of the control
This is an [access-S3 issue](https://wiki.mozilla.org/Accessibility/Triage) because it relies on assistive technology users to guess what this button would do. It really is close to `access-S2` issue because at the moment the `Firefox` label is meaningless within the Firefox application.
Screen reader users in the recent user interviews (4 of 4) missed this button or did not really need what to expect in it, i.e.:
> Firefox Button - application button. I do not know what it does, honestly.
Note that while users did find an alternative ways to the actions requested via the ribbon menu, not all functionality is provided in there and could only be accessed via the main menu or a direct URI "about:" which is not widely known by users
|
Firefox Menu button has vague accessible name of "Firefox" ### Prerequisites:
1. Ensure a screen reader is running, i.e. NVDA on WinOS
### STR:
1. In Firefox, locate and focus with keyboard the hamburger menu and observe the screen reader announcement
1. you'd need to press `Tab` key until you get to the last group of toolbar controls, by default in release starting with "Save to Pocket" button, then press `Right Arrow` key to move the focus through the tools to the hamburger menu
### Expected:
1. Menu button has a clear accessible name that concisely describes the functionality of this control, i.e. "Application menu" or "Firefox menu"
### Actual:
1. `Firefox` is the label of the menu button. It has a description `Open application menu` that is often skipped and should not be relied on to provide an accessible name and communicate the functionality of the control
This is an [access-S3 issue](https://wiki.mozilla.org/Accessibility/Triage) because it relies on assistive technology users to guess what this button would do. It really is close to `access-S2` issue because at the moment the `Firefox` label is meaningless within the Firefox application.
Screen reader users in the recent user interviews (4 of 4) missed this button or did not really need what to expect in it, i.e.:
> Firefox Button - application button. I do not know what it does, honestly.
Note that while users did find an alternative ways to the actions requested via the ribbon menu, not all functionality is provided in there and could only be accessed via the main menu or a direct URI "about:" which is not widely known by users
|
P3
|
NEW
|
2025-01-14 18:03:53+00:00
|
2025-01-23 17:29:52+00:00
| 395
| 3
|
|
1941645
|
Tab group with many tabs moves when expanding and collapsing
|
**Steps to reproduce [can add screenshots or video recordings for reference]:**
Create a tab group with many tabs inside (example has 26 tabs)
Open enough ungrouped tabs in the tab strip to have scrolling arrows appear to the left and right of the tab strip
**Expected behavior [What should have happened?]:**
I can expand and collapse a group without the tab strip scrolling to another position (if I click on the group to expanding/collapse, it should still stay in the same position or close enough to the same position so I wouldn't have to move my mouse to click on it again).
**Actual behavior [What actually happened?]:**
When expanding and collapsing a large tab group, the tab strip scrolls so the label is no longer visible on the tab strip (expanding). When collapsing the tab group the tab strip scrolls so I have to move my mouse to click on the tab group again (see video attachment).
|
Tab group with many tabs moves when expanding and collapsing **Steps to reproduce [can add screenshots or video recordings for reference]:**
Create a tab group with many tabs inside (example has 26 tabs)
Open enough ungrouped tabs in the tab strip to have scrolling arrows appear to the left and right of the tab strip
**Expected behavior [What should have happened?]:**
I can expand and collapse a group without the tab strip scrolling to another position (if I click on the group to expanding/collapse, it should still stay in the same position or close enough to the same position so I wouldn't have to move my mouse to click on it again).
**Actual behavior [What actually happened?]:**
When expanding and collapsing a large tab group, the tab strip scrolls so the label is no longer visible on the tab strip (expanding). When collapsing the tab group the tab strip scrolls so I have to move my mouse to click on the tab group again (see video attachment).
|
P1
|
VERIFIED
|
FIXED
|
2025-01-14 19:35:26+00:00
|
2025-01-20 09:24:06+00:00
| 217
| 1
|
1941799
|
Selecting "Reopen All Tabs" from the "Recently Closed Tabs" menu opens all tabs ungrouped, even if some of them were closed by deleting a tab group
|
Steps to reproduce:
1. Open some "worth-saving" tabs. Put some of them in a tab group.
2. Right click the tab group label and select "Delete group".
3. Close the rest of the ungrouped tabs.
4. From the top menu, go to "History > Recently Closed Tabs > Reopen All Tabs".
Expected result:
All tabs are reopened, and the tabs that were closed through deleting the tab group are reopened as part of a group.
Actual result:
All tabs are reopened ungrouped.
|
Selecting "Reopen All Tabs" from the "Recently Closed Tabs" menu opens all tabs ungrouped, even if some of them were closed by deleting a tab group Steps to reproduce:
1. Open some "worth-saving" tabs. Put some of them in a tab group.
2. Right click the tab group label and select "Delete group".
3. Close the rest of the ungrouped tabs.
4. From the top menu, go to "History > Recently Closed Tabs > Reopen All Tabs".
Expected result:
All tabs are reopened, and the tabs that were closed through deleting the tab group are reopened as part of a group.
Actual result:
All tabs are reopened ungrouped.
|
P2
|
VERIFIED
|
FIXED
|
2025-01-15 14:42:41+00:00
|
2025-02-10 08:34:57+00:00
| 162
| 2
|
1941832
|
In the all tabs menu, sort saved groups by when they were closed
|
As discussed with Stefan and Amy.
|
In the all tabs menu, sort saved groups by when they were closed As discussed with Stefan and Amy.
|
P2
|
RESOLVED
|
FIXED
|
2025-01-15 16:36:50+00:00
|
2025-01-16 21:45:05+00:00
| 24
| 2
|
1941857
|
Copying complete punycode URL's from the address bar does not percent-encode them while partial URL's work fine
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
Yesterday I was reading into punycode and looking for an URL example to do some tests with it and I found something that seems not to be correct. Specifically:
1. Open the non-existent example site https://møllerriis.dk/ .
2. When Firefox tells you the site could not be loaded copy the full URL out of the address bar and paste it somewhere (like Notepad).
3. Repeat the previous step with only copying a part of the URL from the address bar (anything except the last / ).
Actual results:
Copying the full URL does not percent-encode it while copying the partial URL does percent-encode it.
Expected results:
Both copied URL's should have been percent-encoded.
Additional details:
I recall a few years ago there was an issue where copying full non-punycode URL's did percent-encode them while this did not work for partial URL's. But this got changed so that copying partial URL's from the beginning does percent-encode them as well. Now with punycode URL's the case is swaped here for some reason.
|
Copying complete punycode URL's from the address bar does not percent-encode them while partial URL's work fine User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
Yesterday I was reading into punycode and looking for an URL example to do some tests with it and I found something that seems not to be correct. Specifically:
1. Open the non-existent example site https://møllerriis.dk/ .
2. When Firefox tells you the site could not be loaded copy the full URL out of the address bar and paste it somewhere (like Notepad).
3. Repeat the previous step with only copying a part of the URL from the address bar (anything except the last / ).
Actual results:
Copying the full URL does not percent-encode it while copying the partial URL does percent-encode it.
Expected results:
Both copied URL's should have been percent-encoded.
Additional details:
I recall a few years ago there was an issue where copying full non-punycode URL's did percent-encode them while this did not work for partial URL's. But this got changed so that copying partial URL's from the beginning does percent-encode them as well. Now with punycode URL's the case is swaped here for some reason.
|
P3
|
NEW
|
2025-01-15 18:16:11+00:00
|
2025-01-16 18:04:43+00:00
| 324
| 3
|
|
1941963
|
Importing RemoteSettingsExperimentLoader has side effects
|
Importing RemoteSettingsExperimentLoader.sys.mjs presently creates a [`new _RemoteSettingsExperimentLoader()`](https://searchfox.org/mozilla-central/rev/cbc10b90d92e10fd695cd75f966756ea28596308/toolkit/components/nimbus/lib/RemoteSettingsExperimentLoader.sys.mjs#894-895), which has the side effect of registering observers (https://searchfox.org/mozilla-central/rev/cbc10b90d92e10fd695cd75f966756ea28596308/toolkit/components/nimbus/lib/RemoteSettingsExperimentLoader.sys.mjs#144-167). Because unit tests often make their own test RemoteSettingExperimentLoaders, this means that at any given time there can be two active RSEL listening for events. This has lead to intermittent and hard to debug test failures when making seemingly innocuous changes.
IMO this is enough of a footgun to warrant refactoring and such a refactor should make it easier for non-experts to write unit tests in Nimbus.
|
Importing RemoteSettingsExperimentLoader has side effects Importing RemoteSettingsExperimentLoader.sys.mjs presently creates a [`new _RemoteSettingsExperimentLoader()`](https://searchfox.org/mozilla-central/rev/cbc10b90d92e10fd695cd75f966756ea28596308/toolkit/components/nimbus/lib/RemoteSettingsExperimentLoader.sys.mjs#894-895), which has the side effect of registering observers (https://searchfox.org/mozilla-central/rev/cbc10b90d92e10fd695cd75f966756ea28596308/toolkit/components/nimbus/lib/RemoteSettingsExperimentLoader.sys.mjs#144-167). Because unit tests often make their own test RemoteSettingExperimentLoaders, this means that at any given time there can be two active RSEL listening for events. This has lead to intermittent and hard to debug test failures when making seemingly innocuous changes.
IMO this is enough of a footgun to warrant refactoring and such a refactor should make it easier for non-experts to write unit tests in Nimbus.
|
P2
|
RESOLVED
|
FIXED
|
2025-01-16 01:02:42+00:00
|
2025-02-24 22:35:24+00:00
| 318
| 2
|
1942064
|
PDF viewer seems to have problems displaying images correctly rotated (maybe EXIF related)
|
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
1. Open the pdf.js issue #12027 on GitHub: https://github.com/mozilla/pdf.js/issues/12027
2. Open the file "pdfjs_orientation_issue.pdf" with Firefox:
https://github.com/mozilla/pdf.js/files/4836022/pdfjs_orientation_issue.pdf
3. Open the same file with a different PDF viewer (e.g. Chrome, Edge, Acrobat Reader, etc.)
Actual results:
The image in the PDF is rotated incorrectly in Firefox.
Expected results:
The image should have the same orientation as in other PDF viewers.
|
PDF viewer seems to have problems displaying images correctly rotated (maybe EXIF related) User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
1. Open the pdf.js issue #12027 on GitHub: https://github.com/mozilla/pdf.js/issues/12027
2. Open the file "pdfjs_orientation_issue.pdf" with Firefox:
https://github.com/mozilla/pdf.js/files/4836022/pdfjs_orientation_issue.pdf
3. Open the same file with a different PDF viewer (e.g. Chrome, Edge, Acrobat Reader, etc.)
Actual results:
The image in the PDF is rotated incorrectly in Firefox.
Expected results:
The image should have the same orientation as in other PDF viewers.
|
P3
|
VERIFIED
|
FIXED
|
2025-01-16 14:35:13+00:00
|
2025-02-13 16:01:54+00:00
| 220
| 3
|
1942095
|
Newtab startupcache race condition
|
Seeing a couple race conditions with the startup cache.
The big one being:
1. If the events that flip isForStartupCache happen before startup cached page has rehydrated, the rehydrated page doesn't have the updated state from those events.
Other race condition I have found:
2. If sponsored topsites finishes before sponsored stories, or vice versa, and flips isForStartupCache, the other section displays a cached ad.
|
Newtab startupcache race condition Seeing a couple race conditions with the startup cache.
The big one being:
1. If the events that flip isForStartupCache happen before startup cached page has rehydrated, the rehydrated page doesn't have the updated state from those events.
Other race condition I have found:
2. If sponsored topsites finishes before sponsored stories, or vice versa, and flips isForStartupCache, the other section displays a cached ad.
|
P2
|
NEW
|
2025-01-16 16:17:33+00:00
|
2025-03-05 06:09:48+00:00
| 107
| 2
|
|
1942156
|
Dialog is missing name and correct role
|
## Prerequisites:
Found in Nightly 136.0a1 (2025-01-15)(64-bit)
Open a few tabs in Nightly
## STR:
1. Turn on NVDA
2. Open Firefox Nightly
3. Press `Ctrl` + `L` to move focus into the URL bar
4. Use `Shift` + `TAB` to move focus to the active tab
5. Use `fn` + `Shift` + `F10` to open the context menu on the active tab
6. Use the `Down arrow` key to move focus to 'Add tab to New Group' and press `ENTER`
7. Observe NVDA output
## Expected / Actual:
At this time, NVDA states that the role of 'Create tab group' is menu and it should be role (See: [Tab Grouping Spec Figma](https://www.figma.com/design/f6J2lH6XDxLxyzOLr2E8oE/Tab-Grouping-Spec?node-id=9958-35451&t=tbTTriMm0ARVLAjq-4)). In addition, the dialog is missing an accessible name.
|
Dialog is missing name and correct role ## Prerequisites:
Found in Nightly 136.0a1 (2025-01-15)(64-bit)
Open a few tabs in Nightly
## STR:
1. Turn on NVDA
2. Open Firefox Nightly
3. Press `Ctrl` + `L` to move focus into the URL bar
4. Use `Shift` + `TAB` to move focus to the active tab
5. Use `fn` + `Shift` + `F10` to open the context menu on the active tab
6. Use the `Down arrow` key to move focus to 'Add tab to New Group' and press `ENTER`
7. Observe NVDA output
## Expected / Actual:
At this time, NVDA states that the role of 'Create tab group' is menu and it should be role (See: [Tab Grouping Spec Figma](https://www.figma.com/design/f6J2lH6XDxLxyzOLr2E8oE/Tab-Grouping-Spec?node-id=9958-35451&t=tbTTriMm0ARVLAjq-4)). In addition, the dialog is missing an accessible name.
|
P1
|
VERIFIED
|
FIXED
|
2025-01-16 20:17:07+00:00
|
2025-02-06 16:49:45+00:00
| 274
| 1
|
1942157
|
can't use keyboard to navigate history sidebar
|
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
Open history sidebar using cmd-shift-h
Attempting to use tab and shift-tab to navigate history sidebar.
Can't progress past first entry or use enter to open.
Actual results:
Elements in webpage are highlighted instead.
Expected results:
Would be helpful to be able to navigate history without using mouse
|
can't use keyboard to navigate history sidebar User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
Open history sidebar using cmd-shift-h
Attempting to use tab and shift-tab to navigate history sidebar.
Can't progress past first entry or use enter to open.
Actual results:
Elements in webpage are highlighted instead.
Expected results:
Would be helpful to be able to navigate history without using mouse
|
P3
|
UNCONFIRMED
|
2025-01-16 20:21:23+00:00
|
2025-02-11 10:49:20+00:00
| 120
| 3
|
|
1942170
|
Radio button group is missing labels
|
## Prerequisites:
Found in Nightly 136.0a1 (2025-01-15)(64-bit)
Open a few tabs in Nightly
## STR:
1. Turn on NVDA
2. Open Firefox Nightly
3. Press `Ctrl` + `L` to move focus into the URL bar
4. Use `Shift` + `TAB` to move focus to the active tab
5. Use `fn` + `Shift` + `F10` to open the context menu on the active tab
6. Use the `Down arrow` key to move focus to 'Add tab to New Group' and press `ENTER`
7. Use `TAB` to move focus to the group of color radio buttons, observe NVDA output
## Expected / Actual:
The group of color radio buttons needs a label that explains the purpose of the group
|
Radio button group is missing labels ## Prerequisites:
Found in Nightly 136.0a1 (2025-01-15)(64-bit)
Open a few tabs in Nightly
## STR:
1. Turn on NVDA
2. Open Firefox Nightly
3. Press `Ctrl` + `L` to move focus into the URL bar
4. Use `Shift` + `TAB` to move focus to the active tab
5. Use `fn` + `Shift` + `F10` to open the context menu on the active tab
6. Use the `Down arrow` key to move focus to 'Add tab to New Group' and press `ENTER`
7. Use `TAB` to move focus to the group of color radio buttons, observe NVDA output
## Expected / Actual:
The group of color radio buttons needs a label that explains the purpose of the group
|
P1
|
VERIFIED
|
FIXED
|
2025-01-16 21:10:03+00:00
|
2025-02-06 13:59:08+00:00
| 191
| 1
|
1942176
|
'Manage tab group' dialog cannot be accessed by keyboard via context menu key
|
## Prerequisites:
Found in Nightly 136.0a1 (2025-01-15)(64-bit)
Open a few tabs in Nightly and create a tab group
## STR:
1. Open Firefox Nightly
2. Press `Ctrl` + `L` to move focus into the URL bar
3. Use `Shift` + `TAB` to move focus to the active tab
4. Press the `Left arrow` key to move focus to the tab group button
5. Use `fn` + `Shift` + `F10` to open the context menu on the active tab
## Expected / Actual:
Mouse users are able to right click on the tab group button and open the 'Manage tab group' dialog. Keyboard-only users cannot. When using the key combination to 'right-click' on the tab group button, the tab context menu opens, not the 'Manage tab group' dialog.
[Link to screen recording of issue (no audio)](https://drive.google.com/file/d/1yBf_ezT0NxV_vMFYZYRIMX237OI8Rg50/view?usp=sharing)
|
'Manage tab group' dialog cannot be accessed by keyboard via context menu key ## Prerequisites:
Found in Nightly 136.0a1 (2025-01-15)(64-bit)
Open a few tabs in Nightly and create a tab group
## STR:
1. Open Firefox Nightly
2. Press `Ctrl` + `L` to move focus into the URL bar
3. Use `Shift` + `TAB` to move focus to the active tab
4. Press the `Left arrow` key to move focus to the tab group button
5. Use `fn` + `Shift` + `F10` to open the context menu on the active tab
## Expected / Actual:
Mouse users are able to right click on the tab group button and open the 'Manage tab group' dialog. Keyboard-only users cannot. When using the key combination to 'right-click' on the tab group button, the tab context menu opens, not the 'Manage tab group' dialog.
[Link to screen recording of issue (no audio)](https://drive.google.com/file/d/1yBf_ezT0NxV_vMFYZYRIMX237OI8Rg50/view?usp=sharing)
|
P1
|
VERIFIED
|
FIXED
|
2025-01-16 21:30:23+00:00
|
2025-02-06 13:30:49+00:00
| 273
| 1
|
1942303
|
The chevron arrow from the overflow menu is not in the correct position after clicking restore defaults while the vertical tabs is enabled
|
**Found in**
* 136.0a1 (2025-01-16)
**Affected versions**
* 136.0a1 (2025-01-16)
* 135.0b5
* 134.0.1
**Tested platforms**
* Affected platforms: Windows 10x64, macOS 12, Ubuntu 24
* Unaffected platforms: none
**Steps to reproduce**
1. Enable sidebar and vertical tabs.
2. Open the Customize menu and click the restore defaults button.
****Expected result****
* The overflow menu chevron arrow is in the correct position.
**Actual result**
* The overflow menu chevron arrow is not in the correct position.
**Regression range**
* pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b17f4d3142eeb0488513b984c8f5113e80101b96&tochange=82dacb5e3821fc0081deed13bd932839d65867e0
**Additional notes**
* Attached a screen recording.
|
The chevron arrow from the overflow menu is not in the correct position after clicking restore defaults while the vertical tabs is enabled **Found in**
* 136.0a1 (2025-01-16)
**Affected versions**
* 136.0a1 (2025-01-16)
* 135.0b5
* 134.0.1
**Tested platforms**
* Affected platforms: Windows 10x64, macOS 12, Ubuntu 24
* Unaffected platforms: none
**Steps to reproduce**
1. Enable sidebar and vertical tabs.
2. Open the Customize menu and click the restore defaults button.
****Expected result****
* The overflow menu chevron arrow is in the correct position.
**Actual result**
* The overflow menu chevron arrow is not in the correct position.
**Regression range**
* pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b17f4d3142eeb0488513b984c8f5113e80101b96&tochange=82dacb5e3821fc0081deed13bd932839d65867e0
**Additional notes**
* Attached a screen recording.
|
P3
|
NEW
|
2025-01-17 13:31:37+00:00
|
2025-02-10 19:06:05+00:00
| 294
| 3
|
|
1942307
|
Typing "gm" in the address-bar does not highlight "gmail.com" since a few days
|
In my usual firefox profile, type "gm" in the address-bar.
AR: gmail.com is not highlighted / auto-selected
ER: IT should. It used to till a couple of days back.
:mak, ni? you as you have looked at similar issue in the past. Thanks.
|
Typing "gm" in the address-bar does not highlight "gmail.com" since a few days In my usual firefox profile, type "gm" in the address-bar.
AR: gmail.com is not highlighted / auto-selected
ER: IT should. It used to till a couple of days back.
:mak, ni? you as you have looked at similar issue in the past. Thanks.
|
P3
|
NEW
|
2025-01-17 13:56:29+00:00
|
2025-01-24 02:22:00+00:00
| 90
| 3
|
|
1942314
|
Sidebar still showing on popup windows when sidebar.revamp is on
|
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
1. Enable sidebar.revamp
2. Open a webside which can generate popup windows (e.g. Ingress Intel Map)
3. Open up a popup window (e.g. click Login with Google)
Actual results:
Sidebar buttons still showing on popup windows when sidebar.revamp is on. Screenshot attached.
Expected results:
No sidebar buttons.
|
Sidebar still showing on popup windows when sidebar.revamp is on User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
1. Enable sidebar.revamp
2. Open a webside which can generate popup windows (e.g. Ingress Intel Map)
3. Open up a popup window (e.g. click Login with Google)
Actual results:
Sidebar buttons still showing on popup windows when sidebar.revamp is on. Screenshot attached.
Expected results:
No sidebar buttons.
|
P1
|
VERIFIED
|
FIXED
|
2025-01-17 14:35:36+00:00
|
2025-02-11 13:02:31+00:00
| 143
| 1
|
1942332
|
Creating groups by dragging and dropping a card onto another card is extremely inconvenient and creates groups against my intention.
|
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
I am testing the tab grouping feature, so I have it enabled.
While rearranging tabs on the tab bar, I do not intend to create groups.
Actual results:
When simply dragging tabs on the tab bar, I have accidentally created tab groups multiple times. This goes against my intention. I did not want to create a tab group, only to move a tab!
Expected results:
The feature of creating tab groups by dragging and dropping one tab onto another should be entirely disabled. This behavior is highly unintuitive and poorly designed.
I am not sure if it can be implemented in a better way, but what is currently in place (even during testing) is simply a very bad solution.
Tab groups are a dream feature, but creating groups via drag and drop is absolutely unbearable.
|
Creating groups by dragging and dropping a card onto another card is extremely inconvenient and creates groups against my intention. User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
I am testing the tab grouping feature, so I have it enabled.
While rearranging tabs on the tab bar, I do not intend to create groups.
Actual results:
When simply dragging tabs on the tab bar, I have accidentally created tab groups multiple times. This goes against my intention. I did not want to create a tab group, only to move a tab!
Expected results:
The feature of creating tab groups by dragging and dropping one tab onto another should be entirely disabled. This behavior is highly unintuitive and poorly designed.
I am not sure if it can be implemented in a better way, but what is currently in place (even during testing) is simply a very bad solution.
Tab groups are a dream feature, but creating groups via drag and drop is absolutely unbearable.
|
P1
|
RESOLVED
|
FIXED
|
2025-01-17 16:25:51+00:00
|
2025-02-25 09:33:22+00:00
| 230
| 1
|
1942347
|
Disable "Move group to new window" if group is already in a new window
|
**Steps to reproduce [can add screenshots or video recordings for reference]:**
1. Create a tab group "Shopping" in Window 1 (ensure there are other ungrouped tabs on the tab strip) and save and close it
2. Go to Tab groups in the TOM menu
3. Right-click on "Shopping" and select "Open group in new window"
4. Go back to Window 1 and right-click on "Shopping" in the TOM menu again
**Expected behavior [What should have happened?]:**
"Move tab to New Window" should be disabled since it is already in a new window with no other tabs on the tab strip
**Actual behavior [What actually happened?]:**
"Move tab to New Window" is not disabled so it closes the window and reopens another new window
|
Disable "Move group to new window" if group is already in a new window **Steps to reproduce [can add screenshots or video recordings for reference]:**
1. Create a tab group "Shopping" in Window 1 (ensure there are other ungrouped tabs on the tab strip) and save and close it
2. Go to Tab groups in the TOM menu
3. Right-click on "Shopping" and select "Open group in new window"
4. Go back to Window 1 and right-click on "Shopping" in the TOM menu again
**Expected behavior [What should have happened?]:**
"Move tab to New Window" should be disabled since it is already in a new window with no other tabs on the tab strip
**Actual behavior [What actually happened?]:**
"Move tab to New Window" is not disabled so it closes the window and reopens another new window
|
P3
|
RESOLVED
|
FIXED
|
2025-01-17 17:32:30+00:00
|
2025-03-05 13:31:13+00:00
| 195
| 3
|
1942375
|
Tab overflow menu: UI desync when changes are made to other windows
|
When you delete a group that is open in another window by right clicking it in the TOM, the group is deleted in the other window but it is still shown in the TOM UI.
|
Tab overflow menu: UI desync when changes are made to other windows When you delete a group that is open in another window by right clicking it in the TOM, the group is deleted in the other window but it is still shown in the TOM UI.
|
P1
|
RESOLVED
|
FIXED
|
2025-01-17 20:11:27+00:00
|
2025-03-05 13:32:09+00:00
| 56
| 1
|
1942393
|
Context menu order is not consistent between opened/closed tab groups
|
**Steps to reproduce [can add screenshots or video recordings for reference]:**
1. Create a tab group "Cooking" in a new window
2. Open another new window and go to the TOM menu and right-click on the tab group "Cooking"
**Expected behavior [What should have happened?]:**
The context menu ordering should be consistent between Opened and Closed tab groups
**Actual behavior [What actually happened?]:**
Opened group context menu
1. Open Group in This Window
2. Open Group in New Window
3. Delete Group
Closed group context menu
1. Move Group to New Window
2. Move Group to This Window
3. Delete Group
The context menu ordering is not consistent between Opened and Closed tab groups
Opened group context menu
1. Open Group in This Window
2. Open Group in New Window
3. Delete Group
Closed group context menu
1. Move Group to This Window
2. Move Group to New Window
3. Delete Group
|
Context menu order is not consistent between opened/closed tab groups **Steps to reproduce [can add screenshots or video recordings for reference]:**
1. Create a tab group "Cooking" in a new window
2. Open another new window and go to the TOM menu and right-click on the tab group "Cooking"
**Expected behavior [What should have happened?]:**
The context menu ordering should be consistent between Opened and Closed tab groups
**Actual behavior [What actually happened?]:**
Opened group context menu
1. Open Group in This Window
2. Open Group in New Window
3. Delete Group
Closed group context menu
1. Move Group to New Window
2. Move Group to This Window
3. Delete Group
The context menu ordering is not consistent between Opened and Closed tab groups
Opened group context menu
1. Open Group in This Window
2. Open Group in New Window
3. Delete Group
Closed group context menu
1. Move Group to This Window
2. Move Group to New Window
3. Delete Group
|
P3
|
RESOLVED
|
FIXED
|
2025-01-17 21:52:38+00:00
|
2025-03-05 13:34:42+00:00
| 215
| 3
|
1942409
|
Missing list of supported sites in non PDP empty state
|
I messed up a rebase and forgot to pass in our [supported domains object ](https://searchfox.org/mozilla-central/rev/2966caf8129d1a0d6a382b5d851456169f1081f8/browser/components/shopping/ReviewCheckerChild.sys.mjs#401) as a param in the [updateLocation function definition](https://searchfox.org/mozilla-central/rev/2966caf8129d1a0d6a382b5d851456169f1081f8/browser/components/shopping/ReviewCheckerChild.sys.mjs#659). Let's add the `supportedDomains` object as a param so that we can correctly render the list of sites.
Edit: perhaps we can add some tests to ensure the domains object is always passed.
|
Missing list of supported sites in non PDP empty state I messed up a rebase and forgot to pass in our [supported domains object ](https://searchfox.org/mozilla-central/rev/2966caf8129d1a0d6a382b5d851456169f1081f8/browser/components/shopping/ReviewCheckerChild.sys.mjs#401) as a param in the [updateLocation function definition](https://searchfox.org/mozilla-central/rev/2966caf8129d1a0d6a382b5d851456169f1081f8/browser/components/shopping/ReviewCheckerChild.sys.mjs#659). Let's add the `supportedDomains` object as a param so that we can correctly render the list of sites.
Edit: perhaps we can add some tests to ensure the domains object is always passed.
|
P1
|
RESOLVED
|
FIXED
|
2025-01-17 23:47:41+00:00
|
2025-01-22 04:42:24+00:00
| 226
| 1
|
1942435
|
Dismissals don't work for Merino suggestions without Suggest features
|
Bug 1941100 regressed this: It removed dismissal handling from `UrlbarProviderQuickSuggest` because I thought it wasn't necessary, but that code path was also used for suggestions that don't have a Suggest feature, e.g., Merino suggestions like dynamic Wikipedia and navigational suggestions.
|
Dismissals don't work for Merino suggestions without Suggest features Bug 1941100 regressed this: It removed dismissal handling from `UrlbarProviderQuickSuggest` because I thought it wasn't necessary, but that code path was also used for suggestions that don't have a Suggest feature, e.g., Merino suggestions like dynamic Wikipedia and navigational suggestions.
|
P1
|
RESOLVED
|
FIXED
|
2025-01-18 06:06:52+00:00
|
2025-01-21 21:33:18+00:00
| 83
| 1
|
1942513
|
Mozilla Firefox shows repeated in default apps
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
If I search for Firefox in Default Apps, it shows up 2 times, I can mark any of them as my default browser but it doesn't work it keeps saying that Firefox is not the default browser. In the Installed apps section in settings, only shows up once.
If I restart the app, it doesn't fixes it, it keeps showing up 2 times, if I uninstall and reinstall, it shows up fine for a couple of days, then it shows up doubled again.
https://imgur.com/a/ppQLf35
Actual results:
If I restart the app, it doesn't fixes it, it keeps showing up 2 times, if I uninstall and reinstall, it shows up fine for a couple of days, then it shows up doubled again.
Expected results:
App should show up only once in default apps
|
Mozilla Firefox shows repeated in default apps User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
If I search for Firefox in Default Apps, it shows up 2 times, I can mark any of them as my default browser but it doesn't work it keeps saying that Firefox is not the default browser. In the Installed apps section in settings, only shows up once.
If I restart the app, it doesn't fixes it, it keeps showing up 2 times, if I uninstall and reinstall, it shows up fine for a couple of days, then it shows up doubled again.
https://imgur.com/a/ppQLf35
Actual results:
If I restart the app, it doesn't fixes it, it keeps showing up 2 times, if I uninstall and reinstall, it shows up fine for a couple of days, then it shows up doubled again.
Expected results:
App should show up only once in default apps
|
P3
|
NEW
|
2025-01-19 12:36:33+00:00
|
2025-02-25 01:03:52+00:00
| 246
| 3
|
|
1942840
|
After Firefox restart, with the option of "open previous windows and tabs", clicking on an unloaded tab should show its URL from the start
|
STR:
1. Have a firefox session with a few tabs loaded.
2. Make sure that the option "Startup" > "open previous windows and tabs" is enabled.
3. Restart Firefox.
4. Click on some of the tabs that are unloaded.
=> There is a more or less brief period of time before the URL is displayed. The period depends on the network condition (maybe DNS?).
It seems to be Desktop only, Android seems to be OK.
(Firefox v136 20250121034512, but I believe it is a long-standing issue, not a recent problem)
|
After Firefox restart, with the option of "open previous windows and tabs", clicking on an unloaded tab should show its URL from the start STR:
1. Have a firefox session with a few tabs loaded.
2. Make sure that the option "Startup" > "open previous windows and tabs" is enabled.
3. Restart Firefox.
4. Click on some of the tabs that are unloaded.
=> There is a more or less brief period of time before the URL is displayed. The period depends on the network condition (maybe DNS?).
It seems to be Desktop only, Android seems to be OK.
(Firefox v136 20250121034512, but I believe it is a long-standing issue, not a recent problem)
|
P3
|
NEW
|
2025-01-21 15:58:27+00:00
|
2025-01-27 16:49:58+00:00
| 173
| 3
|
|
1942925
|
Updating identity.fxaccounts.autoconfig.uri only applies the fetched configuration after starting a sign-in flow
|
### Steps to reproduce
1. Start a fresh profile.
2. Go to `about:config` and update:
- `identity.fxaccounts.autoconfig.uri` to `https://accounts.stage.mozaws.net`.
- `services.sync.log.appender.console` to `Debug`.
3. Restart the browser.
4. Open the browser console to observe for `Got successful configuration response` in next step.
- ```
1737492268477 FirefoxAccounts DEBUG Got successful configuration response: {"auth_server_base_url":"https://api-accounts.stage.mozaws.net","oauth_server_base_url":"https://oauth.stage.mozaws.net","pairing_server_base_uri":"wss://stage.channelserver.nonprod.cloudops.mozgcp.net","profile_server_base_url":"https://profile.stage.mozaws.net","sync_tokenserver_base_url":"https://token.stage.mozaws.net"}
```
5. Start a sync sign-in flow from the FxA menu.
6. Continue the sign-in process until completion.
### Expected behaviour
- At step 5, all requests should be made to the newly received configuration.
- Sign-in from the FxA Menu is successful.
### Actual behaviour
- At step 5, we make requests to the previous configuration instead (e.g. `https://api.accounts.firefox.com/v1/account/device` instead of `https://api-accounts.stage.mozaws.net/v1/account/device`)
### Additional notes
- ⚠️ This bug is not reproducible if step 5 uses `about:preferences#sync` to start the sign-in flow.
|
Updating identity.fxaccounts.autoconfig.uri only applies the fetched configuration after starting a sign-in flow ### Steps to reproduce
1. Start a fresh profile.
2. Go to `about:config` and update:
- `identity.fxaccounts.autoconfig.uri` to `https://accounts.stage.mozaws.net`.
- `services.sync.log.appender.console` to `Debug`.
3. Restart the browser.
4. Open the browser console to observe for `Got successful configuration response` in next step.
- ```
1737492268477 FirefoxAccounts DEBUG Got successful configuration response: {"auth_server_base_url":"https://api-accounts.stage.mozaws.net","oauth_server_base_url":"https://oauth.stage.mozaws.net","pairing_server_base_uri":"wss://stage.channelserver.nonprod.cloudops.mozgcp.net","profile_server_base_url":"https://profile.stage.mozaws.net","sync_tokenserver_base_url":"https://token.stage.mozaws.net"}
```
5. Start a sync sign-in flow from the FxA menu.
6. Continue the sign-in process until completion.
### Expected behaviour
- At step 5, all requests should be made to the newly received configuration.
- Sign-in from the FxA Menu is successful.
### Actual behaviour
- At step 5, we make requests to the previous configuration instead (e.g. `https://api.accounts.firefox.com/v1/account/device` instead of `https://api-accounts.stage.mozaws.net/v1/account/device`)
### Additional notes
- ⚠️ This bug is not reproducible if step 5 uses `about:preferences#sync` to start the sign-in flow.
|
P3
|
NEW
|
2025-01-21 21:07:25+00:00
|
2025-02-13 18:57:17+00:00
| 488
| 3
|
|
1943032
|
Properly localize tab groups' aria-label and aria-description
|
These are currently hardcoded English and should be localized instead: https://searchfox.org/mozilla-central/rev/ef34dd879ef8d4a0f3d68d371d23caebcd8fef65/browser/components/tabbrowser/content/tabgroup.js#185-186
|
Properly localize tab groups' aria-label and aria-description These are currently hardcoded English and should be localized instead: https://searchfox.org/mozilla-central/rev/ef34dd879ef8d4a0f3d68d371d23caebcd8fef65/browser/components/tabbrowser/content/tabgroup.js#185-186
|
P1
|
RESOLVED
|
FIXED
|
2025-01-22 12:57:14+00:00
|
2025-02-25 21:38:19+00:00
| 96
| 1
|
1943147
|
No close button on sidebar of addon when sidebar.revamp = true
|
Steps to reproduce:
1. enable sidebar.revamp
2. install addon such as tree style tab/update scanner
3. open addon's sidebar
Actual results:
No close button on sidebar
Expected resukts:
Close button should be provided just like Bookmarks/History sidebar.
|
No close button on sidebar of addon when sidebar.revamp = true Steps to reproduce:
1. enable sidebar.revamp
2. install addon such as tree style tab/update scanner
3. open addon's sidebar
Actual results:
No close button on sidebar
Expected resukts:
Close button should be provided just like Bookmarks/History sidebar.
|
P2
|
NEW
|
2025-01-22 20:15:24+00:00
|
2025-01-23 17:49:40+00:00
| 81
| 2
|
|
1943160
|
PrefFlipsFeature initialized in child processes.
|
The ExperimentManager is [unconditionally initializing the Pref Flips Feature](https://searchfox.org/mozilla-central/rev/4f5426084651871759f5346eb0ded2e9ac5326fd/toolkit/components/nimbus/lib/ExperimentManager.sys.mjs#106), which should only run in the parent process. This means the feature is also running in the child process, where it cant really do anything and wastes resources.
|
PrefFlipsFeature initialized in child processes. The ExperimentManager is [unconditionally initializing the Pref Flips Feature](https://searchfox.org/mozilla-central/rev/4f5426084651871759f5346eb0ded2e9ac5326fd/toolkit/components/nimbus/lib/ExperimentManager.sys.mjs#106), which should only run in the parent process. This means the feature is also running in the child process, where it cant really do anything and wastes resources.
|
P3
|
NEW
|
2025-01-22 21:18:01+00:00
|
2025-02-07 14:40:47+00:00
| 137
| 3
|
|
1943319
|
The "Checking Review Quality (0%)" update message is displayed in the Firefox Sidebar Review Checker panel on a non PDP
|
**Found in**
* 136.0a1 (2025-01-23)
**Affected versions**
* 136.0a1 (2025-01-23)
**Preconditions**
Enable the Review Checker:
browser.shopping.experience2023.enabled - true
browser.shopping.experience2023.optedIn - 1
browser.shopping.experience2023.autoOpen.enabled - true
browser.shopping.experience2023.integratedSidebar - true
browser.shopping.experience2023.shoppingSidebar - false
**Affected platforms**
* all
**Steps to reproduce**
1. Reach an outdated product on amazon.com that has the Check Now button.
2. Click the Check now button and switch tabs to a non Product details page.
**Expected result**
* The "Checking Review Quality (0%)" update message should not be displayed in the Sidebar.
**Actual result**
* The "Checking Review Quality (0%)" update message is displayed on a non product details page.
**Regression range**
Not a regression
|
The "Checking Review Quality (0%)" update message is displayed in the Firefox Sidebar Review Checker panel on a non PDP **Found in**
* 136.0a1 (2025-01-23)
**Affected versions**
* 136.0a1 (2025-01-23)
**Preconditions**
Enable the Review Checker:
browser.shopping.experience2023.enabled - true
browser.shopping.experience2023.optedIn - 1
browser.shopping.experience2023.autoOpen.enabled - true
browser.shopping.experience2023.integratedSidebar - true
browser.shopping.experience2023.shoppingSidebar - false
**Affected platforms**
* all
**Steps to reproduce**
1. Reach an outdated product on amazon.com that has the Check Now button.
2. Click the Check now button and switch tabs to a non Product details page.
**Expected result**
* The "Checking Review Quality (0%)" update message should not be displayed in the Sidebar.
**Actual result**
* The "Checking Review Quality (0%)" update message is displayed on a non product details page.
**Regression range**
Not a regression
|
P2
|
VERIFIED
|
FIXED
|
2025-01-23 13:05:52+00:00
|
2025-02-13 13:55:52+00:00
| 262
| 2
|
1943326
|
Secondary Actions: Restart glean event telemetry ping not found/sent
|
**Found in**
* 136.0a1 (2024-01-22)
**Affected versions**
* 136.0a1 (2024-01-22)
**Tested platforms**
* Affected platforms: Windows 11, Mac 13, Ubuntu 24
**Preconditions:**
* Open about:glean and select events type pings.
**Steps to reproduce**
1. Type in address bar **restart**
2. Click on the **restart** secondary action.
3. Check the glean telemetry on [firebase](https://debug-ping-preview.firebaseapp.com).
**Expected result**
There are restart glean telemetry pings on [firebase](https://debug-ping-preview.firebaseapp.com).
**Actual result**
There are no restart glean telemetry pings on [firebase](https://debug-ping-preview.firebaseapp.com).
**Regression range**
* N/A - telemetry implemented recently
**Note**
- The **update** keyword also restarts firefox with the same above actual results: no telemetry pings - see bug 1928635
- Its possible that due to the fact that we are using about:glean manual testing options, the event pings for restart are not sent in due time, but better safe than sorry.
- Same situation for **Update** action with the note that Update action should not be available if no update is available to restart for.
|
Secondary Actions: Restart glean event telemetry ping not found/sent **Found in**
* 136.0a1 (2024-01-22)
**Affected versions**
* 136.0a1 (2024-01-22)
**Tested platforms**
* Affected platforms: Windows 11, Mac 13, Ubuntu 24
**Preconditions:**
* Open about:glean and select events type pings.
**Steps to reproduce**
1. Type in address bar **restart**
2. Click on the **restart** secondary action.
3. Check the glean telemetry on [firebase](https://debug-ping-preview.firebaseapp.com).
**Expected result**
There are restart glean telemetry pings on [firebase](https://debug-ping-preview.firebaseapp.com).
**Actual result**
There are no restart glean telemetry pings on [firebase](https://debug-ping-preview.firebaseapp.com).
**Regression range**
* N/A - telemetry implemented recently
**Note**
- The **update** keyword also restarts firefox with the same above actual results: no telemetry pings - see bug 1928635
- Its possible that due to the fact that we are using about:glean manual testing options, the event pings for restart are not sent in due time, but better safe than sorry.
- Same situation for **Update** action with the note that Update action should not be available if no update is available to restart for.
|
P2
|
NEW
|
2025-01-23 13:30:58+00:00
|
2025-01-27 16:51:16+00:00
| 369
| 2
|
|
1943370
|
Can't use arrow keys to move through awesomebar suggestions
|
I've noticed this a couple of times and it's pretty annoying. I'm pretty sure it's a regression.
I've attached a screenrecording of me hitting the down arrow key a bunch and it skipping over a bunch of items.
|
Can't use arrow keys to move through awesomebar suggestions I've noticed this a couple of times and it's pretty annoying. I'm pretty sure it's a regression.
I've attached a screenrecording of me hitting the down arrow key a bunch and it skipping over a bunch of items.
|
P3
|
NEW
|
2025-01-23 16:07:00+00:00
|
2025-02-24 20:57:31+00:00
| 68
| 3
|
|
1943498
|
Avoid setting the active pref when using the migrated sidebar
|
In the current RC, we determine visibility via our active pref. In the migrated RC, visibility is instead determined by `SidebarController`. We don't want to unnecessarily update the pref with the migrated RC if it's inapplicable.
We update the pref here: https://searchfox.org/mozilla-central/rev/55706b888f91fffa6f045f7cbc1a7b1c34598292/browser/components/shopping/content/settings.mjs#56-58
It's possible that I missed more cases when the active pref is set and we forget to check for the integratedSidebar pref. Let's double check for such cases when fixing the bug.
|
Avoid setting the active pref when using the migrated sidebar In the current RC, we determine visibility via our active pref. In the migrated RC, visibility is instead determined by `SidebarController`. We don't want to unnecessarily update the pref with the migrated RC if it's inapplicable.
We update the pref here: https://searchfox.org/mozilla-central/rev/55706b888f91fffa6f045f7cbc1a7b1c34598292/browser/components/shopping/content/settings.mjs#56-58
It's possible that I missed more cases when the active pref is set and we forget to check for the integratedSidebar pref. Let's double check for such cases when fixing the bug.
|
P2
|
NEW
|
2025-01-24 01:30:11+00:00
|
2025-02-05 21:58:08+00:00
| 189
| 2
|
|
1943499
|
Intermittent browser/components/search/test/browser/telemetry/browser_search_glean_serp_event_telemetry_categorization_enabled_by_pref.js | single tracking bug
|
**Filed by:** sstanca [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=491528826&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/TjyROdVmRlu8JQrFAa2xAA/runs/0/artifacts/public/logs/live_backing.log
---
```
[task 2025-01-23T23:46:10.324Z] 23:46:10 INFO - TEST-PASS | browser/components/search/test/browser/telemetry/browser_search_glean_serp_event_telemetry_categorization_enabled_by_pref.js | serpEventsCategorizationEnabled should be true when the pref is true. - true == true -
[task 2025-01-23T23:46:10.325Z] 23:46:10 INFO - Load a sample SERP with organic results.
[task 2025-01-23T23:46:10.325Z] 23:46:10 INFO - Buffered messages finished
[task 2025-01-23T23:46:10.326Z] 23:46:10 INFO - TEST-UNEXPECTED-FAIL | browser/components/search/test/browser/telemetry/browser_search_glean_serp_event_telemetry_categorization_enabled_by_pref.js | Test timed out -
[task 2025-01-23T23:46:10.327Z] 23:46:10 INFO - GECKO(920) | Completed ShutdownLeaks collections in process 920
[task 2025-01-23T23:46:10.327Z] 23:46:10 INFO - TEST-START | Shutdown
```
|
Intermittent browser/components/search/test/browser/telemetry/browser_search_glean_serp_event_telemetry_categorization_enabled_by_pref.js | single tracking bug **Filed by:** sstanca [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=491528826&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/TjyROdVmRlu8JQrFAa2xAA/runs/0/artifacts/public/logs/live_backing.log
---
```
[task 2025-01-23T23:46:10.324Z] 23:46:10 INFO - TEST-PASS | browser/components/search/test/browser/telemetry/browser_search_glean_serp_event_telemetry_categorization_enabled_by_pref.js | serpEventsCategorizationEnabled should be true when the pref is true. - true == true -
[task 2025-01-23T23:46:10.325Z] 23:46:10 INFO - Load a sample SERP with organic results.
[task 2025-01-23T23:46:10.325Z] 23:46:10 INFO - Buffered messages finished
[task 2025-01-23T23:46:10.326Z] 23:46:10 INFO - TEST-UNEXPECTED-FAIL | browser/components/search/test/browser/telemetry/browser_search_glean_serp_event_telemetry_categorization_enabled_by_pref.js | Test timed out -
[task 2025-01-23T23:46:10.327Z] 23:46:10 INFO - GECKO(920) | Completed ShutdownLeaks collections in process 920
[task 2025-01-23T23:46:10.327Z] 23:46:10 INFO - TEST-START | Shutdown
```
|
P5
|
NEW
|
2025-01-24 01:36:22+00:00
|
2025-03-03 06:44:30+00:00
| 499
| 5
|
|
1943589
|
Can't drag a tab from another window into a group
|
STR
1. Have tab groups enabled
2. In a browser window, set up an open tab group with at least two tabs.
3. Open a new window, and open a couple of tabs and load pages.
4. Attempt to drag one of the tabs into the middle of the group in the first window.
Expected Results
The tab is added to the group and placed in location where you dropped it.
Actual Results
The tab is not added to the group, instead it is inserted into the window before the start of the tab group.
|
Can't drag a tab from another window into a group STR
1. Have tab groups enabled
2. In a browser window, set up an open tab group with at least two tabs.
3. Open a new window, and open a couple of tabs and load pages.
4. Attempt to drag one of the tabs into the middle of the group in the first window.
Expected Results
The tab is added to the group and placed in location where you dropped it.
Actual Results
The tab is not added to the group, instead it is inserted into the window before the start of the tab group.
|
P2
|
RESOLVED
|
FIXED
|
2025-01-24 14:09:38+00:00
|
2025-03-05 07:06:27+00:00
| 125
| 2
|
1943635
|
Color options on the tab group panel lack tooltips
|
The color options have accessible names that provide a clarity for users of assistive technology on what are the options and how to refer to them. But for the users without assistive technology, including users with cognitive and developmental disabilities, low vision, or users who are less proficient in English and the color names, there is no visual reference beyond the color of the item. For instance, the "cyan" may not be as apparent of a choice of the color name.
Since assistive technology like Voice Access (Win) would be able to ask the tool to show the names, they would be able to call them to activate, it could still be beneficial for users without any assistive tech to preview the name of the color. For instance, a user with color deficiency may clarify which color they would like to select, while helping their less tech savvy friend to set up their tab groups.
|
Color options on the tab group panel lack tooltips The color options have accessible names that provide a clarity for users of assistive technology on what are the options and how to refer to them. But for the users without assistive technology, including users with cognitive and developmental disabilities, low vision, or users who are less proficient in English and the color names, there is no visual reference beyond the color of the item. For instance, the "cyan" may not be as apparent of a choice of the color name.
Since assistive technology like Voice Access (Win) would be able to ask the tool to show the names, they would be able to call them to activate, it could still be beneficial for users without any assistive tech to preview the name of the color. For instance, a user with color deficiency may clarify which color they would like to select, while helping their less tech savvy friend to set up their tab groups.
|
P1
|
VERIFIED
|
FIXED
|
2025-01-24 17:11:13+00:00
|
2025-02-10 10:02:33+00:00
| 193
| 1
|
1943651
|
Survey X icon z-index is higher than the shopping-container sticky header
|
STR:
1. Make sure to set these prefs as the following:
- browser.shopping.experience2023.survey.enabled = true
- browser.shopping.experience2023.survey.hasSeen = false
- browser.shopping.experience2023.survey.optedInTime to a smaller integer value (ex. 100) for the sake of testing
- browser.shopping.experience2023.survey.pdpVisits = 5
2. Then, go to a PDP that already has analysis results (ex. https://www.amazon.com/dp/B08D66HCXW)
3. The survey should then hopefully appear on Review Checker
4. Scroll down so that the survey is close to the top of the Review Checker container
Expected:
Survey X icon should be underneath the Review Checker header
Actual:
Survey X icon is above the header and is too close to the container's own X icon
|
Survey X icon z-index is higher than the shopping-container sticky header STR:
1. Make sure to set these prefs as the following:
- browser.shopping.experience2023.survey.enabled = true
- browser.shopping.experience2023.survey.hasSeen = false
- browser.shopping.experience2023.survey.optedInTime to a smaller integer value (ex. 100) for the sake of testing
- browser.shopping.experience2023.survey.pdpVisits = 5
2. Then, go to a PDP that already has analysis results (ex. https://www.amazon.com/dp/B08D66HCXW)
3. The survey should then hopefully appear on Review Checker
4. Scroll down so that the survey is close to the top of the Review Checker container
Expected:
Survey X icon should be underneath the Review Checker header
Actual:
Survey X icon is above the header and is too close to the container's own X icon
|
P2
|
RESOLVED
|
FIXED
|
2025-01-24 18:09:53+00:00
|
2025-03-04 05:01:36+00:00
| 213
| 2
|
1943657
|
Keep closed message appears on opt-in UI empty state after turning off RC
|
STR:
1. For the sake of testing, set these prefs:
- browser.shopping.experience2023.showKeepSidebarClosedMessage = true
- browser.shopping.experience2023.survey.pdpVisits = 5
- browser.shopping.experience2023.autoOpen.enabled = true
- browser.shopping.experience2023.autoOpen.userEnabled = true
2. On a PDP, close RC using the X icon
3. The "keep closed" message should appear in RC
4. Instead of interacting with the message, go to the settings card and press the "turn off" button
Expected:
- The "keep closed" message disappears when the empty state is rendered
Actual:
- The "keep closed" message remains when the empty state is rendered
Notes:
- We render the message as a litelement template in our shopping-container: https://searchfox.org/mozilla-central/rev/f41e8cacb8e8ce254204e2526e98d49d024f1674/browser/components/shopping/content/shopping-container.mjs#599-612. Currently, we rely on a `showingKeepClosedMessage`, and we do not actually check the value of the `showKeepSidebarClosedMessage` pref again after opt-out.
- I'm curious if we can pass in `showingKeepClosedMessage: false` when we [detect the optIn state change and try to clear content](https://searchfox.org/mozilla-central/rev/f41e8cacb8e8ce254204e2526e98d49d024f1674/browser/components/shopping/ReviewCheckerChild.sys.mjs#262). The [reset function](https://searchfox.org/mozilla-central/rev/f41e8cacb8e8ce254204e2526e98d49d024f1674/browser/components/shopping/ReviewCheckerChild.sys.mjs#608-617) passes in several props to the shopping-container.
|
Keep closed message appears on opt-in UI empty state after turning off RC STR:
1. For the sake of testing, set these prefs:
- browser.shopping.experience2023.showKeepSidebarClosedMessage = true
- browser.shopping.experience2023.survey.pdpVisits = 5
- browser.shopping.experience2023.autoOpen.enabled = true
- browser.shopping.experience2023.autoOpen.userEnabled = true
2. On a PDP, close RC using the X icon
3. The "keep closed" message should appear in RC
4. Instead of interacting with the message, go to the settings card and press the "turn off" button
Expected:
- The "keep closed" message disappears when the empty state is rendered
Actual:
- The "keep closed" message remains when the empty state is rendered
Notes:
- We render the message as a litelement template in our shopping-container: https://searchfox.org/mozilla-central/rev/f41e8cacb8e8ce254204e2526e98d49d024f1674/browser/components/shopping/content/shopping-container.mjs#599-612. Currently, we rely on a `showingKeepClosedMessage`, and we do not actually check the value of the `showKeepSidebarClosedMessage` pref again after opt-out.
- I'm curious if we can pass in `showingKeepClosedMessage: false` when we [detect the optIn state change and try to clear content](https://searchfox.org/mozilla-central/rev/f41e8cacb8e8ce254204e2526e98d49d024f1674/browser/components/shopping/ReviewCheckerChild.sys.mjs#262). The [reset function](https://searchfox.org/mozilla-central/rev/f41e8cacb8e8ce254204e2526e98d49d024f1674/browser/components/shopping/ReviewCheckerChild.sys.mjs#608-617) passes in several props to the shopping-container.
|
P2
|
NEW
|
2025-01-24 18:34:43+00:00
|
2025-02-07 02:39:11+00:00
| 510
| 2
|
|
1943687
|
When topic management panel is enabled, toggling sections requires a page refresh
|
### Setup:
Set the follow prefs to `true`:
- `browser.newtabpage.activity-stream.discoverystream.sections.personalization.enabled`
- `browser.newtabpage.activity-stream.discoverystream.sections.customizeMenuPanel.enabled`
- `browser.newtabpage.activity-stream.discoverystream.sections.cards.enabled`
### Steps to reproduce:
- Open up a new tab
- Either enable or disable Sections via about:config
- `browser.newtabpage.activity-stream.discoverystream.sections.enabled`
- Look at new tab page
- **Expected**: Should show/not show sections layout
- **Actual**: Displays Oops, something went wrong loading this content. message and requires page refresh
Error:
```
TypeError: can't access property "components", state.DiscoveryStream.layout[0] is undefined
```
I suspect there's some if..else logic not being set correctly here:
https://searchfox.org/mozilla-central/source/browser/components/newtab/content-src/components/CustomizeMenu/SectionsMgmtPanel/SectionsMgmtPanel.jsx#38-52
|
When topic management panel is enabled, toggling sections requires a page refresh ### Setup:
Set the follow prefs to `true`:
- `browser.newtabpage.activity-stream.discoverystream.sections.personalization.enabled`
- `browser.newtabpage.activity-stream.discoverystream.sections.customizeMenuPanel.enabled`
- `browser.newtabpage.activity-stream.discoverystream.sections.cards.enabled`
### Steps to reproduce:
- Open up a new tab
- Either enable or disable Sections via about:config
- `browser.newtabpage.activity-stream.discoverystream.sections.enabled`
- Look at new tab page
- **Expected**: Should show/not show sections layout
- **Actual**: Displays Oops, something went wrong loading this content. message and requires page refresh
Error:
```
TypeError: can't access property "components", state.DiscoveryStream.layout[0] is undefined
```
I suspect there's some if..else logic not being set correctly here:
https://searchfox.org/mozilla-central/source/browser/components/newtab/content-src/components/CustomizeMenu/SectionsMgmtPanel/SectionsMgmtPanel.jsx#38-52
|
P2
|
RESOLVED
|
FIXED
|
2025-01-24 21:06:27+00:00
|
2025-01-25 09:43:15+00:00
| 297
| 2
|
1943814
|
Opening link in new tab won't show next to your current tab after moving tab with Ctrl+Shift+Page Up/Down.
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
1. Open any link in new tab using the context menu or by middle clicking.
2. Move your current tab to the right with Ctrl+Shift+Page Down.
3. Open any link in new tab again.
Actual results:
The newly opened tab showed up next to the previously opened tab.
Expected results:
New tab show up next to your current tab.
|
Opening link in new tab won't show next to your current tab after moving tab with Ctrl+Shift+Page Up/Down. User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
1. Open any link in new tab using the context menu or by middle clicking.
2. Move your current tab to the right with Ctrl+Shift+Page Down.
3. Open any link in new tab again.
Actual results:
The newly opened tab showed up next to the previously opened tab.
Expected results:
New tab show up next to your current tab.
|
P1
|
VERIFIED
|
FIXED
|
2025-01-26 07:49:11+00:00
|
2025-02-14 10:27:48+00:00
| 150
| 1
|
1943850
|
Trying to open a recently closed tab results in the wrong tab opening
|
Steps to reproduce:
This isn't the only way to reproduce it and I haven't tested if re-opening closed windows is affected as well.
1. Open two windows.
2. On window A, open three links and a newtab.
3. On window A, right-click on the newtab and close the other tabs.
4. On window B, go to the hamburger menu > History > Recently closed tabs and select the first entry.
5. On window B, open a new tab, and close the tab opened at the previous step.
6. On window B, go again to the recently closed tabs and select the second entry.
Actual results:
The tab that reopens at step 6 is not the one clicked on the menu.
At some point I encountered an entry in the recently closed tabs menu that didn't open any tab at all when clicked, but I don't have STR for that.
Expected results:
Regressed by Bug 1932941.
|
Trying to open a recently closed tab results in the wrong tab opening Steps to reproduce:
This isn't the only way to reproduce it and I haven't tested if re-opening closed windows is affected as well.
1. Open two windows.
2. On window A, open three links and a newtab.
3. On window A, right-click on the newtab and close the other tabs.
4. On window B, go to the hamburger menu > History > Recently closed tabs and select the first entry.
5. On window B, open a new tab, and close the tab opened at the previous step.
6. On window B, go again to the recently closed tabs and select the second entry.
Actual results:
The tab that reopens at step 6 is not the one clicked on the menu.
At some point I encountered an entry in the recently closed tabs menu that didn't open any tab at all when clicked, but I don't have STR for that.
Expected results:
Regressed by Bug 1932941.
|
P1
|
VERIFIED
|
FIXED
|
2025-01-26 16:06:14+00:00
|
2025-02-13 13:26:53+00:00
| 220
| 1
|
1943876
|
Pinned Tabs scrambled after browser restart
|
I exited Firefox normally in response to an update notification and ended up with 135.0b6. Upon starting Firefox back up with the new version, all my pinned tabs had been rearranged into a seemingly random order. My main window has 12 pinned tabs so bringing them back into the previous order was a little annoying. It seems like my non-pinned tabs weren't scrambled, though - all my tabs in all my windows seem to be in their proper order, it just scrambled the pinned ones.
I have Tree Style Tabs active if that matters.
|
Pinned Tabs scrambled after browser restart I exited Firefox normally in response to an update notification and ended up with 135.0b6. Upon starting Firefox back up with the new version, all my pinned tabs had been rearranged into a seemingly random order. My main window has 12 pinned tabs so bringing them back into the previous order was a little annoying. It seems like my non-pinned tabs weren't scrambled, though - all my tabs in all my windows seem to be in their proper order, it just scrambled the pinned ones.
I have Tree Style Tabs active if that matters.
|
P3
|
NEW
|
2025-01-27 01:00:42+00:00
|
2025-02-20 10:14:24+00:00
| 130
| 3
|
|
1943885
|
Pinning first tab should ungroup it
|
When you have a tab group and pin one of its tabs, behavior is a bit erratic:
* The first pinned tab seems to work (see attached screenshot).
* But as soon as you pin another tab from another group, then that tab gets detached from its group.
* If you add many tabs, so that the tab list scrolls, then the pinned tab gets completely inaccessible.
I'd expect either:
* Pinning a tab always "ungroups" it. A bit unfortunate since it might be useful to have a tab group in the pinned tab area, but maybe ok.
* Pinning a tab pins the whole group.
But I haven't thought too hard about this. In any case making the tab inaccessible seems clearly a bug.
|
Pinning first tab should ungroup it When you have a tab group and pin one of its tabs, behavior is a bit erratic:
* The first pinned tab seems to work (see attached screenshot).
* But as soon as you pin another tab from another group, then that tab gets detached from its group.
* If you add many tabs, so that the tab list scrolls, then the pinned tab gets completely inaccessible.
I'd expect either:
* Pinning a tab always "ungroups" it. A bit unfortunate since it might be useful to have a tab group in the pinned tab area, but maybe ok.
* Pinning a tab pins the whole group.
But I haven't thought too hard about this. In any case making the tab inaccessible seems clearly a bug.
|
P1
|
RESOLVED
|
FIXED
|
2025-01-27 05:05:39+00:00
|
2025-02-03 10:23:54+00:00
| 162
| 1
|
1943888
|
Tab overflow menu does not reflect the current state of saved tab groups reopened or deleted from the overflow menu until reopened
|
### Steps to reproduce
1. Create a new tab group with tabs.
2. Right click on the tab group name and select "Save and close group".
3. Open the tab overflow menu.
4. Right click on the saved tab group in the overflow menu.
5. Select "Open Group in This Window" or "Delete Group".
### Expected behavior
The tab group name should, depending on which comment you selected in step 5 above, either:
1. Move from the overflow menu's tab groups section to the open tabs section.
2. Or disappear from the overflow menu.
### Actual behavior
The tab group name is still listed the overflow menu's tab group even though it has been reopened or deleted. If you close and then reopen the overflow menu, the menu will then show the correct tab group state.
|
Tab overflow menu does not reflect the current state of saved tab groups reopened or deleted from the overflow menu until reopened ### Steps to reproduce
1. Create a new tab group with tabs.
2. Right click on the tab group name and select "Save and close group".
3. Open the tab overflow menu.
4. Right click on the saved tab group in the overflow menu.
5. Select "Open Group in This Window" or "Delete Group".
### Expected behavior
The tab group name should, depending on which comment you selected in step 5 above, either:
1. Move from the overflow menu's tab groups section to the open tabs section.
2. Or disappear from the overflow menu.
### Actual behavior
The tab group name is still listed the overflow menu's tab group even though it has been reopened or deleted. If you close and then reopen the overflow menu, the menu will then show the correct tab group state.
|
P2
|
RESOLVED
|
DUPLICATE
|
2025-01-27 06:37:12+00:00
|
2025-01-30 13:10:31+00:00
| 208
| 2
|
1943895
|
Website viewport changes when bookmark toolbar set to only show on new tab
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:136.0) Gecko/20100101 Firefox/136.0
Steps to reproduce:
Whenever i switch between new tab and a website tab, the website's screen or viewport changes especially the footer, it feels like after switching to the new tab the bookmark bar gets visible in every tab and therefore after switching to the website tab the bar gets hidden and it causes the issue.
|
Website viewport changes when bookmark toolbar set to only show on new tab User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:136.0) Gecko/20100101 Firefox/136.0
Steps to reproduce:
Whenever i switch between new tab and a website tab, the website's screen or viewport changes especially the footer, it feels like after switching to the new tab the bookmark bar gets visible in every tab and therefore after switching to the website tab the bar gets hidden and it causes the issue.
|
P3
|
RESOLVED
|
DUPLICATE
|
2025-01-27 07:48:18+00:00
|
2025-01-31 10:46:26+00:00
| 125
| 3
|
1943927
|
The fade is visible when widget.macos.titlebar-blend-mode.behind-window is enabled on macOS.
|
The fade is visible when widget.macos.titlebar-blend-mode.behind-window is enabled on macOS.
|
The fade is visible when widget.macos.titlebar-blend-mode.behind-window is enabled on macOS. The fade is visible when widget.macos.titlebar-blend-mode.behind-window is enabled on macOS.
|
P2
|
NEW
|
2025-01-27 11:19:51+00:00
|
2025-02-25 22:02:27+00:00
| 56
| 2
|
|
1943928
|
Firefox View appears as "Switch to Tab" suggestion, should probably be a secondary action instead
|
Steps to reproduce:
* Open Firefox View
* Click another tab and type `firefox` into the address bar
Actual results:
Your address bar suggestions now include `about:firefoxview [Switch to Tab]`.
Expected results:
Firefox View isn't treated as a tab by the GUI and can't be closed, so it shouldn't be shown as a "Switch to Tab" suggestion.
|
Firefox View appears as "Switch to Tab" suggestion, should probably be a secondary action instead Steps to reproduce:
* Open Firefox View
* Click another tab and type `firefox` into the address bar
Actual results:
Your address bar suggestions now include `about:firefoxview [Switch to Tab]`.
Expected results:
Firefox View isn't treated as a tab by the GUI and can't be closed, so it shouldn't be shown as a "Switch to Tab" suggestion.
|
P3
|
NEW
|
2025-01-27 11:46:44+00:00
|
2025-02-17 16:17:55+00:00
| 110
| 3
|
|
1943971
|
When moving multiple tabs to the end, if the last item is an open tab group, moved items are added to the group
|
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
It is important that the last item in a window should be an open tab group.
1. CMD + Click or SHIFT + CLICK on the tabs to select multiple tabs.
2. Right click and select “Move Tabs > Move to End”.
Actual results:
The selected tabs are added to the open group at the end.
Expected results:
The tabs should have moved to the end ungrouped, after the open group.
|
When moving multiple tabs to the end, if the last item is an open tab group, moved items are added to the group User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
It is important that the last item in a window should be an open tab group.
1. CMD + Click or SHIFT + CLICK on the tabs to select multiple tabs.
2. Right click and select “Move Tabs > Move to End”.
Actual results:
The selected tabs are added to the open group at the end.
Expected results:
The tabs should have moved to the end ungrouped, after the open group.
|
P1
|
RESOLVED
|
FIXED
|
2025-01-27 14:21:15+00:00
|
2025-03-05 07:06:25+00:00
| 163
| 1
|
1943999
|
First key typed is ignored after entering search mode through the contextual search secondary action using tab key
|
**Found in**
- Nightly Version 136.0a1
**Steps to reproduce**
1. Navigate to a page of an engine not set to default, for example https://www.wikipedia.org/
2. Type a character into the address bar such that the top/auto-completed result is a URL from history
3. Press the tab key to enter search mode via the contextual search secondary action
4. Type in any additional character to continue your search string
**Expected result**
- Additional key typed is registered and added to search query string
**Actual result**
- First additional key typed is not registered
|
First key typed is ignored after entering search mode through the contextual search secondary action using tab key **Found in**
- Nightly Version 136.0a1
**Steps to reproduce**
1. Navigate to a page of an engine not set to default, for example https://www.wikipedia.org/
2. Type a character into the address bar such that the top/auto-completed result is a URL from history
3. Press the tab key to enter search mode via the contextual search secondary action
4. Type in any additional character to continue your search string
**Expected result**
- Additional key typed is registered and added to search query string
**Actual result**
- First additional key typed is not registered
|
P3
|
NEW
|
2025-01-27 15:38:28+00:00
|
2025-01-27 20:10:36+00:00
| 152
| 3
|
|
1944103
|
Refine targeting for tab groups onboarding messages
|
Scope here is to fix bugs caused by some incorrect targeting and tidy up the flow of the onboarding messages.
|
Refine targeting for tab groups onboarding messages Scope here is to fix bugs caused by some incorrect targeting and tidy up the flow of the onboarding messages.
|
P1
|
RESOLVED
|
FIXED
|
2025-01-27 19:05:01+00:00
|
2025-01-30 04:10:50+00:00
| 33
| 1
|
1944133
|
Onboarding message about "if you close a tab group" is unclear about what it means by "close"
|
I noticed a tab-groups-onboarding message today which pointed to the "List all tabs" menu. The text said:
```
If you close a tab group, you can reopen it here anytime.
```
(This was added in bug 1943442.)
We might want to modify the language there -- I think we might really intend to say "collapse" or something on those lines, rather than "close"?
Intuitively, I interpret (and I think users interpret) "close a tab group" as meaning "close all of the tabs in the tab group" (which for a tab group would mean clicking all the "x" buttons, or right-clicking the tab-group and choosing "Delete"). And if you do either of those things, then the list-all-tabs menu **does not** have any UI to reopen that group, which seems to superficially contradict what this onboarding message was trying to say.
|
Onboarding message about "if you close a tab group" is unclear about what it means by "close" I noticed a tab-groups-onboarding message today which pointed to the "List all tabs" menu. The text said:
```
If you close a tab group, you can reopen it here anytime.
```
(This was added in bug 1943442.)
We might want to modify the language there -- I think we might really intend to say "collapse" or something on those lines, rather than "close"?
Intuitively, I interpret (and I think users interpret) "close a tab group" as meaning "close all of the tabs in the tab group" (which for a tab group would mean clicking all the "x" buttons, or right-clicking the tab-group and choosing "Delete"). And if you do either of those things, then the list-all-tabs menu **does not** have any UI to reopen that group, which seems to superficially contradict what this onboarding message was trying to say.
|
P1
|
RESOLVED
|
FIXED
|
2025-01-27 20:28:57+00:00
|
2025-02-24 18:52:12+00:00
| 230
| 1
|
1944328
|
"Reopen All Tabs" should support closed tab groups from closed windows
|
Steps to reproduce:
1. Open some "worth-saving" tabs. Put some of them in a tab group.
2. Open a second window.
3. In the first window, right click the tab group label and select "Delete group".
4. Close the first window.
5. From the top menu, go to "History > Recently Closed Tabs". Observe that the closed tab group from the first window exists."
6. Click "Reopen All Tabs".
Expected result:
The tabs from the closed tab group are reopened in the existing window, as part of a tab group.
Actual result:
Nothing happens.
|
"Reopen All Tabs" should support closed tab groups from closed windows Steps to reproduce:
1. Open some "worth-saving" tabs. Put some of them in a tab group.
2. Open a second window.
3. In the first window, right click the tab group label and select "Delete group".
4. Close the first window.
5. From the top menu, go to "History > Recently Closed Tabs". Observe that the closed tab group from the first window exists."
6. Click "Reopen All Tabs".
Expected result:
The tabs from the closed tab group are reopened in the existing window, as part of a tab group.
Actual result:
Nothing happens.
|
P1
|
RESOLVED
|
FIXED
|
2025-01-28 15:05:25+00:00
|
2025-03-05 07:06:31+00:00
| 150
| 1
|
1944414
|
Requesting an accessibility review of the Mozilla VPN add-on
|
Hi folks, the VPN team is releasing a browser extension for Firefox and we'd like to request an accessibility review to ensure the extension properly reports to accessibility tools and works well for users of those tools.
A few things to note:
- The extension will only be available on Windows (for now)
- Extension functionality requires a Mozilla VPN subscription (we can set the reviewers up with these of course) and that the VPN client be installed on the user's device (MSI can be downloaded here: https://ftp.mozilla.org/pub/vpn/candidates/2.25.0-candidates/build20250115012521/windows/)
- The GitHub repository for the extension is here: https://github.com/mozilla-extensions/mozilla-vpn-extension/
- Unsigned XPIs can be installed here: https://github.com/mozilla-extensions/mozilla-vpn-extension/deployments/github-pages
Please let us know what other information you need from us or how we can be helpful!
Thank you!
|
Requesting an accessibility review of the Mozilla VPN add-on Hi folks, the VPN team is releasing a browser extension for Firefox and we'd like to request an accessibility review to ensure the extension properly reports to accessibility tools and works well for users of those tools.
A few things to note:
- The extension will only be available on Windows (for now)
- Extension functionality requires a Mozilla VPN subscription (we can set the reviewers up with these of course) and that the VPN client be installed on the user's device (MSI can be downloaded here: https://ftp.mozilla.org/pub/vpn/candidates/2.25.0-candidates/build20250115012521/windows/)
- The GitHub repository for the extension is here: https://github.com/mozilla-extensions/mozilla-vpn-extension/
- Unsigned XPIs can be installed here: https://github.com/mozilla-extensions/mozilla-vpn-extension/deployments/github-pages
Please let us know what other information you need from us or how we can be helpful!
Thank you!
|
P3
|
NEW
|
2025-01-28 21:52:24+00:00
|
2025-02-26 16:47:54+00:00
| 264
| 3
|
|
1944416
|
Individual tabs from closed tab groups in closed windows cannot be restored from history menus
|
Steps to reproduce:
1. Open some "worth-saving" (i.e. not `about:blank` tabs). Put some (but not all — see bug1941622) into a tab group.
2. Right click the tab group label and click "delete tab group".
3. Open a new window.
4. Close the original window.
5. From the top menu, go to "History > Recently Closed Tabs". Find the closed tab group in the list. Click any of the tabs within that tab group.
Expected result:
The tab opens in the new window.
Actual result:
Nothing happens.
This is a follow-on bug from bug1932941, which allows users to reopen closed *tab groups* from closed windows, but not individual tabs within the tab group.
|
Individual tabs from closed tab groups in closed windows cannot be restored from history menus Steps to reproduce:
1. Open some "worth-saving" (i.e. not `about:blank` tabs). Put some (but not all — see bug1941622) into a tab group.
2. Right click the tab group label and click "delete tab group".
3. Open a new window.
4. Close the original window.
5. From the top menu, go to "History > Recently Closed Tabs". Find the closed tab group in the list. Click any of the tabs within that tab group.
Expected result:
The tab opens in the new window.
Actual result:
Nothing happens.
This is a follow-on bug from bug1932941, which allows users to reopen closed *tab groups* from closed windows, but not individual tabs within the tab group.
|
P1
|
RESOLVED
|
FIXED
|
2025-01-28 22:07:41+00:00
|
2025-03-05 07:06:28+00:00
| 191
| 1
|
1944546
|
[Rollout][Desktop] The Fx 102-128 RootCA Infobar is triggered on Fx versions newer than ESR 115.12
|
**[Affected versions]:**
- Firefox ESR 115.13 - Build ID: 20240703222632
**[Affected Platforms]:**
- Windows 7
- Windows 8
- Windows 10
- Windows 11
- macOS 15.0.1
- Ubuntu 22.04
**[Prerequisites]:**
- Have a Firefox ESR 115.13 installed, with any locale.
- Have the “root-ca” pref added in the “about:config” page, set to the “true” value.
**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Change the system time to any date between the 12th of February and the 17th of March, included.
3. Open a new tab and observe the address bar.
**[Expected result]:**
- The Fx 102-128 RootCA Infobar is NOT displayed.
**[Actual result]:**
- The Fx 102-128 RootCA Infobar IS displayed.
**[Notes]:**
- Upon further investigation, we noticed that the targeting expression includes versions newer than the intended maximum version, ESR 115.12
- Attached a screenshot of the issue.
|
[Rollout][Desktop] The Fx 102-128 RootCA Infobar is triggered on Fx versions newer than ESR 115.12 **[Affected versions]:**
- Firefox ESR 115.13 - Build ID: 20240703222632
**[Affected Platforms]:**
- Windows 7
- Windows 8
- Windows 10
- Windows 11
- macOS 15.0.1
- Ubuntu 22.04
**[Prerequisites]:**
- Have a Firefox ESR 115.13 installed, with any locale.
- Have the “root-ca” pref added in the “about:config” page, set to the “true” value.
**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Change the system time to any date between the 12th of February and the 17th of March, included.
3. Open a new tab and observe the address bar.
**[Expected result]:**
- The Fx 102-128 RootCA Infobar is NOT displayed.
**[Actual result]:**
- The Fx 102-128 RootCA Infobar IS displayed.
**[Notes]:**
- Upon further investigation, we noticed that the targeting expression includes versions newer than the intended maximum version, ESR 115.12
- Attached a screenshot of the issue.
|
P1
|
VERIFIED
|
FIXED
|
2025-01-29 13:02:41+00:00
|
2025-01-31 13:11:11+00:00
| 301
| 1
|
1944549
|
[Rollout][Desktop] Clicking the SUMO page link dismisses the Fx 102-128 RootCA Infobar on Firefox versions older than 115.0
|
**[Affected versions]:**
- Firefox ESR 102.0 - Build ID: 20220623064521
- Firefox Release 114.0.2 - Build ID: 20230619081400
**[Affected Platforms]:**
- Windows 7
- Windows 8
- Windows 10
- Windows 11
- macOS 15.0.1
- Ubuntu 22.04
**[Prerequisites]:**
- Have a Firefox Release 114.0.2 installed, with any locale.
- Have the “root-ca” pref added in the “about:config” page, set to the “true” value.
**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Change the system time to any date between the 12th of February and the 17th of March, included.
3. Open a new tab.
4. Click on the SUMO page link on the Fx 102-128 RootCA Infobar.
5. Observe the behaviour.
**[Expected result]:**
- The SUMO page is opened in a new tab and the Fx 102-128 RootCA Infobar is still displayed.
**[Actual result]:**
- The SUMO page is opened in a new tab and the Fx 102-128 RootCA Infobar is dismissed.
**[Notes]:**
- This issue is reproducible on all Firefox versions older than 115.
- This issue is reproducible on all locales.
- Attached a screen recording of the issue [here](https://drive.google.com/file/d/1AmHnUq8tDaBMvX6DhUTcmL_TPl_QoOfA/view?usp=sharing).
|
[Rollout][Desktop] Clicking the SUMO page link dismisses the Fx 102-128 RootCA Infobar on Firefox versions older than 115.0 **[Affected versions]:**
- Firefox ESR 102.0 - Build ID: 20220623064521
- Firefox Release 114.0.2 - Build ID: 20230619081400
**[Affected Platforms]:**
- Windows 7
- Windows 8
- Windows 10
- Windows 11
- macOS 15.0.1
- Ubuntu 22.04
**[Prerequisites]:**
- Have a Firefox Release 114.0.2 installed, with any locale.
- Have the “root-ca” pref added in the “about:config” page, set to the “true” value.
**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Change the system time to any date between the 12th of February and the 17th of March, included.
3. Open a new tab.
4. Click on the SUMO page link on the Fx 102-128 RootCA Infobar.
5. Observe the behaviour.
**[Expected result]:**
- The SUMO page is opened in a new tab and the Fx 102-128 RootCA Infobar is still displayed.
**[Actual result]:**
- The SUMO page is opened in a new tab and the Fx 102-128 RootCA Infobar is dismissed.
**[Notes]:**
- This issue is reproducible on all Firefox versions older than 115.
- This issue is reproducible on all locales.
- Attached a screen recording of the issue [here](https://drive.google.com/file/d/1AmHnUq8tDaBMvX6DhUTcmL_TPl_QoOfA/view?usp=sharing).
|
P1
|
RESOLVED
|
WONTFIX
|
2025-01-29 13:08:08+00:00
|
2025-01-30 20:09:11+00:00
| 423
| 1
|
1944627
|
Sidebar button still present checked (pressed) after turning off sidebar revamp
|
STR:
1. open clean Firefox nightly profile
2. open Labs or the settings page where we put the new "browsing" section post-bug 1936379
3. turn on new/revamped sidebar
4. turn off
ER:
either the sidebar button stays or is removed - but if it stays, its state should correspond to whether the sidebar is open or not
AR:
the sidebar button stays but also is checked, which is confusing because the sidebar is not open.
|
Sidebar button still present checked (pressed) after turning off sidebar revamp STR:
1. open clean Firefox nightly profile
2. open Labs or the settings page where we put the new "browsing" section post-bug 1936379
3. turn on new/revamped sidebar
4. turn off
ER:
either the sidebar button stays or is removed - but if it stays, its state should correspond to whether the sidebar is open or not
AR:
the sidebar button stays but also is checked, which is confusing because the sidebar is not open.
|
P1
|
VERIFIED
|
FIXED
|
2025-01-29 17:26:57+00:00
|
2025-02-06 14:37:23+00:00
| 122
| 1
|
1944677
|
userPrefersReducedMotion is undefined in xpcshell tests
|
The work from bug 1941961 was backed out because we triggered some logging in the targeting context recorder:
```
TEST-UNEXPECTED-FAIL | xpcshell.toml:toolkit/components/search/tests/xpcshell/test_defaultEngine.js | test_switch_with_invalid_overriddenBy - [test_switch_with_invalid_overriddenBy : 614] Unexpected console message received during test: TargetingContextRecorder: Could not get "userPrefersReducedMotion" - false == true
```
As it turns out, this property is undefined in xpcshell tests because xpcshell tests used a [stubbed out version of nsIXULAppInfo](https://searchfox.org/mozilla-central/rev/0b189f017bc9d48b62012205c5b9f8a8b560497b/testing/modules/AppInfo.sys.mjs) that does not define the property.
|
userPrefersReducedMotion is undefined in xpcshell tests The work from bug 1941961 was backed out because we triggered some logging in the targeting context recorder:
```
TEST-UNEXPECTED-FAIL | xpcshell.toml:toolkit/components/search/tests/xpcshell/test_defaultEngine.js | test_switch_with_invalid_overriddenBy - [test_switch_with_invalid_overriddenBy : 614] Unexpected console message received during test: TargetingContextRecorder: Could not get "userPrefersReducedMotion" - false == true
```
As it turns out, this property is undefined in xpcshell tests because xpcshell tests used a [stubbed out version of nsIXULAppInfo](https://searchfox.org/mozilla-central/rev/0b189f017bc9d48b62012205c5b9f8a8b560497b/testing/modules/AppInfo.sys.mjs) that does not define the property.
|
P1
|
RESOLVED
|
FIXED
|
2025-01-29 20:52:10+00:00
|
2025-02-13 13:19:14+00:00
| 250
| 1
|
1944715
|
No :active state for Screenshot buttons
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
Clicked on Take Screenshot from context menu and then selected an area to screenshot. Then clicked any of the screenshot buttons that appear to the lower right (Cancel, Copy & Download).
Actual results:
When hovering over the button the button background color changes, but it remains the same color when pressing the mouse button.
Expected results:
As with most other Firefox buttons the background color should change to the :active state style when pressing the mouse button. A check in Browser Toolbox shows that :active state CSS styles are defined and seems to be working correctly.
When searching for this problem I found a long-standing Firefox bug that could very well be related to this problem:
https://bugzilla.mozilla.org/show_bug.cgi?id=771241
|
No :active state for Screenshot buttons User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
Clicked on Take Screenshot from context menu and then selected an area to screenshot. Then clicked any of the screenshot buttons that appear to the lower right (Cancel, Copy & Download).
Actual results:
When hovering over the button the button background color changes, but it remains the same color when pressing the mouse button.
Expected results:
As with most other Firefox buttons the background color should change to the :active state style when pressing the mouse button. A check in Browser Toolbox shows that :active state CSS styles are defined and seems to be working correctly.
When searching for this problem I found a long-standing Firefox bug that could very well be related to this problem:
https://bugzilla.mozilla.org/show_bug.cgi?id=771241
|
P3
|
NEW
|
2025-01-30 01:00:08+00:00
|
2025-02-06 19:41:00+00:00
| 223
| 3
|
|
1944733
|
Tab overflow menu: "move group to new window" fails when caller window has only one tab
|
STR
1. add a tab group and an ungrouped tab to a window
2. open a new window with only a single tab
3. open TOM on the new window
4. right click the tab group in the list and select "move to new window"
Expected: The group is moved to a new window
Actual: `TypeError: can't access property "addEventListener", newWindow is null`
|
Tab overflow menu: "move group to new window" fails when caller window has only one tab STR
1. add a tab group and an ungrouped tab to a window
2. open a new window with only a single tab
3. open TOM on the new window
4. right click the tab group in the list and select "move to new window"
Expected: The group is moved to a new window
Actual: `TypeError: can't access property "addEventListener", newWindow is null`
|
P2
|
RESOLVED
|
FIXED
|
2025-01-30 05:18:42+00:00
|
2025-03-05 07:06:23+00:00
| 112
| 2
|
1944791
|
Tab has an extra animation when dragged out of the Tab group at the beginning of the Tab Strip
|
**Found in**
* 136.0a1 (2025-01-30)
**Affected versions**
* 136.0a1 (2025-01-30)
**Affected platforms**
* all
**Steps to reproduce**
1. Have a Tab group created as the first item from the Horizontal Tab strip
2. Drag a Tab outside of the Tab Group to the left of it.
**Expected result**
* The Tab should move outside of the Tab group without any extra animations
**Actual result**
* The Tab jumps back when moved outside of the Tab group and placed as the first Tab on the Horizontal tab strip.
**Regression range**
This issue started to occur now that Bug 1932489 was fixed.
|
Tab has an extra animation when dragged out of the Tab group at the beginning of the Tab Strip **Found in**
* 136.0a1 (2025-01-30)
**Affected versions**
* 136.0a1 (2025-01-30)
**Affected platforms**
* all
**Steps to reproduce**
1. Have a Tab group created as the first item from the Horizontal Tab strip
2. Drag a Tab outside of the Tab Group to the left of it.
**Expected result**
* The Tab should move outside of the Tab group without any extra animations
**Actual result**
* The Tab jumps back when moved outside of the Tab group and placed as the first Tab on the Horizontal tab strip.
**Regression range**
This issue started to occur now that Bug 1932489 was fixed.
|
P3
|
VERIFIED
|
FIXED
|
2025-01-30 10:07:56+00:00
|
2025-02-21 15:50:00+00:00
| 177
| 3
|
1944842
|
Sidebar can get into scenario where it's expanded but vertical tabs aren't showing labels
|
STR:
Enable vertical tabs in about:preferences that will also enable the new sidebar
Toggle the sidebar toolbar button until it expands the sidebar
Disable the new sidebar while still in expanded state
Reenable vertical tabs
This looks to be the same issue we were seeing in bug 1936839.
|
Sidebar can get into scenario where it's expanded but vertical tabs aren't showing labels STR:
Enable vertical tabs in about:preferences that will also enable the new sidebar
Toggle the sidebar toolbar button until it expands the sidebar
Disable the new sidebar while still in expanded state
Reenable vertical tabs
This looks to be the same issue we were seeing in bug 1936839.
|
P1
|
VERIFIED
|
FIXED
|
2025-01-30 13:30:12+00:00
|
2025-02-07 14:05:11+00:00
| 88
| 1
|
1944844
|
Tab groups are not created with Drag and Drop when Tab group indicators are displayed
|
**Found in**
* 136.0a1 (2025-01-30) ID 20250130092924
**Affected versions**
* 136.0a1 (2025-01-30) ID 20250130092924
**Affected platforms**
* all
**Steps to reproduce**
1. Drag a Tab over a 2nd Tab and Release it when they both show a blue border.
**Expected result**
* As soon as the Tabs show a Blue border it should create the Tab group.
**Actual result**
* Users have to keep one Tab over the other for a longer period of time in order to create the Tab group.
**Regression range**
4:04.67 INFO: Last good revision: 2b7278af32c77e822c8cc5dad005e033c08bfd3b
4:04.67 INFO: First bad revision: f8fda1ba5cd3ee4d27e6e337803cdf53eaad9011
4:04.68 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=2b7278af32c77e822c8cc5dad005e033c08bfd3b&tochange=f8fda1ba5cd3ee4d27e6e337803cdf53eaad9011
|
Tab groups are not created with Drag and Drop when Tab group indicators are displayed **Found in**
* 136.0a1 (2025-01-30) ID 20250130092924
**Affected versions**
* 136.0a1 (2025-01-30) ID 20250130092924
**Affected platforms**
* all
**Steps to reproduce**
1. Drag a Tab over a 2nd Tab and Release it when they both show a blue border.
**Expected result**
* As soon as the Tabs show a Blue border it should create the Tab group.
**Actual result**
* Users have to keep one Tab over the other for a longer period of time in order to create the Tab group.
**Regression range**
4:04.67 INFO: Last good revision: 2b7278af32c77e822c8cc5dad005e033c08bfd3b
4:04.67 INFO: First bad revision: f8fda1ba5cd3ee4d27e6e337803cdf53eaad9011
4:04.68 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=2b7278af32c77e822c8cc5dad005e033c08bfd3b&tochange=f8fda1ba5cd3ee4d27e6e337803cdf53eaad9011
|
P1
|
VERIFIED
|
FIXED
|
2025-01-30 13:32:48+00:00
|
2025-02-06 08:39:53+00:00
| 344
| 1
|
1944908
|
RemoteSettingsExperimentLoader logs use recipe.id instead of recipe.slug
|
The logs use recipe.id instead of recipe.slug. In production use this is fine because id == slug. However, ExperimentFakes.recipe() does not maintain this property.
The logging should be updated to use .slug and ExperimentFakes should be updated to generate ids that match slugs.
|
RemoteSettingsExperimentLoader logs use recipe.id instead of recipe.slug The logs use recipe.id instead of recipe.slug. In production use this is fine because id == slug. However, ExperimentFakes.recipe() does not maintain this property.
The logging should be updated to use .slug and ExperimentFakes should be updated to generate ids that match slugs.
|
P3
|
RESOLVED
|
FIXED
|
2025-01-30 16:49:54+00:00
|
2025-02-05 09:59:50+00:00
| 85
| 3
|
1944918
|
Vertical tabs visually jump a bit when expanding and collapsing the new sidebar
|
As part of bug 1941344, the `padding-block` was changed for vertical tabs only when the sidebar is collapsed. We should match this padding-block regardless of whether the sidebar is collapsed or expanded to ensure a smooth transition between the two states.
|
Vertical tabs visually jump a bit when expanding and collapsing the new sidebar As part of bug 1941344, the `padding-block` was changed for vertical tabs only when the sidebar is collapsed. We should match this padding-block regardless of whether the sidebar is collapsed or expanded to ensure a smooth transition between the two states.
|
P1
|
VERIFIED
|
FIXED
|
2025-01-30 17:13:59+00:00
|
2025-02-11 15:55:09+00:00
| 74
| 1
|
1944931
|
When initally enabling Vertical tabs in about:preferences, the "Show sidebar" option is checked by default but the sidebar is hiding when toggled
|
When you initially toggle on Vertical tabs, “Show sidebar” is checked on by default, but toggling the sidebar using the toolbar button is actually hiding it. Once I uncheck it and reenable vertical tabs, it’s expanding/collapsing as expected.
|
When initally enabling Vertical tabs in about:preferences, the "Show sidebar" option is checked by default but the sidebar is hiding when toggled When you initially toggle on Vertical tabs, “Show sidebar” is checked on by default, but toggling the sidebar using the toolbar button is actually hiding it. Once I uncheck it and reenable vertical tabs, it’s expanding/collapsing as expected.
|
P1
|
RESOLVED
|
FIXED
|
2025-01-30 17:57:35+00:00
|
2025-02-18 17:09:43+00:00
| 97
| 1
|
1944968
|
New tab page weather widget overlaps pocket content
|
With the updated layout of the new tab page, the weather widget on the right overlaps the right-most Pocket story at my default browser size and resolution. See attached screenshot.
|
New tab page weather widget overlaps pocket content With the updated layout of the new tab page, the weather widget on the right overlaps the right-most Pocket story at my default browser size and resolution. See attached screenshot.
|
P1
|
NEW
|
2025-01-30 21:34:08+00:00
|
2025-02-06 21:18:45+00:00
| 50
| 1
|
|
1944970
|
New tab column layout is inconsistent
|
The vertical location of the Pocket stories is not consistent across browser window widths.
When wide enough for 4 columns of stories, the stories are in-line with the Firefox logo and the weather widget.
When sized down to 3 columns, the stories are always below the logo and weather (even it it appears there is room for them to fit between the logo and widget).
When sized down to 2 columns, the stories are below the logo and widget when wider, but in-line with the logo and widget when narrower.
See attached recording that shows these cases as the browser width is changed.
|
New tab column layout is inconsistent The vertical location of the Pocket stories is not consistent across browser window widths.
When wide enough for 4 columns of stories, the stories are in-line with the Firefox logo and the weather widget.
When sized down to 3 columns, the stories are always below the logo and weather (even it it appears there is room for them to fit between the logo and widget).
When sized down to 2 columns, the stories are below the logo and widget when wider, but in-line with the logo and widget when narrower.
See attached recording that shows these cases as the browser width is changed.
|
P1
|
ASSIGNED
|
2025-01-30 21:44:39+00:00
|
2025-02-22 20:29:43+00:00
| 133
| 1
|
|
1945031
|
Unable to pin local file URL to new tab page
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
1. Pin random site in New Tab page
2. Change its URL to file:///C:/SomeFolder/SomePage.html
Actual results:
An error appears "Valid URL required".
Expected results:
The URL is valid and must be accepted. There's no reason for FF to reject local URLs.
|
Unable to pin local file URL to new tab page User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0
Steps to reproduce:
1. Pin random site in New Tab page
2. Change its URL to file:///C:/SomeFolder/SomePage.html
Actual results:
An error appears "Valid URL required".
Expected results:
The URL is valid and must be accepted. There's no reason for FF to reject local URLs.
|
P3
|
NEW
|
2025-01-31 05:46:02+00:00
|
2025-02-12 13:10:50+00:00
| 130
| 3
|
|
1945077
|
The Search Shortcut for Actions does not work
|
Steps to reproduce:
1. Make sure the "Actions" Search Engine is enabled in the settings
2. Go to the search bar and type ">" followed by a space
Actual results:
Despite the ">" being listed as the keyword for the "Actions" Search Engine, it does nothing when used in the search bar. The "Actions" Search Engine has to be manually selected from the menu underneath the search suggestions.
Expected results:
It should work like all the other Search Engine Keywords. When ">" is typed followed by a space, the "Actions" Search Engine should be selected.
|
The Search Shortcut for Actions does not work Steps to reproduce:
1. Make sure the "Actions" Search Engine is enabled in the settings
2. Go to the search bar and type ">" followed by a space
Actual results:
Despite the ">" being listed as the keyword for the "Actions" Search Engine, it does nothing when used in the search bar. The "Actions" Search Engine has to be manually selected from the menu underneath the search suggestions.
Expected results:
It should work like all the other Search Engine Keywords. When ">" is typed followed by a space, the "Actions" Search Engine should be selected.
|
P3
|
NEW
|
2025-01-31 11:45:19+00:00
|
2025-03-03 14:24:11+00:00
| 133
| 3
|
|
1945111
|
Tabs closed from tab groups disappear from history menu if their original tab group is deleted
|
Steps to reproduce:
1. Open some tabs with content (i.e. not `about:blank`).
2. Add tabs to a group.
3. Close one of these tabs.
4. In the top menu, open "History > Recently Closed Tabs". Verify the closed tab exists in the list.
5. Right click the tab group label and click "Delete group".
6. Re-open the recently closed tabs menu.
Expected result:
The initially closed tab appears in Recently Closed Tabs alongside the now closed tab group.
Actual result:
The initially closed tab disappears from the menu.
|
Tabs closed from tab groups disappear from history menu if their original tab group is deleted Steps to reproduce:
1. Open some tabs with content (i.e. not `about:blank`).
2. Add tabs to a group.
3. Close one of these tabs.
4. In the top menu, open "History > Recently Closed Tabs". Verify the closed tab exists in the list.
5. Right click the tab group label and click "Delete group".
6. Re-open the recently closed tabs menu.
Expected result:
The initially closed tab appears in Recently Closed Tabs alongside the now closed tab group.
Actual result:
The initially closed tab disappears from the menu.
|
P2
|
RESOLVED
|
FIXED
|
2025-01-31 12:36:01+00:00
|
2025-03-05 07:06:30+00:00
| 148
| 2
|
1945146
|
List all tabs no longer automatically scrolls to current tab
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:136.0) Gecko/20100101 Firefox/136.0
Steps to reproduce:
Open the List all tabs drop down menu with enough tabs to include a scrollbar
Select a tab at the bottom of the list (not visible without scrolling)
Open List all tabs again
Actual results:
List all tabs scrollbar is at top, non-scrolled position.
Expected results:
List all tabs scrollbar should have automatically scrolled to show the currently selected tab.
|
List all tabs no longer automatically scrolls to current tab User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:136.0) Gecko/20100101 Firefox/136.0
Steps to reproduce:
Open the List all tabs drop down menu with enough tabs to include a scrollbar
Select a tab at the bottom of the list (not visible without scrolling)
Open List all tabs again
Actual results:
List all tabs scrollbar is at top, non-scrolled position.
Expected results:
List all tabs scrollbar should have automatically scrolled to show the currently selected tab.
|
P1
|
VERIFIED
|
FIXED
|
2025-01-31 13:42:50+00:00
|
2025-02-13 09:30:17+00:00
| 138
| 1
|
1945149
|
Dragged tab is not added in group when dragged on the first slot of the group in List All Tabs dropdown
|
**Found in**
* 136.0a1 (2025-01-31)
**Affected versions**
* 136.0a1 (2025-01-31)
**Affected platforms**
* All
**Preconditions**
* Have a group created with two or more tabs
**Steps to reproduce**
1. Open List all tabs
2. Drag another tab over the first slot in the previously created group
**Expected result**
* The dragged tab is added to the group and in the first slot
**Actual result**
* The tab is not added to the group and it will be thrown to the bottom of the list
**Regression range**
* Will see if this is a regression
**Additional Notes**
* The issue can be seen in the attachment
|
Dragged tab is not added in group when dragged on the first slot of the group in List All Tabs dropdown **Found in**
* 136.0a1 (2025-01-31)
**Affected versions**
* 136.0a1 (2025-01-31)
**Affected platforms**
* All
**Preconditions**
* Have a group created with two or more tabs
**Steps to reproduce**
1. Open List all tabs
2. Drag another tab over the first slot in the previously created group
**Expected result**
* The dragged tab is added to the group and in the first slot
**Actual result**
* The tab is not added to the group and it will be thrown to the bottom of the list
**Regression range**
* Will see if this is a regression
**Additional Notes**
* The issue can be seen in the attachment
|
P3
|
NEW
|
2025-01-31 13:48:40+00:00
|
2025-02-10 09:12:21+00:00
| 193
| 3
|
|
1945169
|
When a group is the only thing in a window, moving it via the TOM context menu creates a saved clone
|
STR
1. Create a group in a window such that there are no tabs in the window outside of the group
2. open a new window
3. open TOM in the new window, right click on the group in the other window, and select "move to this window"
Expected: Group moves to this window
Actual: Group moves to this window, and a copy of the group gets saved.
Presumably the closing window triggers the group being saved.
|
When a group is the only thing in a window, moving it via the TOM context menu creates a saved clone STR
1. Create a group in a window such that there are no tabs in the window outside of the group
2. open a new window
3. open TOM in the new window, right click on the group in the other window, and select "move to this window"
Expected: Group moves to this window
Actual: Group moves to this window, and a copy of the group gets saved.
Presumably the closing window triggers the group being saved.
|
P1
|
RESOLVED
|
FIXED
|
2025-01-31 14:39:56+00:00
|
2025-03-05 07:06:34+00:00
| 115
| 1
|
1945264
|
pressing Ctrl+T while a tab in a tab group is active should create a new tab in the same tab group if browser.tabs.insertAfterCurrent is set to true (open tab next to current one)
|
Firefox 136.0a1 20250131152909 on Windows 10
Pressing Ctrl+T while a tab in a tab group is active should create a new tab in the same tab group if the preference browser.tabs.insertAfterCurrent is set to true (= open tab next to current one).
|
pressing Ctrl+T while a tab in a tab group is active should create a new tab in the same tab group if browser.tabs.insertAfterCurrent is set to true (open tab next to current one) Firefox 136.0a1 20250131152909 on Windows 10
Pressing Ctrl+T while a tab in a tab group is active should create a new tab in the same tab group if the preference browser.tabs.insertAfterCurrent is set to true (= open tab next to current one).
|
P3
|
VERIFIED
|
FIXED
|
2025-01-31 21:52:29+00:00
|
2025-02-17 14:53:04+00:00
| 119
| 3
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.