av9ash/GitBugs huggingface dataset:
Bug: Sometimes editing a URL selected from address bar dropdown reverts to the previous one when pressing Enter
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2023-09-13 19:26:29+00:00
Resolved: 2024-01-29 21:12:13+00:00

I very frequently start typing something in the address bar to edit it before navigating to it.
For example, I type `my-admin` because I know it'll autocomplete `https://my-admin-portal.example.com/user/foo`. I then edit the completed URL and replace `foo` with `bar`.
This is incredibly useful and I prefer this over creating bookmarks with search shortcuts - and it's more flexible because it works fine for pretty much everything I use regularly.

However, lately I noticed that occasionally (I was not able to figure out what exactly causes this to happens) as soon as I press Enter to navigate to the new URL, it reverts to the original URL and navigates to that one...

I think this started happening some weeks ago, so probably at some point during 118 or 117 (I'm on the beta channel).
Bug: unloaded pinned tabs still spawn a process when pref browser.sessionstore.restore_pinned_tabs_on_demand is true
Status: NEW
Priority: P3
Created: 2023-09-13 19:47:26+00:00
Resolved: 2024-12-10 23:39:34+00:00

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/117.0

Steps to reproduce:

- Have session restore enabled
- Have on-demand loading set for tabs (default?) and pinned tabs (have pref browser.sessionstore.restore_pinned_tabs_on_demand = true)
- Optionally, have pref browser.tabs.tooltipsShowPidAndActiveness set to true and the "Auto Tab Discard" extension installed.

Open some tabs, pin some of those tabs, then quit and reopen Firefox. Hover over the tab for a pid, or check about:processes.


Actual results:

When Firefox is started, neither pinned tabs nor unpinned tabs will be loaded after the windows are restored. However, when examining about:processes (and formerly about:performance), the pinned tabs would still have a process (OS task with a pid) created for them. Each tab will be idle. Unpinned tabs would have no process created. Multiple processes would be created for a pinned site (seemingly per-domain) with only one (discarded) tab assigned to it (in this case, about:processes reports it consumes 13-15 MB per redundant process). With many pinned tabs present, this created a lot of wasted processes and memory on the system. As an example from my case, while I only have one Twitter tab open in its container, I have four unloaded pinned Twitter tabs as well. This created four processes, three of which are completely redundant and have consumed zero CPU time.

Note that after startup, "unloaded" and loaded pinned tabs can still be manually discarded (via an extension, from the tab context menu) to remove the process from the tab. As far as I know, there is no way to do this in batch.


Expected results:

Processes should just be spawned only for the tabs that are focused in each window. Pinned tabs, with the aforementioned on-demand preference set, should not differ from unpinned tabs in this regard. Processes should also not exist solely for the purpose of storing a single unloaded (pinned) tab.
Bug: Shift+Ctrl+T doesn't restore last tab anymore
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2023-09-13 20:42:39+00:00
Resolved: 2024-04-01 12:23:04+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/117.0

Steps to reproduce:

I pressed Shift+Ctrl+T to restore my last tab in Firefox 117. 


Actual results:

To my surprise the last WINDOW opened, which I would normally get back by pressing Shift+Ctrl+N.
I remember seeing this bug in some older Firefox developer editions, where it more or less acted erratically, mostly opening the last window, sometimes opening the last tab. In FF 117, it just always opening the last Window, for that though there's already a shortcut.


Expected results:

The last closed tab should be opened.
Bug: When launcher file (firefox-trunk, shipped by Ubuntu) is set as opener app, infinite tab opening loops can happen on Linux
Status: NEW
Priority: P3
Created: 2023-09-14 01:23:03+00:00
Resolved: 2024-07-18 15:18:37+00:00

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36

Steps to reproduce:

 goto https://www.postgresql.org/message-id/CAExHW5tx1i5AqehEkT1sr-4B16MA-r%3DBd-QW9xsRW0g4xm1kLQ%40mail.gmail.com 
download any dot patch file.
try to open it in firefox nightly (in the search bar). (I didn't test on firefox).


Actual results:

it will open as many tabs, and will not stop.


Expected results:

should just like chrome. just like open a txt file. since patch is plain text file.
Bug: The tspan dy attributes doesn't support rem values. eg. <tspan dy="1rem">test</tspan> will not render correctly.
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-09-14 02:27:55+00:00
Resolved: 2023-09-14 11:15:28+00:00

Steps to reproduce:

eg. <tspan dy="1rem">test</tspan> will not render correctly.




Actual results:

The y-axis position was always 0 when a rem value was provided. When a pixel value was provided such as <tspan dy="16">test</tspan> the y-axis position was correctly rendered.
 


Expected results:

The dy attribute (and assumedly other positioning attributes such as x) in the tspan element should position the tspan when a rem value is provided as well as when the pixel value is provided.
Bug: Links from the onboarding card are read as buttons by screen readers
Status: NEW
Priority: P3
Created: 2023-09-14 06:31:00+00:00
Resolved: 2023-10-04 16:32:49+00:00

**Found in**
* 119.0a1 (2023-09-13)


**Affected versions**
* 119.0a1 (2023-09-13)






**Tested platforms**
* Affected platforms: Ubuntu 20, macOS 12, Windows 10x64
* Unaffected platforms: none

**Preconditions**
* browser.shopping.experience2023.enabled:true
* browser.shopping.experience2023.optedIn:0
* screen reader enabled

**Steps to reproduce**
1. Open a random Amazon product.
2. Use the keyboard to select the `Learn more`, `privacy policy`, and `terms of use` links.

**Expected result** 
* Screen readers identify the above-selected strings as links.

**Actual result**
* Screen reader identifies the above-selected strings as buttons.

**Regression**
* Not a regression.






**Additional notes**
* The `Launch analyzer on Fakepost.com` from the `Updates available` card is correctly read as a link.
* The Fakespot by Mozilla determines review quality from the How we determine review quality card is correctly read as a link.
Bug: Analysis is coming soon card is displayed after a product is analyzed and we return to that product using back/forward browser buttons
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2023-09-14 08:58:07+00:00
Resolved: 2023-09-15 10:18:58+00:00

**Found in**
* 119.0a1 (2023-09-13)


**Affected versions**
* 119.0a1 (2023-09-13)






**Tested platforms**
* Affected platforms: Ubuntu 20, macOS 12, Windows 10x64
* Unaffected platforms: none

**Preconditions**
* browser.shopping.experience2023.enabled:true
* browser.shopping.experience2023.optedIn:1


**Steps to reproduce**
1. Open a random Amazon product that needs to be reanalyzed.
2. Click to launch the analyzer and reanalyze the product.
3. Wait on the analyzer tab until the analysis is completed.
4. Refresh the product tab page to update the sidebar.
5. Go to another product and click the back browser arrow to return to the previous product.

**Expected result** 
* The analyzed product is displayed in the sidebar.

**Actual result**
* The `Analysis is coming soon` card is displayed.

**Regression**
* Not a regression.






**Additional notes**
* Attached a screen recording.
* Refreshing the page will show the updated sidebar without the `Analysis is coming soon` card.
* This issue is only reproducible if the product tab page is not focused until the analysis is completed.
* The issue is intermittent sometimes.
Bug: Address bar flickers when suggestions are removed after "Show less frequently"
Status: NEW
Priority: P3
Created: 2023-09-14 08:58:35+00:00
Resolved: 2024-11-12 14:03:41+00:00

**Found in**
* 118.0b9 (treeherder)

**Affected versions**
* 118.0b9 (treeherder)
* 119.0a1 (2023-09-13)

**Tested platforms**
* Affected platforms: Windows 10, Mac 13, Ubuntu 22

**Preconditions**
* `browser.search.region` set to US
* `browser.urlbar.pocket.featureGate` to true for pocket suggest

**Steps to reproduce**
1. Open new tab, type 'tts' into address bar (for addon suggestions)
1'. Open new tab, type 'breakfast' into address bar (for pocket suggestions)
2. Using the results menu use Show less frequently 3 times.
3. Dissmiss and refocus address bar.

**Expected result**
* Address bar suggestions should not contain either the addon suggestion (1) or the pocket suggestion(1')

**Actual result**

1. For addon suggestion the issue is more visible, since the addon suggestion flickers while it is removed from the suggestions.
1'. For the pocket suggestion, is less visible since there is only the last row removed and repopulated with a search suggestion.

**Regression range**
* Not a regression.
Bug: [linux]  The how to determine review quality card is read separately row by row by screen reader
Status: NEW
Priority: P5
Created: 2023-09-14 10:28:35+00:00
Resolved: 2024-02-09 20:32:15+00:00

**Found in**
* 119.0a1 (2023-09-13)


**Affected versions**
* 119.0a1 (2023-09-13)






**Tested platforms**
* Affected platforms: Ubuntu 20
* Unaffected platforms:  macOS 12, Windows 10x64

**Preconditions**
* browser.shopping.experience2023.enabled:true
* browser.shopping.experience2023.optedIn:1
* screen reader enabled


**Steps to reproduce**
1. Open a random Amazon product.
2. Expand the `How we determine review quality` card.
3. Click on a random text.

**Expected result** 
* Screen reader reads all text.

**Actual result**
* Only the selected row is read.

**Regression**
* Not a regression.
Bug: Recently closed tabs from other windows are not preserved in Fx View list after exiting session
Status: NEW
Priority: P3
Created: 2023-09-14 10:43:59+00:00
Resolved: 2024-04-04 23:03:07+00:00

**Found in**
- Firefox 119.0a1

**Affected versions**
- Firefox 119.0a1

**Tested platforms**
- Affected platforms: macOS 13.5.2, Ubuntu 22.04, Windows 10

**Steps to reproduce**
1. Launch Firefox and access Firefox View
2. Have a second window opened and access some websites in some tabs
3. Close the tabs in order to populate the list in Recently closed tabs
4. Quit Firefox and re-open it with the same profile
5. Access Firefox View

**Expected result**
- The websites closed in step 3 are still present in Recently closed tabs card

**Actual result**
- The websites closed in step 3 are not shown anymore in Recently closed tabs

**Regression range**
- Will see for a regression

**Additional notes**
- The issue can be seen in the following [attachment](https://drive.google.com/file/d/11P7pfd9OOUvOtLcTnNwrCSbiearzQIjs/view?usp=sharing)
- This is not reproducible if Firefox is only restarted and not completely closed
- Reproduces only if the websites are closed from within a second window
Bug: Opening Firefox View at least once will cause the tab animation that plays when the tab finishes loading to disappear
Status: NEW
Priority: --
Created: 2023-09-14 12:48:43+00:00
Resolved: 2023-10-20 13:40:06+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/117.0

Steps to reproduce:

Open Firefox View at least once.


Actual results:

Tab animation that plays when the tab finishes loading disappears.


Expected results:

Opening or using Firefox View at least once should not cause the tab animation that plays when the tab finishes loading to disappear.
Bug: Primary password prompt does not show
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2023-09-14 15:11:50+00:00
Resolved: 2023-09-14 15:19:17+00:00

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/117.0

Steps to reproduce:

Mozilla Firefox 117.0.1
Arch Linux

1. Updated Firefox
2. Went to a website where my login is saved. Password prompt did not show up like it used to.
3. Went to about:logins. A bar "Please enter your Primary Password to view saved logins & passwords" with a "log in" button
4. Pressing "log in" only reloads the page


Actual results:

The Primary Password prompt does not show up


Expected results:

It should've showed up.
Bug: Links in the chrome are using the wrong color with a dark theme applied
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2023-09-14 15:38:09+00:00
Resolved: 2023-10-19 08:11:47+00:00

The current link color in the chrome is darker than expected when a dark theme is applied. Previously the color was brighter/more similar to the primary button color (see attached screenshot for a comparison).

Using mozregression points to Bug 1843044.

It looks like prior to that change [these styles](https://searchfox.org/mozilla-central/rev/fa219b9c1d6c2c64aa139a848573caa03bc81f25/browser/themes/shared/browser-shared.css#161-164) were getting used to set the link color.
Bug: The chevron button in shopping-details summary is missing expanded/collapsed state
Status: NEW
Priority: P3
Created: 2023-09-14 17:14:49+00:00
Resolved: 2023-10-25 14:33:23+00:00

### Preconditions:
- Set the `browser.shopping.experience2023.enabled` - `TRUE`
- Set the `browser.shopping.experience2023.optedIn` - `1`
- Enable a screen reader, i.e. NVDA on Windows

### STR:
1. Reach the following links https://www.amazon.com/dp/B07V6ZSHF4?th=1
2. Hover the mouse cursor over either `How we determine review quality` chevron button or `Settings` chevron button
3. Navigate to the  `How we determine review quality` collapsed button (i.e. by using `Tab`), then press `DownArrow` to hear the announcement for the chevron button. 
    1. Observe the announcement about the state of the button
4. Press `Enter` while the chevron button is focused with a screen reader OR click on the button with a mouse/touch
5. Repeat for `Settings` chevron button

### Expected:
- The state `expanded` or `collapsed` should be read out loud by NVDA alongside the role and the label (added in Bug #1851735)  of the button
- Either the chevron button is not announced by a screen reader at all (because the label, role, and state are already announced by the focusable `<summary>` element) or the button provides the current state of the control (mirroring the `<details>` element)

### Actual:
- The button state is not announced by a screen reader.
Bug: Shopping Microsurvey includes an unlabelled visually hidden button that is focusable at the end of the container
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2023-09-14 17:27:40+00:00
Resolved: 2023-09-20 16:17:36+00:00

### Preconditions:
- Set the `browser.shopping.experience2023.enabled` - `TRUE`
- Set the `browser.shopping.experience2023.optedIn` - `1`
- Set the `browser.shopping.experience2023.survey.pdpVisits` - `4`
- Set the `browser.shopping.experience2023.survey.hasSeen` - `FALSE`

### STR:
1. Reach the following PDP link: https://www.amazon.com/dp/B07V6ZSHF4?th=1
2. Ensure the microsurvey `Help improve Firefox` is shown in the Shopping sidebar (if it's not, try reloading the page. <sup>I'm not sure how to reliably prompt it</sup>)
3. Navigate with `Tab` keypresses through the Shopping Sidebar past the `Help improve Firefox` radio button group and observe the focus indication movement between this group and the following `How we determine review quality` control.
4. Enable a screen reader, i.e. NVDA on Windows
5. When a screen reader is running and the `How we determine review quality` is focused, press `Tab + Shift` to move the focus to the previous focusable element and observe the announcement for this control and (if possible) visible position of the focus indication

### Expected:
- Only visible and active UI elements (controls that can be clicked/tapped) are receiving keyboard focus and when they are focused, the focus indication's position is clearly visible on the screen
- Every focusable with `Tab` element is announced by a screen reader so the user could hear the purpose of this element (its label/accessible name), role (button/radio button/link, etc.) and, when applicable, state.

### Actual:
- The off-screen element is receiving keyboard focus, while the focus indication jsut disappears from the screen and its location remains unknown until the user presses `Tab` or `Shift+Tab` once again.
- A button that is announced by a screen reader is not labelled and its purpose is unknown.
Bug: A large part of the web page is not translated
Status: RESOLVED
Priority: P3
Resolution: DUPLICATE
Created: 2023-09-14 18:17:34+00:00
Resolved: 2023-10-17 18:13:15+00:00

https://yle.fi/a/74-20049658

This is the first random Finnish website and I ran into this issue.

You'll need to enable Finnish in Remote settings in Nightly to test it, but the problem can be reproduced on many websites with dynamic content loading. Likely the same as https://bugzilla.mozilla.org/show_bug.cgi?id=1845776.

Here is another example of a large news web-site in Russian where a similar problem is easily reproducible: https://www.rbc.ru/.

This problem makes such web-sites quite unusable because you can read only the main article.

Also, this worked in the addon, so it's a regression.
Bug: [Survey] The stepper element misses aria-label and is announced by screen readers as "busy"
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2023-09-14 19:12:36+00:00
Resolved: 2023-10-19 12:25:38+00:00

### Preconditions:
- Set the `browser.shopping.experience2023.enabled` - `TRUE`
- Set the `browser.shopping.experience2023.optedIn` - `1`
- Set the `browser.shopping.experience2023.survey.pdpVisits` - `4`
- Set the `browser.shopping.experience2023.survey.hasSeen` - `FALSE`
- Enable a screen reader, i.e. NVDA on Windows

### STR:
1. Reach the following PDP link: https://www.amazon.com/dp/B07V6ZSHF4?th=1
2. Ensure the microsurvey `Help improve Firefox` is shown in the Shopping sidebar (if it's not, try reloading the page. <sup>I'm not sure how to prompt it reliably </sup>)
3. Navigate to the stepper element within the survey container (i.e. with NVDA on WinOS, press `Tab` key through the Shopping Sidebar to the `Help improve Firefox` radio button group, then press `DownArrow` keys to move the tracking focus to the stepper
4. Observe the announcement for this element to find out: how many steps are in the process and which step is currently open.

### Expected:
- A screen reader would announce the current position and total number of steps, i.e. `1 of 2`. Good example is the stepper on `about:welcome` that is announced by VoiceOver on macOS as: `Progress: step 1 of 4, busy, progress indicator`

### Actual:
- The progress bar misses the current position and the total number of steps, as well as its role, and only announces `busy`. A screen reader user won't be aware what the purpose of this element, why is it busy, and how many steps are in the survey.

The HTML element has `attrs: aria-label` but this attribute is not being rendered, thus no accessible name is provided to the progressbar. More on the use of this role: https://w3c.github.io/aria/#progressbar
Bug: Bookmarks not showing when a tag is selected
Status: UNCONFIRMED
Priority: --
Created: 2023-09-14 19:18:40+00:00
Resolved: 2023-09-29 16:28:14+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/116.0

Steps to reproduce:

Go into Pocket -> All tags -> Click on a tag (in my case, the one for "computation").


Actual results:

Shows loading icons indefinitely while never loading any of the saved bookmarks.

(It seems to be a problem with just that one tag; other tags will load.)


Expected results:

It should have shown the bookmarks I've saved under "computation".

Note: I can get some of the items to display by changing the sort order to "oldest first" but then it only does the first page of loads and won't load any further.
Bug: Intermittent browser/components/enterprisepolicies/tests/browser/browser_policy_search_engine.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2023-09-14 20:02:43+00:00
Resolved: 2023-10-13 12:00:44+00:00

**Filed by:** smolnar [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=429140593&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/d-fu0N13SE2u-cwaxozQiw/runs/0/artifacts/public/logs/live_backing.log

---
```
TEST-PASS | browser/components/enterprisepolicies/tests/browser/browser_policy_search_engine.js | "Find more search engines" link should be hidden - true == true - 
[task 2023-09-14T15:05:42.241Z] 15:05:42     INFO - Leaving test bound test_prevent_install_ui
[task 2023-09-14T15:05:42.241Z] 15:05:42     INFO - Entering test bound test_opensearch_disabled
[task 2023-09-14T15:05:42.242Z] 15:05:42     INFO - Buffered messages finished
[task 2023-09-14T15:05:42.243Z] 15:05:42     INFO - TEST-UNEXPECTED-FAIL | browser/components/enterprisepolicies/tests/browser/browser_policy_search_engine.js | There should be no search engines available to add - Got [object XULElement], expected null
[task 2023-09-14T15:05:42.243Z] 15:05:42     INFO - Stack trace:
[task 2023-09-14T15:05:42.243Z] 15:05:42     INFO - chrome://mochikit/content/browser-test.js:test_is:1608
[task 2023-09-14T15:05:42.243Z] 15:05:42     INFO - chrome://mochitests/content/browser/browser/components/enterprisepolicies/tests/browser/browser_policy_search_engine.js:test_opensearch:49
[task 2023-09-14T15:05:42.243Z] 15:05:42     INFO - chrome://mochitests/content/browser/browser/components/enterprisepolicies/tests/browser/browser_policy_search_engine.js:test_opensearch_disabled:108
[task 2023-09-14T15:05:42.243Z] 15:05:42     INFO - chrome://mochikit/content/browser-test.js:handleTask:1131
[task 2023-09-14T15:05:42.243Z] 15:05:42     INFO - chrome://mochikit/content/browser-test.js:_runTaskBasedTest:1203
[task 2023-09-14T15:05:42.243Z] 15:05:42     INFO - chrome://mochikit/content/browser-test.js:Tester_execTest:1345
[task 2023-09-14T15:05:42.243Z] 15:05:42     INFO - chrome://mochikit/content/browser-test.js:nextTest/<:1120
[task 2023-09-14T15:05:42.243Z] 15:05:42     INFO - chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/<:1058
[task 2023-09-14T15:05:42.244Z] 15:05:42     INFO - TEST-PASS | browser/components/enterprisepolicies/tests/browser/browser_policy_search_engine.js | Search bar should not have addengines attribute
```
Bug: In the newest Firefox Update (Version 117.0.1 (64-bit)) on MacOS 13.5.2, the Firefox View window displays white text on a white background when dark mode is active
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2023-09-14 20:15:21+00:00
Resolved: 2023-09-20 15:12:19+00:00

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/117.0

Steps to reproduce:

I didn't do anything specific, just note that the newest Firefox Version installed it automatically, as i set it to do so, and my browser is on Automatic mode, so dark mode when the the sun is down and light mode when the sun's up. 


Actual results:

After i clicked (by accident) on the Firefox view window, i saw the icons of the listed Tabs on the left hand side of where the text's normally at, but i didn't see any text. To find out what happend, i activated light mode, and with light mode activated, the text reapeared. I'm guessing that the text colour switched to dark mode, but the background stayed in light mode, so it basically displayed a white text on a white background.

Important to note, the only text visable was the text in the three boxes on top of the tab list in which some tabs are shown. The rest isn't visable, but all the links still work, you just need to click on the place where the text's supposed to be. Also note i have the extension "Dark Background and Light Text" installed, but deactivated on Firefox view (It's even blocked form activating on the Firefox view window)


Expected results:

The Background should've gone dark, thus resulting in the white text being visable.