av9ash/GitBugs huggingface dataset:
Bug: The Review Checker Callout 3 panel is not displayed after 5 or more days have passed and the opted-out user reached a product details page
Status: RESOLVED
Priority: P1
Resolution: DUPLICATE
Created: 2024-01-29 12:39:25+00:00
Resolved: 2024-02-05 19:24:09+00:00

**Found in**
* Nightly 124.0a1 (2024-01-29)

**Affected versions**
* Nightly 124.0a1 (2024-01-29)

**Affected platforms**
* All

**Preconditions:**
Set the browser.shopping.experience2023.enabled - TRUE
Set the browser.shopping.experience2023.optedIn - 0
Set nimbus.debug to true
Set messaging-system.rsexperimentloader.collection_id to nimbus-preview
Set browser.newtabpage.activity-stream.asrouter.devtoolsEnabled to true
security.ssl.enable_ocsp_stapling - False

Reach the following link: 
about:studies?optin_slug=review-checker-callouts-v11-experiment&optin_branch=treatment-a&optin_collection=nimbus-preview

**Steps to reproduce**
1. Reach : https://www.amazon.com/XUEGW-Computer-Assembly-Required-Foldable/dp/B0CDS1238W/ref=sr_1_2_sspa?keywords=desk&qid=1706529514&sr=8-2-spons&sp_csd=d2lkZ2V0TmFtZT1zcF9hdGY&th=1
2. Close the Review Checker from the X Close button.
3. Click Got it at the 1st Callout panel.
4. Close Firefox and Advance system time 5 days.
5. Launch Firefox and Reach https://www.amazon.com/XUEGW-Computer-Assembly-Required-Foldable/dp/B0CDS1238W/ref=sr_1_2_sspa?keywords=desk&qid=1706529514&sr=8-2-spons&sp_csd=d2lkZ2V0TmFtZT1zcF9hdGY&th=1

**Expected result**
* The New Callout panel 3 should be displayed.

**Actual result**
* Even after passing another 5 days the New Version of Callout 3 is not displayed at all.

**Regression range**
Not a Regression
Bug: No dismiss telemetry is registered if any of the MailTo infobar is dismissed by clicking the "X" button
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-01-29 13:34:33+00:00
Resolved: 2024-04-24 11:27:21+00:00

**[Affected versions]:**
- Firefox Release 122.0 (Build ID: 20240118164516)
- Firefox Beta 123.0b3 (Build ID: 20240126091653)
- Firefox Nightly 124.0a1 (Build ID:20240128212206)

**[Affected Platforms]:**
- macOS 13.1
- Windows 10 x64
- Ubuntu 20.04

**[Prerequisites]:**
- Firefox is NOT set as the default OS mailto handler (Windows Settings -> Choose the default app by protocol -> MAILTO:Thunderbird)
- The "Always ask" action is set for the "mailto" content type in about:preferences -> Applications.
- Have a new profile with the following prefs set:
browser.mailto.dualPrompt set to true
browser.mailto.dualPrompt.os set to true 
browser.mailto.prompt.os set to true

**[Steps to reproduce]:**
1. Open the browser with the settings described in prerequisites.
2. Navigate to about:glean, set a tag and select the "metrics" type.
3. Navigate to the following test website: https://snappymail.eu/demo/.
4. Click the "SIGN IN" button.
5. Click the "X" button for both infobars displayed.
6. Navigate back to about:glean and click the "Apply setting and submit ping".
6. Navigate to https://debug-ping-preview.firebaseapp.com/pings/, choose your tag set in Step 2. 
7. Verify the latest "metrics" ping.


**[Expected result]:**
- The "protocolhandler.mailto.prompt_clicked" is registered and has the "dismiss_os_default": 1" and "dismiss_local_default": 1 values.

**[Actual result]:**
- The "protocolhandler.mailto.prompt_clicked" is NOT registered.

**[Notes]:**
- The telemetry is correctly registered if the "Not now" button is clicked.
- Attached a screen recording of the issue.
Bug: Screenshot buttons overlap with the selected area when the selection is made on a partially hidden element
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-01-29 15:19:30+00:00
Resolved: 2024-03-14 18:55:25+00:00

**Found in**
* 123.0b3

**Affected versions**
* 124.0a1 
* 123.0b3
* 122.0


**Affected platforms**
* Windows 10
* macOS 12

**Steps to reproduce**
1. From Menu - More tools - Customise toolbar..  drag the Screenshot icon inside the toolbar 
2. Open a long page (eg. [link](https://www.mozilla.org/en-US/privacy/firefox/))
3. Perform a selection through screenshot option on an area that is not entirely visible. 
4. Scroll down and observe the buttons


**Expected result**
* [X], Copy and Download buttons are out of the selected area.

**Actual result**
* [X], Copy and Download buttons are in the selected area.

**Regression range**
* It doesn’t seem to be a regression, reproducible way back to 97.0a1.

**Additional notes**
* Once the selection is clicked the Buttons are moved outside the selection.
* The buttons are functional if the user interacts directly with them.
Bug: Update a11y review documentation to reference assigned value
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2024-01-29 22:12:36+00:00
Resolved: 2024-02-22 09:24:10+00:00

In bug 1877292 we added a new option to the Accessibility Review field in bugzilla, our docs should explain what this field is and how it is used.
Bug: Firefox 122 system theme missing borders (Linux/X11)
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2024-01-30 11:46:26+00:00
Resolved: 2024-02-29 03:25:45+00:00

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

Steps to reproduce:

I'm using FF with the system theme. In Firefox 121, the URL bar and search bar had a white background and a contrast enhancing outline. There was also a line separating the tabs and toolbox bars.

After updating to Firefox 122, the background of various UI elements including the URL bar became grey (probably the GTK default grey?), and the URL and search bar outlines are gone. I didn't see any theme related changes mentioned in the release notes...

This is on a Debian system but I have checked that this also happens with the official 64 bit Linux build using a fresh profile, and it's still the same with the 124.0a1 nightly release.

What may be unusual about my installation is that there is no themed window manager, so all "system defaults" will be built into GTK+.
Bug: Make the feature callout dismiss button transparent
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2024-01-30 18:58:04+00:00
Resolved: 2024-05-03 22:02:13+00:00

Right now, the feature callout dismiss button takes on [the background of the callout](https://searchfox.org/mozilla-central/rev/f6e3b81aac49e602f06c204f9278da30993cdc8a/browser/components/asrouter/content-src/styles/_feature-callout.scss#356). This is not ideal because sometimes we want to display the button on top of images. We want it to start transparent and then only gain a standard background color on hover/active states.
Bug: Decline in sync success rates for tabs and clients engines on Beta
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2024-01-30 21:26:49+00:00
Resolved: 2024-02-21 20:55:55+00:00

Beginning on 1/23/24 the sync success rates for the clients and tabs engines on Firefox Desktop beta began to decline (see [here](https://sql.telemetry.mozilla.org/queries/85526?p_Days=60&p_channel=beta&p_engine_name=all-engines#211801) for details). There was also a drop in the clients engine sync success rate on Nightly starting 1/13/24 which _*may*_ be related (see [here](https://sql.telemetry.mozilla.org/queries/85526?p_Days=60&p_channel=nightly&p_engine_name=all-engines#211801)). The tabs engine success rate on Nightly is also decreasing, but much more gradually.

Checking the [Desktop Sync Error Message graph](https://sql.telemetry.mozilla.org/queries/86456?p_channel=beta&p_engine_name=all-engines#214076) there is an increase in remote setup failure and UTF-8 errors for both the tabs and clients engines around the same time period.
Bug: URL constructor doesn't parse URL correctly
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-01-30 22:57:03+00:00
Resolved: 2024-01-31 17:07:14+00:00

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

Steps to reproduce:

const url = new URL("file://foo/bar/baz")


Actual results:

Got these values for the properties:

host: ""
hostname: ""
href: "file:///bar/baz"
origin: "null",
pathname: "/bar/baz"
protocol: "file:"



Expected results:

host: "foo"
hostname: "foo"
href: "file://foo/bar/baz"
origin: "file://",
pathname: "/bar/baz"
protocol: "file:"
Bug: "Open previous windows and tabs" setting ignored on opening normal window with private window open
Status: NEW
Priority: P2
Created: 2024-01-31 03:13:03+00:00
Resolved: 2024-05-17 15:46:36+00:00

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

Steps to reproduce:

1. Ensure "Open previous windows and tabs" is unchecked
2. With no windows open, open a normal window and navigate away from the home page (e.g. to mozilla.org)
3. Close the normal window
4. Open a private window (directly, e.g. from taskbar icon right-click)
5. Open a normal window


Actual results:

The page from step 2 is reopened on the normal window.


Expected results:

The normal window in step 5 should have been opened to the home page. Switching steps 3 and 4 gets the same result, but the original order is more impactful. For example, I might close a normal window with multiple tabs open, and then hours later open a private window, and then a normal window. I do not expect the past session to reopen.

This seems somewhat recent, and it also seems kind of the opposite situation of 1833007.
Bug: Mouse wheel scrolling in bookmarks drop-down list is disabled when pointer hovers over folder,  opening subfolder list
Status: NEW
Priority: P5
Created: 2024-01-31 05:19:37+00:00
Resolved: 2024-02-15 14:00:34+00:00

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

Steps to reproduce:

While mouse-wheel scrolling in the overflow drop-down list of bookmark-toolbar bookmarks, at some point the mouse pointer momentarily hovers over a folder in the list, spontaneously opening a sub-menu of the folder's contents.


Actual results:

At that moment mouse-wheel scrolling of the drop-down list gets disabled.


Expected results:

The ability to mouse-wheel scroll the list should have continued, uninterrupted.


Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0
Bug: The privileged content process starts image animations in the background and keeps vsync ticking forever
Status: NEW
Priority: --
Created: 2024-01-31 11:15:24+00:00
Resolved: 2024-08-24 14:55:28+00:00

See this profile: https://share.firefox.dev/3vWPfat

In the screenshot track you can see that the about:newtab page was not visible (I just profiled loading the wikipedia home page).

In the markers of the privileged content process, there is a network load for [a 102KB gif image](https://img-getpocket.cdn.mozilla.net/592x296/filters:format(jpeg):quality(60):no_upscale():strip_exif()/https%3A%2F%2Fs3.us-east-1.amazonaws.com%2Fpocket-curatedcorpusapi-prod-images%2F3c5ebd59-257f-4311-801f-373d192a84f4.gif), after which there are "RefreshDriverTick - Tick reasons: HasImageAnimations" markers at 120Hz.
The process priority is "background".

The root cause is probably bug 1548683, but I wonder if there might be additional things we might do to avoid image animations. Especially as even opening the new tab page is not enough to actually see the animation, as the image is below the fold.
Bug: The privileged content process animates scollbars while in the background
Status: NEW
Priority: --
Created: 2024-01-31 11:44:08+00:00
Resolved: 2024-08-24 14:55:34+00:00

See this profile: https://share.firefox.dev/49hHSca

There are at least 6 opacity transitions on scrollbar elements. The process priority is "background".

In the screenshot track you can see that the about:newtab page was not visible (I just profiled loading the wikipedia home page).

The root cause is probably bug 1548683, but I wonder if there might be additional things we might do to avoid image animations. Especially as even opening the new tab page is not enough to actually see the animation, as the image is below the fold.
Bug: Intermittent browser/components/firefoxview/tests/browser/browser_opentabs_tab_indicators.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: FIXED
Created: 2024-01-31 12:18:14+00:00
Resolved: 2024-02-05 06:57:42+00:00

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

---
```
[task 2024-01-31T11:14:06.180Z] 11:14:06     INFO - TEST-PASS | browser/components/firefoxview/tests/browser/browser_opentabs_tab_indicators.js | The tab has the mute button showing. - 
[task 2024-01-31T11:14:06.180Z] 11:14:06     INFO - Buffered messages finished
[task 2024-01-31T11:14:06.180Z] 11:14:06     INFO - TEST-UNEXPECTED-FAIL | browser/components/firefoxview/tests/browser/browser_opentabs_tab_indicators.js | Uncaught exception in test bound test_sound_playing_muted_indicator - The tab doesn't have the soundplaying attribute. - timed out after 50 tries.
[task 2024-01-31T11:14:06.182Z] 11:14:06     INFO - Leaving test bound test_sound_playing_muted_indicator
[task 2024-01-31T11:14:06.182Z] 11:14:06     INFO - GECKO(8096) | MEMORY STAT | vsize 1138MB | vsizeMaxContiguous 1293MB | residentFast 372MB | heapAllocated 145MB
[task 2024-01-31T11:14:06.183Z] 11:14:06     INFO - TEST-OK | browser/components/firefoxview/tests/browser/browser_opentabs_tab_indicators.js | took 8653ms
[task 2024-01-31T11:14:06.183Z] 11:14:06     INFO - Not taking screenshot here: see the one that was previously logged
[task 2024-01-31T11:14:06.185Z] 11:14:06     INFO - TEST-UNEXPECTED-FAIL | browser/components/firefoxview/tests/browser/browser_opentabs_tab_indicators.js | Found an unexpected tab at the end of test run: http://mochi.test:8888/browser/dom/base/test/file_audioLoop.html - 
[task 2024-01-31T11:14:06.189Z] 11:14:06     INFO - Not taking screenshot here: see the one that was previously logged
[task 2024-01-31T11:14:06.191Z] 11:14:06     INFO - TEST-UNEXPECTED-FAIL | browser/components/firefoxview/tests/browser/browser_opentabs_tab_indicators.js | Found an unexpected tab at the end of test run: about:firefoxview#opentabs - 
```
Bug: Intermittent browser/components/firefoxview/tests/browser/browser_opentabs_cards.js | single tracking bug
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2024-01-31 12:22:04+00:00
Resolved: 2024-04-01 07:03:56+00:00

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

---
```
[task 2024-01-31T11:24:48.741Z] 11:24:48     INFO - TEST-PASS | browser/components/firefoxview/tests/browser/browser_opentabs_cards.js | The container shows one column when one window is open. - 
[task 2024-01-31T11:24:48.745Z] 11:24:48     INFO - Console message: 1706700122260	FirefoxView.TabsSetup	DEBUG	updateViewVisibility for instance: 6360776, visibility: unloaded
[task 2024-01-31T11:24:48.746Z] 11:24:48     INFO - Console message: 1706700122260	FirefoxView.TabsSetup	DEBUG	Resetting timestamp and tabs pending flags as there are no visible views
[task 2024-01-31T11:24:48.746Z] 11:24:48     INFO - Console message: 1706700122261	FirefoxView.TabsSetup	DEBUG	updateViewVisibility for instance: 6360776, visibility: hidden
[task 2024-01-31T11:24:48.747Z] 11:24:48     INFO - Console message: 1706700122261	FirefoxView.TabsSetup	DEBUG	Resetting timestamp and tabs pending flags as there are no visible views
[task 2024-01-31T11:24:48.748Z] 11:24:48     INFO - Buffered messages logged at 11:23:18
[task 2024-01-31T11:24:48.749Z] 11:24:48     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 1
[task 2024-01-31T11:24:48.749Z] 11:24:48     INFO - Buffered messages finished
[task 2024-01-31T11:24:48.751Z] 11:24:48     INFO - TEST-UNEXPECTED-FAIL | browser/components/firefoxview/tests/browser/browser_opentabs_cards.js | Test timed out - 
[task 2024-01-31T11:24:48.752Z] 11:24:48     INFO - GECKO(5565) | Completed ShutdownLeaks collections in process 5565
```
Bug: sync of default theme when adding new device to sync
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-01-31 12:26:46+00:00
Resolved: 2024-01-31 21:09:47+00:00

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

Steps to reproduce:

- on my pc running windows10 (device1) I had enabled sync
- on device1 I set a theme of my choice and then I synced
- on a different pc running windows10 (device2) I have enabled sync with same account used on device1



Actual results:

-after sync on device 2 is completed the theme on device1 was changed to the default (light theme).
it seems that device2 starts syncing and propagates to device1 the default theme.
it should be the opposite: on the new device2 I want to see the theme I previously selected on device1.




Expected results:

-device1 should keep the theme I had previously chosen
- and device2 should have been set to use the same theme as device1
Bug: The End Private Session button is not restored after restoring defaults while the normal browsing window is opened and the browser was not restarted
Status: NEW
Priority: P3
Created: 2024-01-31 15:08:21+00:00
Resolved: 2024-06-19 15:13:18+00:00

**Found in**
* 123.0b4



**Affected versions**


* 124.0a1 (2024-01-26)
* 123.0b4
* 122.0







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

**Preconditions**
* new profile

**Steps to reproduce**
1. Open about:config and set `browser.privatebrowsing.resetPBM.enabled` and `browser.privatebrowsing.felt-privacy-v1 ` to true
2. Open a new private window and enter customize mode.
4. Remove the End Private Session button and click Done.
5. Enter customize mode and click on restore defaults.


**Expected result** 
* The End Private Session button is restored

**Actual result**
* The End Private Session button is not restored





**Regression**
* not a regression. Reproducible with 120.0a1 (2023-09-28) after bug 1846498.












**Additional notes**
* Attached a screen recording.
* The issue does not reproduce if a browser restart is performed after enabling the feature.
Bug: Ensure that "action" property remains when dispatching spotlight telemetry
Status: NEW
Priority: P3
Created: 2024-01-31 17:43:44+00:00
Resolved: 2024-03-19 21:18:26+00:00

Because of the way that spotlight is configured to use `defaultDispatch`, the `action` property of the telemetry data that is initially created gets left behind and isn't sent with the `sendTelemetry` call [in this code block](https://searchfox.org/mozilla-central/rev/762f24e00a9548d80ebba1b985c871ba6d9b829d/browser/components/newtab/lib/Spotlight.jsm#35-40). Because of this, [the spotlight policy](https://searchfox.org/mozilla-central/rev/2a867dd1ab015c3ef24b774a57709fb3b3dc4961/browser/components/newtab/lib/TelemetryFeed.sys.mjs#525-531) doesn't get applied, which ultimately causes null pings in our telemetry data that coincide with spotlight pings.

It would be beneficial to address this so that all spotlight pings have the spotlight policy applied appropriately, so the data is represented appropriately without null pings.
Bug: Closing Firefox using the cross on macos doesn't bring back previous tabs
Status: NEW
Priority: P3
Created: 2024-01-31 21:25:52+00:00
Resolved: 2024-09-27 21:23:29+00:00

I'm not sure if this bug belongs in this component, but it is related to app startup.

I have the **open previous windows and tabs** option checked in about:preferences, and expect my windows and tabs to stay once I close firefox. I tend to use the top left cross to close applications sometimes on macos (and am aware that this doesn't actually quit the application). However, once I close firefox with the cross, and reopen it, none of my tabs are restored. It works as expected if I Quit firefox and reopen.

This is reproducible on release and nightly, and I noticed the same behaviour on chrome. I'm not sure if this is intended, since I suspect many people close their windows using the cross and expect to get their tabs back. Attached a video for reference.
Bug: [RTL] Arrows in the open tabs "more" menu are pointing in the wrong direction
Status: NEW
Priority: P3
Created: 2024-01-31 22:27:41+00:00
Resolved: 2024-02-15 22:33:49+00:00

Specifically, this:
https://searchfox.org/mozilla-central/rev/6e2e933cd6b7931e1d4e8bd8af8daa9788b27760/toolkit/content/widgets/panel-list/panel-item.css#89-91
should be working, but it isn't.
Curiously, if I change the `rtl` to `ltr` it starts working, even though the document is most certainly RTL. Is it because it's in the shadow root or something?
Bug: Hovering a tab in a background window still opens a preview and pulls the window to the foreground
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-02-01 12:59:07+00:00
Resolved: 2024-02-06 15:45:12+00:00

If Firefox is a background window then moving the mouse over a tab now causes the tab preview to appear and brings the Firefox window to the foreground, though it doesn't actually focus it.
Bug: Unable to navigate with NVDA using Down arrow from the X Close button of the Review Checker Callouts v1.1
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2024-02-01 13:36:16+00:00
Resolved: 2024-02-26 16:21:39+00:00

**Found in**
* Nightly 124.0a1 (2024-02-01)

**Affected versions**
* Nightly 124.0a1 (2024-02-01)
ALL version where the user is Enrolled in the experiment.

**Affected platforms**
* All

**Preconditions:**
Set the browser.shopping.experience2023.enabled - TRUE
Set the browser.shopping.experience2023.optedIn - 1
Set nimbus.debug to true
Set messaging-system.rsexperimentloader.collection_id to nimbus-preview
Set browser.newtabpage.activity-stream.asrouter.devtoolsEnabled to true
security.ssl.enable_ocsp_stapling - False

Reach the following link: 
about:studies?optin_slug=review-checker-callouts-v11-experiment&optin_branch=treatment-a&optin_collection=nimbus-preview

ENABLE NVDA

**Steps to reproduce**
1. Reach : https://www.amazon.com/XUEGW-Computer-Assembly-Required-Foldable/dp/B0CDS1238W/ref=sr_1_2_sspa?keywords=desk&qid=1706529514&sr=8-2-spons&sp_csd=d2lkZ2V0TmFtZT1zcF9hdGY&th=1
2. Close the Review Checker from the X Close button.
3. Reach the X Close button from the Callout using Keyboard navigation.
4. Hit The Down Arrow in order to Read the Callout content using NVDA.

**Expected result**
* The user should be able to Reach the Text from the Callous with NVDA using the Down Arrow while on the X Close button.

**Actual result**
* Hitting the Down arrow on the keyboard will keep NVDA blocked on the X Close button.

* Hitting UP arrow from the Dissmis button will allow NVDA to reach the Text from the Callout without issues.

**Regression range**
Not a Regression

Please also note that this issue occurs on CALLOUT 1, CALLOUT 2 as well as CALLOUT 3.