av9ash/GitBugs huggingface dataset:
Bug: Sometimes, when the >> button to show more bookmarks is pressed, ALL bookmarks are shown, including the ones already visible in the bookmarks toolbar.
Status: NEW
Priority: P3
Created: 2023-06-01 10:53:23+00:00
Resolved: 2024-04-06 10:50:09+00:00

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

Steps to reproduce:

Click the >> button to show more bookmarks (only visible when the user has more bookmarks that can be displayed in the bookmark tab)

This doesn't happen always. It's rare.


Actual results:

ALL bookmarks are shown in the panel that opens, INCLUDING the ones that are already visible in the bookmarks tab. 
Since the panel that opens is to see only the extra bookmarks that can't be shown, this is a bug.


Expected results:

Only the non-visible bookmarks (the extra ones) should be shown.
Bug: Make Translations section in about:preferences a richlistbox
Status: NEW
Priority: P3
Created: 2023-06-01 15:28:43+00:00
Resolved: 2024-06-07 04:35:00+00:00

### STR:
1. Ensure a screen reader is running
1. Navigate to the Translations Section in about:preferences
1. Use `Tab` to move focus to the `Download Ukranian` language option

### Actual: 
1. Keyboard-only users would need to tediously navigate past multiple `Download` and `Delete` (when applicable) buttons to access one of languages closer to the end of the list or to even pass this section in the Preferences. This would make keyboard navigation within the page very cumbersome and it would be getting worse with the Translations adding more languages to the list. This would create a high impact on a large diverse set of users, while the issues below are lower severity, but still are not delightful
1. Screen reader users would have multiple repetitive `Download` and `Delete` (when applicable) buttons present and even if they'll utilize a list of controls/buttons provided by their screen reader, it would still be nearly impossible to discern which button should be activated to download/delete specific language. It would make the usage especially confusing for users with cognitive difficulties (who rely on screen readers often too)
1. Scrollable area in Translations section in about:preferences lacks accessible name, thus a screen reader user will have to memorize the heading of the section and the text above the list of languages to know what is the purpose of this list of downloads, affecting users with lower cognition abilities as well
1. For users with low vision, those who uses magnification software, physical magnifiers or just move next to their screen, discerning which row the button is applicable to may be harder, because the buttons are far removed to the right side from their corresponding labels and the focus outline only is provided to the button itself
1. Voice control users would not be able to activate a button by calling the language's name and would have to add an extra step by calling the on-screen label `Download` > then call a number that the voice control software would associate with their desired language.

### Expected/Recommended:
1. Use `RichListbox` component that other sections like `Applications` are using in the about pages - it should be customizable afaik and would provide all the keyboard accessibility and other accessibility-related roles, states, and attributes for free and resolve or simplify all the above barriers for users. If more info is wanted, refer to the [listbox](https://www.w3.org/WAI/ARIA/apg/patterns/listbox/examples/listbox-scrollable/) ARIA-powered design pattern that RichListbox is building on
Bug: Firefox's Trending Search Suggestion keep showing up, even after I un-tick "Show search suggestions in address bar results"
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2023-06-01 16:35:19+00:00
Resolved: 2023-09-04 09:59:03+00:00

STR:
1. In Firefox Nightly (which has trending search suggestions enabled per bug 1832060), hit Ctrl+K.  Take a look at the dropdown/popup. (You'll see some "trending search suggestions" dropping down from the address bar.)
2. Now suppose you'd like to turn those off. Go Firefox Preferences and type "suggestion" into the filter searchbar.
3. Un-tick the checkbox `Show search suggestions in address bar results`.
4. Repeat step 1.

ACTUAL RESULTS:
I'm still seeing trending search suggestions appearing in a dropdown from my address bar.

EXPECTED RESULTS:
Perhaps the suggestions should've gone away.

Note, the suggestions *do* go away if I instead uncheck "Provide search suggestions" (modulo bug 1836325 making that confusing in today's Nightly in particular)

I see daleharvey mentioned the lack of UI for configuring these in https://phabricator.services.mozilla.com/D177498#5852359 -- dale, do you know if that's tracked somewhere? Did we want to add that before letting these get to early-beta (as they will next week)?  I'm a bit concerned that users will un-tick one or the other checkbox, see that the suggestions remain, and conclude that the feature is broken/being-pushed-on-them (without realizing that they just need to go and un-tick one additional checkbox).
Bug: Firefox "Provide search suggestions" and Firefox Suggest checkboxes are un-checked by default, despite the fact that it's actually enabled
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-06-01 17:02:18+00:00
Resolved: 2023-06-02 16:09:21+00:00

STR:
1. Visit about:preferences (Firefox Settings)
2. Type "Suggest" into the filter searchbox
3. Look at the checkbox for `Provide search suggestions` and (further down) the various checkboxes/sliders under `Address Bar — Firefox Suggest`


ACTUAL RESULTS:
All of the settings are shown as "off".

EXPECTED RESULTS:
All of these should be checked/enabled (except the last one for "Improve the Firefox search experience). **They are in fact enabled, but Firefox is mistakenly showing them as disabled.**

mozregression indicates that this was a regression from bug 1831259.

Note, these settings are particularly sensitive to display accurately, given that we have some new search suggestions UI that seems to be shipping to early-beta users, with this first checkbox being one of the things you have to turn off in order to disable that UI.
Bug: Some settings were shown incorrectly in Privacy & Security in Firefox 115.0a1 (2023-06-01)
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2023-06-01 17:45:42+00:00
Resolved: 2023-06-08 06:26:54+00:00

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

Steps to reproduce:

I started Firefox 115.0a1 (2023-06-01) on Wayland in Plasma 5.27.5 in a Fedora 38 KDE Plasma installation. I selected Edit in the the menu bar then Settings. I selected Privacy & Security in the Settings page. I had previously set the following settings in Privacy & Security which are relevant to this problem. For Enhanced Tracking Protection, I had set Custom and enabled the following
Cookies All Cross-site cookies
Tracking Content All Windows
Cryptominers
Fingerprinters

In History, I had selected Always use private browsing mode. In DNS over HTTPS, I had Increased Protection selected (the default).


Actual results:

Some incorrect settings were shown in the Privacy & Security page in the Settings in Firefox 115.0a1 (2023-06-01), but not in earlier builds. For Enhanced Tracking Protection the selected circle was Standard, but the Custom setting box was highlighted in blue. 
Cookies was selected, but Cross-site cookies tracking cookies, and isolate other cross-site cookies was incorrectly shown.
Tracking Content was selected, but Only in Private Windows was incorrectly shown.
Cryptominers was incorrectly shown as not selected
Fingerprinters was incorrectly shown as not selected

In History, Always use private browsing mode didn't have a selected checkbox. In DNS over HTTPS, the circle for Default Protection was incorrectly selected, but the Increased Protection box was highlighted in blue.

I bisected this problem with MOZ_ENABLE_WAYLAND=1 mozregression --good 2023-5-31 --bad 2023-6-1 --persist /tmp/mozregression -p ~/.mozilla/firefox/z8d4nvrc.default-nightly

The first bad revision was for Bug 1831259 - prevent initialization re-entrancy for preference panes

6:15.42 INFO: Narrowed integration regression window from [a934ffbf, 55bc4f5d] (3 builds) to [a934ffbf, c34f2e33] (2 builds) (~1 steps left)
 6:15.42 INFO: No more integration revisions, bisection finished.
 6:15.42 INFO: Last good revision: a934ffbfaecf6f5be6cfa34d789a9430c2330a07
 6:15.42 INFO: First bad revision: c34f2e337a314e032ed98b495ed78b16e193d04e
 6:15.42 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=a934ffbfaecf6f5be6cfa34d789a9430c2330a07&tochange=c34f2e337a314e032ed98b495ed78b16e193d04e

When I restored the settings above to their previous values and restarted Firefox 115.0a1 (2023-06-01), the incorrect settings were shown again except in Enhanced Tracking Protection which saved the correct settings in the second parts of
Cookies All Cross-site cookies
Tracking Content All Windows

I'm attaching a recording of the incorrect settings.




Expected results:

The Privacy & Security settings should have have been shown correctly.
Bug: Risk of messages in tree causing failures of random automated tests
Status: NEW
Priority: P3
Created: 2023-06-01 21:19:25+00:00
Resolved: 2023-06-20 14:08:57+00:00

Messaging is generally enabled during tests since it's enabled by default. This doesn't usually cause too many problems since most of our messages trigger in very specific conditions so they don't come up during automated tests. But in some cases, messages that work fine in experiments will cause problems when landing in tree (see bug 1831144 for example - the message unexpectedly appears on startup when other tests, unrelated to FxMS, are running).

There might be an easy way to disable this specific message during automated tests by just changing its targeting. Then, our own tests can enable it so they can test on it, but the rest of Firefox's browser tests don't need to be edited to account for it. But since this isn't really a problem with this specific message, but a universal risk for all messages with lenient enough trigger/targeting, we should consider a more universal approach to fixing this. For example, disable ASRouter entirely when a pref is set, and set that pref in some file that runs as part of the test harness, or something.
Bug: Deleting language modules doesn't seem to have an effect
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-06-02 00:31:51+00:00
Resolved: 2023-06-29 16:02:05+00:00

Steps to reproduce:
1) Download all language modules for translation.
2) Delete German.
3) Restart Firefox.
4) Visit https://www.ebay.de/ .
5) Click the translate icon in the URL bar and click Translate.
6) View the list of modules.

Expected:
4) The translate icon doesn't show up.
5) Nothing to click.
6) German says "Download".

Actual:
4) The translate icon shows up.
5) The page gets translated from German to English.
6) German says "Download", but how can it not be present if the page could be translated?

The profile has the Firefox Translations add-on, but it is disabled.
Bug: Title bar overflow bug
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-06-02 05:13:31+00:00
Resolved: 2023-06-16 12:34:09+00:00

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

Steps to reproduce:

Open more tabs than 30+ tabs.


Actual results:

Opening more than 30 tabs in a single Firefox browsing session cases an overflow which pushes the restore up/down, new tab, minimize, maximize and close buttons get pushed off screen.


Expected results:

Opening more than 30+ tabs should not push the restore up/down, new tab, minimize, maximize and close buttons off screen.
Bug: Firefox black favicons look bad on black/dark backgrounds
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2023-06-02 08:34:35+00:00
Resolved: 2024-05-14 10:15:15+00:00

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

Steps to reproduce:

Have a tab manager. Use the favicons from the tab api. This is how they look in a dark background.



Expected results:

Maybe they should have more neutral colors.
Bug: No progress indication for translation downloads
Status: NEW
Priority: --
Created: 2023-06-02 10:53:36+00:00
Resolved: 2023-06-29 21:45:23+00:00

STR:

1. go to settings
2. search "translations"
3. click "download" button next to any language

AR:
the button greys out and then nothing happens. Refreshing the page later, the button changes to "delete".

ER:
some indication of progress and when the download finishes.
Bug: 114.0 breaks tab session manager extension with multi account containers
Status: UNCONFIRMED
Priority: --
Created: 2023-06-02 13:16:01+00:00
Resolved: 2023-09-15 23:09:20+00:00

Steps to reproduce:

updated from 113 to 114 (through https://launchpad.net/~mozillateam .deb packages)


Actual results:

saved sessions with tab session manager lose containers on tabs upon restore.
Recreating said session also does not help


Expected results:

Restoring a tab session manager session should reopen each tab in the container it was open at the time of saving.
Use case: multiple gmail accounts one per container.
Bug: Don't re-enroll in rollouts that are opted-out of
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2023-06-02 14:45:51+00:00
Resolved: 2023-06-02 21:37:46+00:00

Bug 1833248 allowed for re-enrollment in rollouts if the enrollment conditions were met again. However, this did not account for opting out of rollouts, which should prevent re-enrollment.
Bug: Tab history from one SERP to another can be recorded as a non-ad click
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2023-06-02 15:07:22+00:00
Resolved: 2023-07-11 15:07:46+00:00

As mentioned in Bug 1835267, the tab history can trigger a "click" event due to the fact that the URL matches a SERP, as we've made the allowable non ad links more permissive.

Could be the same with bookmarks or manually entering a URL that's a SERP? It might a timing issue.
Bug: Intermittent browser/components/newtab/test/browser/browser_asrouter_snippets_dismiss.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2023-06-02 15:32:31+00:00
Resolved: 2023-09-27 12:01:42+00:00

**Filed by:** nerli [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=417900665&repo=try
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/fu-xu7i4Q1Ocst3J6ePUGg/runs/0/artifacts/public/logs/live_backing.log

---
```
[task 2023-06-02T12:23:50.291Z] 12:23:50     INFO - TEST-UNEXPECTED-FAIL | browser/components/newtab/test/browser/browser_asrouter_snippets_dismiss.js | Uncaught exception in test bound test_campaign_dismiss - Should find the snippet inside the footer container - timed out after 50 tries.
[task 2023-06-02T12:23:50.292Z] 12:23:50     INFO - Leaving test bound test_campaign_dismiss
[task 2023-06-02T12:23:50.292Z] 12:23:50     INFO - GECKO(1128) | MEMORY STAT | vsize 2104513MB | vsizeMaxContiguous 69285400MB | residentFast 424MB | heapAllocated 160MB
[task 2023-06-02T12:23:50.293Z] 12:23:50     INFO - TEST-OK | browser/components/newtab/test/browser/browser_asrouter_snippets_dismiss.js | took 6087ms
[task 2023-06-02T12:23:50.293Z] 12:23:50     INFO - Not taking screenshot here: see the one that was previously logged
[task 2023-06-02T12:23:50.293Z] 12:23:50     INFO - TEST-UNEXPECTED-FAIL | browser/components/newtab/test/browser/browser_asrouter_snippets_dismiss.js | Found an unexpected tab at the end of test run: about:home - 
[task 2023-06-02T12:23:50.294Z] 12:23:50     INFO - GECKO(1128) | JavaScript error: , line 0: AbortError: Actor 'ASRouter' destroyed before query 'NEWTAB_MESSAGE_REQUEST' was resolved
[task 2023-06-02T12:23:50.295Z] 12:23:50     INFO - GECKO(1128) | [Child 6048: Main Thread]: I/DocShellAndDOMWindowLeak ++DOCSHELL 15556639000 == 1 [pid = 6048] [id = 14]
[task 2023-06-02T12:23:50.295Z] 12:23:50     INFO - GECKO(1128) | [Child 6048: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 3 (1554f28ada0) [pid = 6048] [serial = 31] [outer = 0]
[task 2023-06-02T12:23:50.295Z] 12:23:50     INFO - GECKO(1128) | [Child 6048: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 4 (1555663a000) [pid = 6048] [serial = 32] [outer = 1554f28ada0]
[task 2023-06-02T12:23:50.296Z] 12:23:50     INFO - checking window state
```
Bug: Reftest logs include new logspam between each test: `console.error: Translations: (new Error("Unable to retrieve the translation models.", "resource://gre/actors/TranslationsParent.sys.mjs", 887))` and another line for Utils.sys.mjs
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2023-06-02 17:25:01+00:00
Resolved: 2023-06-03 09:27:19+00:00

STR:
1. Run some directory of reftests, e.g. here's a relatively short directory (6 tests):
```
./mach reftest layout/reftests/text-stroke/
```
2. Look at your terminal output.

ACTUAL RESULTS:
After each `REFTEST TEST-LOAD` line, the are these two lines:
```
console.error: (new Error("Unexpected content-type \"text/plain;charset=US-ASCII\"", "resource://services-settings/Utils.sys.mjs", 399))
console.error: Translations: (new Error("Unable to retrieve the translation models.", "resource://gre/actors/TranslationsParent.sys.mjs", 887))
```

I I'm pretty sure the second line (for TranslationsParent.sys.mjs) was recently-introduced.  Not sure about the first one (for Utils.sys.mjs), & whether that's introduced at the same time / for the same reason or not.

EXPECTED RESULTS:
No such log-spam.

Filing in Firefox|Translation to start out, given the `TranslationsParent.sys.mjs` filename.
Bug: [a11y] New Tab in the Private Window has inaccessible Search field
Status: RESOLVED
Priority: P3
Resolution: DUPLICATE
Created: 2023-06-03 00:16:39+00:00
Resolved: 2024-04-19 17:26:51+00:00

### STR
1. Keyboard:
1.1. On macOS, ensure `Use keyboard navigation to move focus between controls` checkbox under OS Settings > Keyboard > Shortcuts is checked
1.2. Open Firefox - New Window or New Private Window
1.3. Using `Tab` key navigate to and focus the search input field on the New Tab page
2. Screen Reader:
2.1. Ensure a screen reader is running
2.2. Open Firefox - New Private Window
2.3. While on a New Private Window, use `Tab` key to navigate to the main content area and to focus its search input field on the New Tab page

### Expected
1. Keyboard:
1.1. When a bookmarks bar is focused, pressing `Tab` key would move the keyboard focus to the search input on the main content area
1.2. the focus outline on the search input would be visible and a user would be able to enter their search request using keyboard only
2. Screen Reader:
2.1. When a bookmarks bar is focused, pressing `Tab` key would move the screen reader focus to the search input on the main content area
2.2. a screen reader would announce an informative accessible name of the search input and its role (i.e. `Search with Google or enter address, text field`) and a user would be able to enter their search request using keyboard only

### Actual
1. Keyboard:
1.1. When a bookmarks bar is focused, pressing `Tab` key moves the keyboard focus to the promo section or discovery stream, skipping the search input on the main content area altogether
1.2. user would not be able to enter their search request in a main content area using keyboard only while mouse/touch users would have this affordance
1.3. Sighted users among the keyboard users would see focus jumping over the input field that would not follow the expected/visual reading and focus orders
2. Screen Reader:
2.1. When a bookmarks bar is focused, pressing `Tab` key moves the screen reader focus to the promo area's heading, skipping the search input on the main content area altogether.
2.2. Using browsing mode of a screen reader does not provide access to any content above the promo section, i.e. with VoiceOver `VO`+`Left Arrow` (`Ctrl`+`Opt`+`Left Arrow` by default) keys do not move the focus and user hears a beep marking that they're at the very beginning of the content - while the Firefox logo and search input are both visually present on the screen 
2.3. Results of 1.2 and 1.3 above would apply for a screen reader case as well

On the Private Window's New Tab, the button and its nested input that are creating the search component are both provided with `tabindex=-1` that removes both controls from a keyboard focus order and `aria-hidden=true` removing it from the Accessibility tree for any assistive technology. On the default New Tab the button has only the `tabindex=-1` property exposing it to an assistive technology while keeping it inaccessible with a keyboard alone.

Firefox 113.0.2 (64-bit), 114.0 (64-bit), beta are tested on macOS, but per the markup of the page, the same results would be on all devices and platforms
Bug: Intermittent browser/base/content/test/tabs/browser_navigatePinnedTab.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2023-06-03 01:46:50+00:00
Resolved: 2023-08-16 12:00:38+00:00

**Filed by:** imoraru [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=417973013&repo=mozilla-central
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/BVwTOdhNQ9eVzPQZPng4sw/runs/0/artifacts/public/logs/live_backing.log

---
```
[task 2023-06-03T00:12:05.656Z] 00:12:05     INFO - TEST-START | browser/base/content/test/tabs/browser_navigatePinnedTab.js
[task 2023-06-03T00:12:05.912Z] 00:12:05     INFO - GECKO(9888) | JavaScript warning: resource://gre/modules/Troubleshoot.sys.mjs, line 712: WebGL context was lost.
[task 2023-06-03T00:14:15.124Z] 00:14:15     INFO -  console.error: (new TypeError("connection not specified or invalid.", "resource://gre/modules/Sqlite.sys.mjs", 1507))
[task 2023-06-03T00:14:15.134Z] 00:14:15     INFO -  console.error: (new TypeError("can't access property \"executeBeforeShutdown\", db is undefined", "resource://gre/modules/PlacesUtils.sys.mjs", 1473))
[task 2023-06-03T00:16:15.147Z] 00:16:15     INFO -  console.error: (new TypeError("can't access property \"executeTransaction\", db is undefined", "resource://gre/modules/PlacesFrecencyRecalculator.sys.mjs", 175))
[task 2023-06-03T00:18:15.900Z] 00:18:15     INFO - Buffered messages logged at 00:12:05
[task 2023-06-03T00:18:15.900Z] 00:18:15     INFO - Entering test bound 
[task 2023-06-03T00:18:15.905Z] 00:18:15     INFO - TEST-PASS | browser/base/content/test/tabs/browser_navigatePinnedTab.js | Tab was successfully pinned - 
[task 2023-06-03T00:18:15.905Z] 00:18:15     INFO - Buffered messages finished
[task 2023-06-03T00:18:15.906Z] 00:18:15    ERROR - TEST-UNEXPECTED-TIMEOUT | browser/base/content/test/tabs/browser_navigatePinnedTab.js | application timed out after 370 seconds with no output
[task 2023-06-03T00:18:15.906Z] 00:18:15  WARNING - Force-terminating active process(es).
```
Bug: Download remains at 0%
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2023-06-03 11:25:12+00:00
Resolved: 2023-10-03 12:03:33+00:00

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

Steps to reproduce:

I clicked on the following link...
http://ftp.ch.debian.org/debian/pool/main/p/pygobject-2/python-gobject-2_2.28.6-13+b1_amd64.deb


Actual results:

It looked like the download started (I saw the pulsing download icon) but the download remained at 0%. Even when I cancelled the download, the download icon continued to pulse


Expected results:

The file should have been downloaded to my default download folder
Bug: Browser tab closed when I searched something on google
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2023-06-03 11:54:08+00:00
Resolved: 2024-07-01 12:24:52+00:00

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

Steps to reproduce:

I opened a new tab. I googled a keyword on google on url bar



Actual results:

My browser tab is closed


Expected results:

Browsed bar should not have been closed. It's suspicious.