av9ash/GitBugs huggingface dataset:
Bug: Allow focus to move into and out of feature callouts
Status: NEW
Priority: P1
Created: 2024-05-30 12:19:25+00:00
Resolved: 2025-03-03 18:05:21+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. Open a new tab.
3. Close the message using the “ESC” key.

**[Expected result]:**
- The message is closed using the “ESC” key when there is more than one opened tab


**[Actual result]:**
- The message cannot be closed using the “ESC” key when there is more than one opened tab





**[Notes]:**
- A video of this issue is attached.
- We noticed that this bug is related to the fact that the “Discovery Search” message cannot be focused when there is more than one opened tab.
- This issue is occurring for early day users and existing users, too, and for all the branches.
Bug: Add option to extend feature callout page_event_listener to all windows
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2024-05-30 12:41:39+00:00
Resolved: 2024-12-31 12:03:04+00:00

**[Affected versions]:**
- Firefox Nightly 128.0a1 - Build ID: 20240529214854
- Firefox Beta 127.0b8 - Build ID: 20240529091551
- Firefox Release 126.0.1 - Build ID: 20240526221752

**[Affected Platforms]:**
- Windows 10
- macOS 14
- Ubuntu 22.04

**[Prerequisites]:**
- Have a Firefox build installed and use a new profile.
- Be enrolled in any branch (except control) of the Pin Email and Calendar experiment ([early day](https://experimenter.services.mozilla.com/nimbus/pin-email-and-calendar-tabs-early-day-user/summary) / [existing](https://experimenter.services.mozilla.com/nimbus/pin-email-and-calendar-tabs-existing-user/summary)) through forced enrollment.
- Have the `browser.newtabpage.activity-stream.asrouter.devtoolsEnabled` pref set to `true`.
- Unenroll from any experiment or rollout that the profile might be in using the about:studies page.

**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites and open a New Window.
2. Switch to the previous windows and navigate to the about:asrouter page.
3. Search for the `PIN_EMAIL_AND_CALENDAR_TABS` message ID.
4. Click the `Show` button.
5. Switch to the other window and right click the active tab.
6. Choose the `Pin Tab` option and observe the message from the other window.

**[Expected result]:**
- The message is dismissed.
 
**[Actual result]:**
- The message remains displayed.

**[Notes]:**
- The issue is not reproducible when pinning a tab from the same window the message is anchored in, regardless of the tab state (active/inactive).
- Attached a screen recording of the issue.
Bug: [Experiment] The Pin message is anchored in the active tab when loading the target sites in new background tabs
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2024-05-30 13:16:58+00:00
Resolved: 2024-10-22 19:15:44+00:00

**[Affected versions]:**
- Firefox Nightly 128.0a1 - Build ID: 20240529214854
- Firefox Beta 127.0b8 - Build ID: 20240529091551
- Firefox Release 126.0.1 - Build ID: 20240526221752

**[Affected Platforms]:**
- Windows 10
- macOS 14
- Ubuntu 22.04

**[Prerequisites]:**
- Have a Firefox build installed and use a new profile.
- Be enrolled in any branch (except control) of the Pin Email and Calendar experiment ([early day](https://experimenter.services.mozilla.com/nimbus/pin-email-and-calendar-tabs-early-day-user/summary) / [existing](https://experimenter.services.mozilla.com/nimbus/pin-email-and-calendar-tabs-existing-user/summary)) through forced enrollment.
- Unenroll from any experiment or rollout that the profile might be in using the about:studies page.

**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites and open a new tab.
2. Right click the `reddit` Top Site and choose the `Open Link in a New Tab`.
3. Repeat step 2.
4. Repeat step 2 and observe the current tab.

**[Expected result]:**
- No message is displayed.
 
**[Actual result]:**
- The "Pin" message is displayed.

**[Notes]:**
- Attached a screen recording of the issue.
Bug: Overwriting a PDF file on a Windows share from Firefox's PDF Editor makes the file disappear
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2024-05-30 13:26:42+00:00
Resolved: 2024-07-18 12:11:29+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 was happy to learn that one can use FF as a PDF Editor. 
I tried it on two computers (windows 10 and window 11). When i edit a PDF and then save it in the original Name and Path (overwrite yes).



Actual results:

Afte doing so, the file disappers in the windows explorer. The user (even as administrator) loses the right, to see and open the file.



Expected results:

The file should keep the original access rights.
Bug: [Experiment] The pin message is displayed when navigating back and forth to a target URL or by refreshing a such a page
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2024-05-30 13:32:13+00:00
Resolved: 2024-06-10 17:36:41+00:00

**[Notes]:**
- If the message is required to be a contextual response to actions made by the user, simply navigating to and from a page or refreshing it should not lead to the assumption that users would need to pin that tab. Opening a new tab and specifically navigating to a page is a much clearer marker that users might benefit from having that tab pinned.

**[Affected versions]:**
- Firefox Nightly 128.0a1 - Build ID: 20240529214854
- Firefox Beta 127.0b8 - Build ID: 20240529091551
- Firefox Release 126.0.1 - Build ID: 20240526221752

**[Affected Platforms]:**
- Windows 10
- macOS 14
- Ubuntu 22.04

**[Prerequisites]:**
- Have a Firefox build installed and use a new profile.
- Be enrolled in any branch (except control) of the Pin Email and Calendar experiment ([early day](https://experimenter.services.mozilla.com/nimbus/pin-email-and-calendar-tabs-early-day-user/summary) / [existing](https://experimenter.services.mozilla.com/nimbus/pin-email-and-calendar-tabs-existing-user/summary)) through forced enrollment.
- Unenroll from any experiment or rollout that the profile might be in using the about:studies page.

**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites and navigate to `https://www.reddit.com/`.
2. Click the `Go back one page` button then the `Go forward on page` button.
3. Repeat step 2 two more times.
4. Observe the active tab.

**[Expected result]:**
- No message is displayed.
 
**[Actual result]:**
- The "Pin" message is displayed.

**[Additional Notes]:**
- The issue is also reproducible if the page is refreshed twice instead of going back and forth.
- Attached a screen recording of the issue.
Bug: DLP scan not happening when uploading a folder that contains another folder
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2024-05-30 13:37:21+00:00
Resolved: 2024-06-06 13:28:44+00:00

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

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


**Tested platforms**
* Affected platforms: Windows 10x64, Windows 11x64
* Unaffected platforms: macOS, UbuntuUbuntu 22, 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


**Steps to reproduce**
1. Create `folder1` and create `folder2` inside.
2. Upload `folder1` to https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement/webkitdirectory.

**Expected result** 
* DLP Agent is scanning the uploaded folders and then uploads the files if permitted.

**Actual result**
*  `An error occurred in communicating with QA Test DLP Agent. Upload of folder 2 denied.` notification is displayed. 



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

**Additional notes**
* Attached a screen recording.
* This happens even if the folder has files inside or they are empty.
Bug: [Rollout] The Review Checker button from the Address bar remains displayed if unenerolling from the rollout while the product page is focused
Status: ASSIGNED
Priority: --
Created: 2024-05-30 13:56:26+00:00
Resolved: 2024-06-03 20:47:20+00:00

**[Affected versions]:**
- Firefox Nightly 128.0a1 - Build ID: 20240529214854
- Firefox Beta 127.0b8 - Build ID: 20240529091551
- Firefox Release 126.0.1 - Build ID: 20240526221752

**[Affected Platforms]:**
- Windows 10
- macOS 13.4
- Ubuntu 22.04

**[Prerequisites]:**
- Have following prefs set:
  - browser.search.region = US
  - nimbus.debug = true
- Have the **[user.js](https://drive.google.com/file/d/1iluih4Uh7Dr6T5aw6PfOuAEwRzbCaShE/view?usp=sharing)** file downloaded.  

**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Navigate to about:support page, open the "Profile Folder" folder and paste the user.js file from prerequisites.
3. Restart the browser to enroll in the rollout.
4. Navigate to an Amazon product.
5. Opt-in in the Review Checker.
6. Open a new tab and change the "browser.search.region" to any other region code beside US.
7. Focus the product page opened in Step 4.
8. Open the browser console and restart the browser using the key shortcut (CTRL+ALT+R/Option+CMD+R).
9. Observe the Address bar.

**[Expected result]:**
- The Review Checker button is displayed in the address bar for any websites.

**[Actual result]:**
- The Review Checker button is no longer displayed.

**[ Notes]:**
- The issue is reproducible also if the Fakespot add-on is installed, and the browser is restarted while the product page is opened.
- Attached is a screen recording of the issue.
Bug: Two blue rotating arrows icon is missing after pressing "Sync now"
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2024-05-30 14:53:25+00:00
Resolved: 2024-05-30 15:13:55+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 noticed, that after updating to Firefox 126.0.1 the two blue rotating arrows icon is missing from the Account menu when syncing.

I'm using Windows 10 Pro 19045.4472 and Firefox 126.0.1 (64-bit).
The theme I'm using is "Activist – Soft".


Actual results:

Two blue rotating arrows icon is missing.


Expected results:

Two blue rotating arrows icon should appear after pressing "Sync now".
Bug: Keydown not working on screenshots overlay buttons
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2024-05-30 15:21:48+00:00
Resolved: 2024-06-14 15:28:44+00:00

STR:
1. Open screenshots
2. Use the keyboard to focus the crosshairs cancel button
3. "Enter" or " "(space) on the cancel button

AR:
Nothing happens

ER:
The overlay should close

This also happens on the `x`, `copy` and `download` buttons on the overlay
Bug: Editing a PDF results in unexpected content change
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2024-05-30 15:23:20+00:00
Resolved: 2024-06-19 21:14:17+00:00

User Agent: Mozilla/5.0 (Android 14; Mobile; rv:128.0) Gecko/128.0 Firefox/128.0

Steps to reproduce:

Open this pdf:

https://www.vodafone.de/media/downloads/pdf/2060-sepa-basis-lastschrift-mandat-festnetz.pdf

Make a edit in a field of the pdf 
Leave the field
The barcode on the left turns into rubbish


Actual results:

The barcode on the left turns into rubbish


Expected results:

Only the edited field should have changed
Bug: The page becomes unresponsive until the messages are closed if the DLP scan/warning is triggered across multiple tabs
Status: NEW
Priority: --
Created: 2024-05-30 15:57:12+00:00
Resolved: 2024-06-18 19:41:26+00:00

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

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


**Tested platforms**
* Affected platforms: Windows 10x64, Windows 11x64
* Unaffected platforms: macOS, UbuntuUbuntu 22, 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


**Steps to reproduce**
1. Open https://en.wikipedia.org/wiki/UNESCO in two tabs.
2. Paste “warning text” in both tabs.
3. Focus on the first tab and choose Cancel or Use content.
4. Navigate on the webpage.

**Expected result** 
* Navigation is possible.

**Actual result**
* Page is unresponsive until the second tab finishes scanning or the warning dialog is closed.



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

**Additional notes**
* Attached a screen recording.
* This issue only happens if pasting the second content while the firs scan was not finished inside the DLP agent.
* Pasting a second time on an unresponsive page will make the page blank with a loading circle in the center until all DLP messages are closed.
* THis happens while the scanning and warning messages are displayed. This does not happen while a blocking message is displayed.
Bug: [Nightly] Latest Nightly Breaks Sideberry Tab Extension
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2024-05-30 17:02:42+00:00
Resolved: 2024-06-18 17:09:47+00:00

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

Steps to reproduce:

Install Sideberry
Update to the latest Nightly
Open some tabs


Actual results:

The "X" to close the tabs has gotten pushed way too far to the right to be able to click on it. Even expanding the "Tabs" to as far right as it can go, the "X" is only barely visible. 


Expected results:

The "X" to close the tab should be close to the end of the tab's name. I have included screenshots of Nightly firefox to compare.
Bug: Handle previews for multi-feature experiments in the dashboard
Status: NEW
Priority: P2
Created: 2024-05-30 17:12:05+00:00
Resolved: 2024-06-14 15:15:45+00:00

Right now, we default to previewing the first messaging feature in an experiment. This works fine when there's only one feature, but in cases where there's more than one we need better handling.

Right now there's the [About Welcome post first run](https://experimenter.services.mozilla.com/nimbus/about-welcome-post-first-run-onboarding/summary) experiment as an example; the experiment deals with about:welcome but there is no preview-able about:welcome message (the experiment is for a toolbar button, not a message.) There *is* a Feature Callout as a second messaging feature, and it would be nice to be able to preview the feature callout for the branch where it exists.

Step 1 would be to turn off the preview link if the messaging feature is empty (i.e. no screens prop in the case of about:welcome), which should be covered by an existing PR for feature callout previews.

Step 2 would be searching/iterating through features to look for a message that can be previewed; if there's only one like in this case that should be straightforward. I'm not sure yet how we'll want to handle experiments with multiple possible messages; we'll probably want to investigate and handle that in a separate bug. One possibility would be a dropdown menu allowing users to choose a message to preview; UX input would be required!
Bug: Perma mozilla-beta browser/components/aboutlogins/tests/browser/browser_alertDismissedAfterChangingPassword.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: WORKSFORME
Created: 2024-05-30 18:08:31+00:00
Resolved: 2024-06-03 06:30:04+00:00

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

---
```
TEST-PASS | browser/components/aboutlogins/tests/browser/browser_alertDismissedAfterChangingPassword.js | the breach alert should be visible - true == true - 
[task 2024-05-30T15:59:21.499Z] 15:59:21     INFO - Buffered messages finished
[task 2024-05-30T15:59:21.500Z] 15:59:21     INFO - TEST-UNEXPECTED-FAIL | browser/components/aboutlogins/tests/browser/browser_alertDismissedAfterChangingPassword.js | Test timed out - 
[task 2024-05-30T15:59:21.500Z] 15:59:21     INFO - GECKO(4436) | Completed ShutdownLeaks collections in process 3448
[task 2024-05-30T15:59:21.500Z] 15:59:21     INFO - TEST-START | Shutdown
```
Bug: Since update 126.0.1, every attempt to "Save Image As" crashes Firefox
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2024-05-30 18:41:38+00:00
Resolved: 2024-06-11 08:56:06+00:00

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

Steps to reproduce:

Regardless of website - every attempt to "Save Image As" has crashed Firefox
This just begin occurring after update 126.0.1


Actual results:

Firefox froze - requiring a Force Quit in Mac OS 11.7.4 on a Macbook Pro, mid 2015 


Expected results:

Save image to file on board my MacBook Pro
Bug: poisoning sessionstore + document.title heart attack (emoji problem) = persistant dos scenario
Status: NEW
Priority: --
Created: 2024-05-31 01:19:39+00:00
Resolved: 2024-10-03 16:31:03+00:00

Hello guys.
I found 3 bugs and described them in detail in attached pdf

Best regards,
Piotr Wojciechowski
p.wojciechowski@mixedpixel.pl
Bug: Tree column picker uses button appearance since bug 1889429
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2024-05-31 04:01:00+00:00
Resolved: 2024-05-31 21:35:41+00:00

Per mozregression, after bug 1889429, tree column header pickers changed in appearance to be a button instead of a column header. I have a small patch to fix this.
Bug: [Experiment] Using the screen reader the description of the message is not read
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-05-31 08:45:05+00:00
Resolved: 2024-06-03 17:14:20+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
- Have a screen reader installed and up and running.

**[Steps to reproduce]:**
1. Open the browser from the prerequisites
2. Open a new tab.
3. Focus the mouse on the “Search Discovery” message.
4. Notice how the message is read by the screen reader.

**[Expected result]:**
-  Using the screen reader the description of the message is read; all the elements from the "Discovery Search" message are read

**[Actual result]:**
- Using the screen reader the description of the message is not read; only the title and the "X" button are read by the screen reader




**[Notes]:**
- A video of this issue is attached.
- This issue is occurring for early day users and existing users, too, and for all the branches.
Bug: The "Problem loading languages" error is not read automatically by VoiceOver
Status: NEW
Priority: P3
Created: 2024-05-31 11:13:45+00:00
Resolved: 2024-06-19 15:10:58+00:00

**Note**
* When using VoiceOver to read the Select Translations panel and the "Problem Loading languages" error is displayed, the error is not verbalized.
* The user can use CTRL+ALT+Left/Right to navigate inside the panel and read the error.

**Found in**
* Nightly v128.0a1

**Affected versions**
* Nightly v128.0a1

**Tested platforms**
* Affected platforms: MacOS
* Unaffected platforms: Windows, Ubuntu

**Steps to reproduce**
1. Ensure `browser.translations.select.enable` is set to `true` in the about:config 
    * to trigger errors the "Problem loading languages" error, activate devtools.chrome.enable = true, open the Browser Console and post "TranslationsPanelShared.simulateLangListError()". This will simulate the error ONCE.
2. Ensure a VoiceOver is running
3. Navigate to a page in a language different from the OS/browser
4. Select a text (using mouse or keyboard) and open a context menu/right click
5. Navigate to and activate `Translate Selection to English`
6. When a Translation panel opens _with the error_, observe the screen reader announcement

**Expected result**
* The text of error is announced by a screen reader. 

**Actual result**
* The text of error is added to the panel but it is not announced by the assistive technology. The focus is set to the `Try again` button by default but it is not clear why it should be tried again. Users of screen readers would not be aware of the error, unless they'll navigate backwards in [browse mode of a screen reader](https://www.accessibility-developer-guide.com/knowledge/screen-readers/desktop/browse-focus-modes/).

**Regression range**
* This is not a regression, but a remaining unfixed use case from fixing bug 1894271.

**Additional notes**
* The 2 other error panels are read automatically by VoiceOver when they are displayed.
* NVDA and ORCA really all 3 errors automatically when they are displayed.
Bug: Tab preview no longer displayed when closing another tab using the keyboard keys
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2024-05-31 11:55:49+00:00
Resolved: 2024-06-05 06:15:56+00:00

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

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

**Tested platforms**
* Affected platforms: macOS 14.4, Windows 11, Ubuntu 22.04
* Unaffected platforms: none

**Preconditions**
* Have browser.tabs.cardPreview.enabled set to true in about:config

**Steps to reproduce**
1. Open 2-3 tabs 
2. Hover over the first tab so the tab preview is displayed
3. Without moving the mouse cursor, close the active tab using cmd + W keys
3. Observe the behavior

**Expected result**
* The tab preview is still displayed for the first tab as the mouse cursor stays over the first tab

**Actual result**
* The tab preview is dismissed even though the mouse cursor stays over the first tab

**Regression range**
* Not a regression since this is reproducible on the old Nightly build from 2024-01-14 where this feature officially landed

**Additional notes**
* See the attached video
* Also reproducing when closing a new tab