av9ash/GitBugs huggingface dataset:
Bug: Firefox crashes with the new implementation of Explicit Sync using Nvidia drivers v555 under Wayland
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-05-26 00:44:40+00:00
Resolved: 2024-06-19 13:10:13+00:00

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

Steps to reproduce:

-Installed Nvidia driver v555 implementing explicit sync for the compositor XWayland
-Updated package Xorg-XWayland using the pacman command on Arch Linux to the version 24.1
-Using KDE, Core and Extra testing repositories with the latest Kwin package with full explicit sync support
-Using Firefox nightly from the AUR package made by heftig: https://aur.archlinux.org/packages/firefox-nightly


Actual results:

Normal use of Firefox causes the app to crash unexpectedly when scrolling over random websites like YouTube or Reddit over the Wayland compositor using the latest Nvidia driver v555 and explicit sync. Using stable repos and driver v550 without explicit sync doesn't cause Firefox to crash, and it's completely stable.

Here's a report shown when opening Firefox through the terminal:

[juan@Asus ~]$ firefox-nightly
[Parent 13267, Main Thread] WARNING: pipe error: Bad file descriptor: file /build/firefox-nightly/src/mozilla-central/ipc/chromium/src/chrome/common/ipc_channel_posix.cc:702
Exiting due to channel error.
[GFX1-]: Wayland protocol error: wp_linux_drm_syncobj_surface_v1@67: error 4: explicit sync is used, but no acquire point is set

ExceptionHandler::WaitForContinueSignal waiting for continue signal...
ExceptionHandler::GenerateDump cloned child 16042
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
[juan@Asus ~]$ 



Expected results:

No crashes when using Firefox with explicit sync and stable experience with the browser
Bug: Potential nsIObserver loop in ActivityStream
Status: NEW
Priority: P2
Created: 2024-05-26 10:03:25+00:00
Resolved: 2024-06-03 16:49:05+00:00

[Issue here](https://searchfox.org/mozilla-central/rev/9508d23ab6de8b0734be2c95303515b08da1ce28/browser/components/newtab/lib/ActivityStream.sys.mjs#733,739,781,785).

I'm not sure if a loop can actually happen in practice, but it still would be wise to remove it. This isn't a blocking infinite loop, it just means the observer notification callback can add another observer without removing the existing one. On the initial run, if `lazy.Region.home` is falsy, a `browser-region-updated` observer will be added, and `this.geo` will be set to an empty string. If locale or region is changed, `this.geo` will be set to a non-empty string. If locale or region changes again, and `lazy.Region.home` is somehow falsy again (not sure if this is possible, but it's not ideal to rely on that expectation), a second observer will be added. Now if that same sequence of steps repeats, two observers will become four. The number of observers will double with each repetition, since each observer callback creates a new observer. These region/locale notifications firing repetitively is obviously quite unlikely outside of rare edge cases, but if there's ever a regression in any of the region/locale code that results in repeating spurious notifications, this might turn an otherwise silent bug into a crash.

It could be crash-proofed by just changing line 739 to this:

```js
if (!this._regionObserverAdded) {
  Services.obs.addObserver(this, lazy.Region.REGION_TOPIC);
  this._regionObserverAdded = true;
}
```
Bug: Firefox 126.0 constantly opens with blank pages.
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2024-05-26 12:24:01+00:00
Resolved: 2024-07-25 13:17:47+00:00

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

Steps to reproduce:

I tried updating but no updates are available.  Close firefox 3 times then reopening brings up the normal home page.  The next time you open its back to blank pages.  It all started with 126.0


Actual results:

No changes


Expected results:

Firefox should open normally each time but does not
Bug: When not in full screen, Firefox will show empty space in the top left before the first tab.
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2024-05-26 14:34:58+00:00
Resolved: 2024-06-05 16:34:15+00:00

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

Steps to reproduce:

Remove 'Firefox View' from the top left in the 'Customize Toolbox' section. There should be no space between the first tab and the top left of the app when in full screen. Then, click 'Restore Down' in the top right (left of the 'Close' button). 


Actual results:

Any size you resize the screen to displays a space in the top left before the first tab. Likely because the lack of a button in the top left hasn't been accounted for, so it still displays the space as if the 'Firefox View' button was there (this button is there by default when you first install the browser).


Expected results:

There should be no space between the first tab and the top left — the same as if you were in full screen.
Bug: [Experiment] “Dismiss” button appears as “X”, instead of appearing as a button with a dropdown menu
Status: RESOLVED
Priority: P1
Resolution: WONTFIX
Created: 2024-05-27 11:55:22+00:00
Resolved: 2024-05-30 08:40:13+00:00

**[Affected versions]:**
- Firefox build version >=123

**[Affected Platforms]:**
- Windows 10 x64
- macOS Ventura 13.6.2
- Ubuntu 22.04 x64

**[Prerequisites]:**
- Have a Firefox build version >=123.
- Have a browser client enrolled in a Nimbus experiment that enables the “Discovery Search” message: 
https://experimenter.services.mozilla.com/nimbus/discovery-of-search-sap-early-day-en/summary

**[Steps to reproduce]:**
1. Open the browser from the prerequisites
2. Open a new tab.
3. Notice how the “Dismiss” button from the “Discovery Search” message looks.

**[Expected result]:**
- “Dismiss” button is looking as it is presented in the documentation; “Dismiss” button appears as a button with a dropdown menu

**[Actual result]:**
- “Dismiss” button is not looking as it is presented in the documentation; “Dismiss” button appears as “X”, instead of appearing as a button with a dropdown menu


**[Notes]:**
- A screenshot of this issue is attached.
- This issue is occurring for early day users and existing users, too, and for all the branches.
Bug: Twitter (and not X) is installed as a default top site
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-05-27 20:34:48+00:00
Resolved: 2024-06-19 13:29:24+00:00

In the US and likely other places, Twitter is showing at a default top site. This should change to X, or be replaced with another site.
Bug: Intermittent browser/components/urlbar/tests/browser/browser_close_other_panels.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2024-05-27 23:19:56+00:00
Resolved: 2024-07-03 12:03:18+00:00

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

---
```
[task 2024-05-27T21:22:35.607Z] 21:22:35     INFO - TEST-START | browser/components/urlbar/tests/browser/browser_close_other_panels.js
[task 2024-05-27T21:23:20.614Z] 21:23:20     INFO - TEST-INFO | started process screencapture
[task 2024-05-27T21:23:20.744Z] 21:23:20     INFO - TEST-INFO | screencapture: exit 0
[task 2024-05-27T21:23:20.745Z] 21:23:20     INFO - Buffered messages logged at 21:22:35
[task 2024-05-27T21:23:20.745Z] 21:23:20     INFO - Entering test bound 
[task 2024-05-27T21:23:20.746Z] 21:23:20     INFO - TEST-PASS | browser/components/urlbar/tests/browser/browser_close_other_panels.js | The panel is closed to begin with. - "closed" == "closed" - 
[task 2024-05-27T21:23:20.746Z] 21:23:20     INFO - Buffered messages finished
[task 2024-05-27T21:23:20.747Z] 21:23:20     INFO - TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/browser/browser_close_other_panels.js | Test timed out - 
[task 2024-05-27T21:23:20.747Z] 21:23:20     INFO - GECKO(2774) | Completed ShutdownLeaks collections in process 2774
[task 2024-05-27T21:23:20.747Z] 21:23:20     INFO - TEST-START | Shutdown
```
Bug: DLP content messages are not RTL
Status: NEW
Priority: --
Created: 2024-05-28 06:03:32+00:00
Resolved: 2024-06-18 19:40:23+00:00

**Found in**
* 128.0a1 (2024-05-27)

**Affected versions**
* 128.0a1 (2024-05-27)


**Tested platforms**
* Affected platforms: Windows 10x64, Windows 11
* Unaffected platforms: Ubuntu 23, macOS 

**Preconditions**
* Download the DLP test assets from https://drive.google.com/file/d/1yjqVRuxdKV3WnO7D2wzMgDXBuYBxUgVw/view
* Create a distribution folder inside the Firefox folder and paste the policies-1.json to it and then rename it to policies.json
* run the DLP agent in CMD using: .\content_analysis_sdk_agent.exe --user --toblock=.*\d{3}-?\d{2}-?\d{4}.* --towarn=.*warn.* --delays=10
* use RTL build (e.g he or ar)

**Steps to reproduce**
1. Copy the “123456789” text in the clipboard and open Wikipedia.
2. Paste the text and observe the message while the scan is ongoing and after the scan is finished.

**Expected result** 
* All message content is in right to left (RTL).

**Actual result**
* Only the button and the first part of the message ("You're not permitted to paste this content") are right to left (RTL). The middle part of the message is not in right to left (RTL)



**Regression range**
* Not a regression. New implementation.

**Additional notes**
* Attached a screenshot.
* This applies to warning messages.
Bug: Firefox 126: UI is partially localized with language packs
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2024-05-28 10:26:03+00:00
Resolved: 2024-10-02 12:51:47+00:00

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

Steps to reproduce:

Update to FF 126 as part of the Manjaro update


Actual results:

The menu language can no longer be changed to German even though the language is installed
Bug: Extensions managing tabs still show original tab title for http auth spoof scenario
Status: NEW
Priority: P3
Created: 2024-05-28 10:47:56+00:00
Resolved: 2024-05-29 20:16:49+00:00

Bug 791594 includes a patch to update the tab title when a http auth dialog is shown on top of an unrelated page. This change does not seem to affect the extension API though. When testing the PoC with Sideberry installed it still shows the original tab title.

PoC: https://eviltrap.site/trap/http-auth-prompt-spoof
Bug: Missing translation for menus
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-05-28 11:40:09+00:00
Resolved: 2024-05-29 11:45:46+00:00

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

Steps to reproduce:

1. Go to about:preferences, then Language
2. Select any other than default English (US) language (tested RU, DE, BY)
3. Open context menu with RMB or open application menu


Actual results:

Menu items are displayed in English


Expected results:

Menu items are displayed in selected language
Bug: Print preview window can be accessed while DLP dialog is active
Status: NEW
Priority: --
Created: 2024-05-28 11:45:26+00:00
Resolved: 2024-06-18 19:40:39+00:00

**Found in**
* 128.0a1 (2024-05-27)

**Affected versions**
* 128.0a1 (2024-05-27)

**Preconditions**
* Download the DLP test assets from https://drive.google.com/file/d/1yjqVRuxdKV3WnO7D2wzMgDXBuYBxUgVw/view 
* Create a distribution folder inside the Firefox folder and paste the policies-1.json to it and then rename it to policies.json
* Run the DLP agent in CMD using: .\content_analysis_sdk_agent.exe --user --toblock=.\d{3}-?\d{2}-?\d{4}. --towarn=.warn. --delays=10

**Tested platforms**
* Affected platforms: Windows 10/11
* Unaffected platforms:Ubuntu 22.04, macOS 12.6.6

**Steps to reproduce**
1. Navigate to wikipedia.org
2. Open up a document in an external program (for example Notepad) and type “123456789” into it and copy it
3. Return to Firefox and paste the “123456789” into the search bar 
4. While the content is being analyzed, open the Print preview either by clicking the application menu -> Print option or by using the Ctrl+P keys
5. Observe the behavior

**Expected result**
* Print preview window is not displayed

**Actual result**
* Print preview window is displayed in Loading state

**Regression range**
* This is not a regression as this is a new feature

**Additional notes**
* See the attached video
* After the scan is finalized, the Print preview window is automatically dismissed
* Reproducing for the rest of the DLP messages as well
Bug: After installing the Dutch language pack, you cannot select it in the "Languages" right-mouse-button menu and it does not spell-check in Dutch
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2024-05-28 13:34:04+00:00
Resolved: 2024-06-04 10:53:17+00:00

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

Steps to reproduce:

Install the dutch language pack from: 
https://addons.mozilla.org/nl/firefox/addon/nederlands-nl-language-pack/

Choose any text dialog, type anything and right click the text. Go to "Languages" and observe there is no Dutch option. 

I can see the language pack in the Settings > Addons > Languages settings window. Several other reviews confirm this (look for recent 1-star reviews):
https://addons.mozilla.org/nl/firefox/addon/nederlands-nl-language-pack/reviews/



Actual results:

There is no Dutch option


Expected results:

There is a Dutch option
Bug: Pasting copied content into search engine bar via right-click triggers DLP analysis
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2024-05-28 13:56:54+00:00
Resolved: 2024-06-07 05:51:38+00:00

**Found in**
* 128.0a1 (2024-05-27)

**Affected versions**
* 128.0a1 (2024-05-27)

**Preconditions**
* Download the DLP test assets from https://drive.google.com/file/d/1yjqVRuxdKV3WnO7D2wzMgDXBuYBxUgVw/view 
* Create a distribution folder inside the Firefox folder and paste the policies-1.json to it and then rename it to policies.json
* Run the DLP agent in CMD using: .\content_analysis_sdk_agent.exe --user --toblock=.\d{3}-?\d{2}-?\d{4}. --towarn=.warn. --delays=10

**Tested platforms**
* Affected platforms: Windows 10/11
* Unaffected platforms:Ubuntu 22.04, macOS 12.6.6

**Steps to reproduce**
1. Open up a document in an external program (for example Notepad) and type “123456789” into it and copy it (Ctrl+C)
2. Open a new tab and paste the copied text into the search engine bar under the Firefox logo by using the right click -> Paste option
3. Observe the behavior

**Expected result**
* The text shows up immediately, without being analyzed by DLP

**Actual result**
* “Scan in progress” dialog is displayed. The content is analyzed and blocked afterwards

**Regression range**
* This is not a regression as this is a new feature

**Additional notes**
* See the attached video
* The scan is triggered regardless of the pasted content
* Not reproducing if pasting the copied content using Ctrl + V
* Not reproducing when pasting the content in the URL address bar
Bug: Intermittent browser/base/content/test/tabMediaIndicator/browser_webAudio_silentData.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2024-05-28 14:03:23+00:00
Resolved: 2024-07-17 12:03:36+00:00

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

---
```
TEST-START | browser/base/content/test/tabMediaIndicator/browser_webAudio_silentData.js
[task 2024-05-28T12:04:57.548Z] 12:04:57     INFO - TEST-INFO | started process screentopng
[task 2024-05-28T12:04:59.672Z] 12:04:59     INFO - TEST-INFO | screentopng: exit 0
[task 2024-05-28T12:04:59.675Z] 12:04:59     INFO - Buffered messages logged at 12:04:11
[task 2024-05-28T12:04:59.675Z] 12:04:59     INFO - Entering test bound testSilentAudioContext
[task 2024-05-28T12:04:59.675Z] 12:04:59     INFO - - create new tab -
[task 2024-05-28T12:04:59.675Z] 12:04:59     INFO - Buffered messages finished
[task 2024-05-28T12:04:59.677Z] 12:04:59     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/tabMediaIndicator/browser_webAudio_silentData.js | Test timed out - 
[task 2024-05-28T12:04:59.677Z] 12:04:59     INFO - GECKO(4047) | Completed ShutdownLeaks collections in process 4047
[task 2024-05-28T12:04:59.677Z] 12:04:59     INFO - TEST-START | Shutdown
[task 2024-05-28T12:04:59.679Z] 12:04:59     INFO - Browser Chrome Test Summary
[task 2024-05-28T12:04:59.680Z] 12:04:59     INFO - Passed:  80
[task 2024-05-28T12:04:59.682Z] 12:04:59     INFO - Failed:  1
[task 2024-05-28T12:04:59.683Z] 12:04:59     INFO - Todo:    0
[task 2024-05-28T12:04:59.684Z] 12:04:59     INFO - Mode:    e10s
[task 2024-05-28T12:04:59.684Z] 12:04:59     INFO - *** End BrowserChrome Test Results ***
[task 2024-05-28T12:11:09.689Z] 12:11:09     INFO - TEST-UNEXPECTED-TIMEOUT | browser/base/content/test/tabMediaIndicator/browser_webAudio_silentData.js | application timed out after 370 seconds with no output
[task 2024-05-28T12:11:09.690Z] 12:11:09     INFO - TEST-INFO took 417505ms
[task 2024-05-28T12:11:09.691Z] 12:11:09     INFO - Buffered messages finished
[task 2024-05-28T12:11:09.691Z] 12:11:09  WARNING - Force-terminating active process(es).
[task 2024-05-28T12:11:09.691Z] 12:11:09     INFO - Determining child pids from psutil...
[task 2024-05-28T12:11:09.707Z] 12:11:09     INFO - [4151, 4195, 4238, 4313, 4338, 4391, 4400, 5103, 5164, 5202]
```
Bug: Random character displayed in the Tab Preview when hovering over the in focus tab and PID is displayed
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2024-05-28 14:08:42+00:00
Resolved: 2024-05-30 08:26:06+00:00

**Found in**
* Latest Nightly 128.0a1

**Affected versions**
* Nightly 128.0a1

**Tested platforms**
* Affected platforms: MacOS 13, Windows 11 and Ubuntu 22.04
* Unaffected platforms: none

**Preconditions**
* `browser.tabs.cardPreview.enabled` - `true`

**Steps to reproduce**
1. Visit a few pages in different tabs
2. Hover over the page that the focus is on

**Expected result**
* Tab preview has all the information displayed (title, domain and PID).

**Actual result**
* A random [A] character can be seen in the right side of the tab preview in the same row with the PID

**Regression range**
* This happens after bug 1889369 was fixed.

**Additional notes**
* If the PID is not displayed use the pref `browser.tabs.tooltipsShowPidAndActiveness` - `true` to enable displaying it.
* Only appears when the PID is displayed and only on the tabs in focus, if moving the focus from a tab that previously displayed the character and hovering over the tab will make that the [A] character to not be displayed anymore.
Bug: Shift+Middle button click on a bookmark item in the library window opens the previously selected item instead of the clicked item.
Status: NEW
Priority: P5
Created: 2024-05-28 16:54:27+00:00
Resolved: 2024-06-17 15:21:51+00:00

Steps to reproduce:
1. Open Library (Ctrl+Shift+O)
2. Expand the tree/folder so that there are many bookmark items in the right pane.
3. Make one of any bookmark item selected.

4. Shift+middle button click on any other unselected bookmark item.

Actual Results:
Instead of the clicked bookmark item, the bookmark item selected in step 3 will be opened.

Expected Results:
The bookmark item you clicked on should be opened.
Bug: SelectTranslationsPanel languageInfo cache is not correctly cleared between page loads
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2024-05-28 17:12:21+00:00
Resolved: 2024-06-21 20:41:10+00:00

### Description

Bug 1870368 patch [D211230](https://phabricator.services.mozilla.com/D211230) introduced a cache to the `SelectTranslationsPanel` which includes the document's determined language tag.

This cached information is occasionally used in our fallback algorithm for when we detect that the selected text is in a language that is not yet supported by translations. In this case, we check the document's language tag, to see if the page's language is supported, and attempt to fall back to that in case the selected text was misidentified. 

This cache was not being properly cleared between page loads, and it causes the panel to fall back to the document language of the previous page in this scenario, rather than the current page. 

---

### Steps to reproduce

* Go to a page in a supported language, such as https://fi.wikipedia.org. 
* Select a paragraph of text on the page.
* Open the `SelectTranslationsPanel` from the right-click context menu, and ensure that a valid translation completes in the document's language.
* Next, navigate to https://ru.wikipedia.org and select the "Welcome to Wikipedia" at the top of the page: "Добро пожаловать в Википедию". Note, it is important to test with this exact string because our current language detector misidentifies this string as Serbian, which we currently do not support.
* Open the `SelectTranslationsPanel` from the right-click context menu.

**Expected Behavior**
The `SelectTranslationsPanel` opens and translates from Russian, based on the **current** document's language tag.

**Actual Behavior**
The `SelectTranslationsPanel` opens and translates from the previous document's language (Finnish in this STR), based on the **previous** document's cached language tag. 

---

### Steps to implement

* Ensure that the cache is properly cleared between navigating to other pages.

---

### Tests to implement

* Create a test case the reproduces the above situation, and ensure that the fallbacking is for the correct language.
Bug: Safe browsing "Go back" doesn't respect new tab preference
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-05-28 19:37:23+00:00
Resolved: 2024-06-03 16:58:32+00:00

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

Steps to reproduce:

0) Clear the startup cache about:support to ensure safe browsing backoff is reset (optional)
1) Set Settings > Home > New tabs to Blank Page (or browser.newtabpage.enabled to false)
2) Ensure Privacy & Security > Block dangerous and deceptive content is enabled by default
3) Visit https://testsafebrowsing.appspot.com/s/phishing.html
4) Click "Go back"
4.5) Alternatively, open the details panel, click "ignore the risk", then click "Get me out of here!" in the toolbar that appears


Actual results:

Firefox Home was opened


Expected results:

The user's selected new tab preference should've been opened
Alternatively, either of the buttons mentioned could take the user back to the page they were previously on instead of to a NTP