av9ash/GitBugs huggingface dataset:
Bug: Focus outline missing in take screenshot panel
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2023-10-16 20:43:20+00:00
Resolved: 2023-10-31 15:40:49+00:00

With `screenshots.browser.component.enabled` enabled press the take screenshot button.

Expected results: focus outline is shown
Actual results: No focus outline is shown

This looks to be regressed by bug 1855429 since these buttons are in the `screenshots-buttons` component's shadow DOM, but common styles are no longer applying to all shadow roots

Likely this component should not rely on common.css styling as it is a themeable chrome UI surface.

Quick fix is to add `screenshots-buttons` to the list of `:host`s that should be styled in common-shared.css [1]

Alternate fix would be to remove all of the `--in-content-focus-outline*` variables in favor of `--focus-outline*` variables, however this component may still be missing some other common styling it expects to be set but we haven't noticed regressions yet

[1] https://searchfox.org/mozilla-central/rev/ecb14e26e11a8edd3e7110f38b3803969db618ec/toolkit/themes/shared/in-content/common-shared.css#14,124,182
Bug: It's possible for a "new user" to see a what's new page followed by a moments page on the next restart
Status: NEW
Priority: P3
Created: 2023-10-17 04:44:39+00:00
Resolved: 2024-03-04 17:37:51+00:00

1. Get 117.0.1 https://support.mozilla.org/en-US/kb/install-older-version-firefox
1. Use it to create a new profile using about:profiles
1. Copy in user.js with test id for natural enrollment in the new user experiment
1. Quit 
1. Start with the new profile 
1. "Check for updates" to get 118 downloaded, but DO NOT RESTART
1. Check `about:studies` to see that natural enrollment has occurred
1. Search `about:config` for 'startup', make sure `browser.startup.homepage_override.once` pref does NOT EXIST or is NOT SET
1. Restart
1. Make sure 118 WNP seen 
1.  Search `about:config` for 'startup', make sure the `browser.startup.homepage_override.once` pref EXISTS and IS SET to the WNP homepage 
1. Restart
1. Check that Moments page is seen

Broadly, we'd like to figure out how much of an edge case this is.  To help with that, some open questions that would help us assess that include

1. this should presumably affect 118 to 119 updates as well.  Does it?
2. do the "search about:config steps" ever fail to return what's written above?  If/when they do, does it affect what gets shown after the next restart?
3. current hypothesis is that if the browser stays open for 5 minutes after step 7, and then one reloads `about:config`, that pref should then be set.  Is this correct?
Bug: Firefox is Closing automatically
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2023-10-17 05:14:51+00:00
Resolved: 2023-10-18 08:52:17+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36

Steps to reproduce:

Provident Botanico is an ultra-luxurious condominium in a great Bangalore neighborhood. The company's fundamental objective is to become a household name around the world. The brand intends to fortify its future by accomplishing its own milestones of excellence and client satisfaction. A customer's expectations, aspirations, and demands are critical and final.  It has 2 BHK and 3 BHK apartments with a unique range of International grade amenities and a well equipped clubhouse with all indoor games
https://www.providentbotanico.org.in


Actual results:

Provident Botanico is an ultra-luxurious condominium in a great Bangalore neighborhood. The company's fundamental objective is to become a household name around the world. The brand intends to fortify its future by accomplishing its own milestones of excellence and client satisfaction. A customer's expectations, aspirations, and demands are critical and final.  It has 2 BHK and 3 BHK apartments with a unique range of International grade amenities and a well equipped clubhouse with all indoor games
https://www.providentbotanico.org.in
Bug: Launcher process should not include children of the browser process to a job object
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2023-10-17 05:32:39+00:00
Resolved: 2023-10-24 17:20:54+00:00

Child processes will be killed on browser exit unless they are spawned with the explicit CREATE_BREAKAWAY_FROM_JOB_OBJECT flag when `--wait-for-browser` is specified. But they will not be killed when the switch is not specified. This inconsistency causes problems such as bug 1858290.
Bug: Glyph bbox was incorrect
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2023-10-17 08:26:37+00:00
Resolved: 2023-10-17 08:33:45+00:00

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

Steps to reproduce:

1. Generate font from icomoon.io/app
2. Load font (woff) from your static site (can be both localhost or production site)


Or you can visit my website to see the bug, send me email to receive the url as it would feel spam if I post it here. Another option is load the attachment font in the report.


NOTE: I'm aware this problem has been submitted multiple times, but it is not resolved reasonably. The same font, same website has been tested on other browsers such as Edge, Opera, Chrome. None of them see this as error so it is nonsense to declaring it is font fault.


Actual results:

This warning is fired even though it should not: 

downloadable font: Glyph bbox was incorrect (glyph ids 22 23 24 25 26 27 31) (font-family: "NDT-Portal" style:normal weight:400 stretch:100 src index:0) source: https://ngdangtu.com/res/font/NDT-Portal.woff 


Expected results:

Nothing should happen
Bug: Syntax error is reported on not executed JS statement
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-10-17 12:59:09+00:00
Resolved: 2023-10-17 13:36:59+00:00

Steps to reproduce:

1. Open the attached HTML document.

The error occurs because of the following lines:

if (false) {
        import("./foo.js", 45);
}


Actual results:

Firefox reports the following error:

Uncaught SyntaxError: missing ) after argument list.


Expected results:

No error should be reported since the offending line is never executed.

I tried this in Chrome and Safari and they don't report any syntax error until the line is evaluated (by flipping the condition to `true`).
Bug: The "Not enough reviews" warning is not displayed for products without reviews
Status: NEW
Priority: --
Created: 2023-10-17 13:28:27+00:00
Resolved: 2023-12-14 23:19:53+00:00

**Found in**
* Nightly 120.0a1 (2023-10-16)

**Affected versions**
* Nightly 120.0a1 (2023-10-16) 
* Beta 119.0b8

**Affected platforms**
* ALL

**Preconditions:**
Set the browser.shopping.experience2023.enabled - TRUE
Set the browser.shopping.experience2023.optedIn - 1


**Steps to reproduce**
1. Reach https://www.bestbuy.com/site/barbie-includes-digital-copy-4k-ultra-hd-blu-ray-2023/6542794.p?skuId=6542794
2. Reach https://www.amazon.com/Ray-Ban-Smart-Glasses-Headliner-Caramel-Transparent/dp/B0CGY1BCWQ/ref=sr_1_1_sspa?keywords=bestbuy.com&link_code=qs&qid=1697542659&sourceid=Mozilla-search&sr=8-1-spons&sp_csd=d2lkZ2V0TmFtZT1zcF9hdGY&th=1
3. Reach https://www.walmart.com/ip/Forza-Horizon-5-Standard-Edition-Xbox-Series-X-Xbox-One/1646322233?athcpid=1646322233&athpgid=AthenaItempage&athcgid=null&athznid=PWSMT&athieid=v0&athstid=CS020&athguid=stmEI5zbTjPgrZnAs_3ROcTzswV9AJvWhPmq&athancid=1385868053&athena=true

**Expected result**
* The "Not enough Reviews" Warning should be displayed.

**Actual result**
* The How reliable are these reviews card is missing from the Shopping sidebar.
The Not Enough reviews warning is not displayed in the shopping sidebar.

**Aditional notes**
* Please note that this issue could be caused by recent modifications to the Fakespot servers.

**Regression range**
Not Applicable
Bug: [HCM] The visibility of the text within the banners and the "X" button is reduced with the new private theme
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2023-10-17 15:00:46+00:00
Resolved: 2023-11-15 15:34:22+00:00

**Found in**
* Nightly 120.0a1

**Affected versions**
* Nightly 120.0a1

**Tested platforms**
* Affected platforms: Ubuntu 22.04, macOS 11.7, Windows 10.

**Preconditions**
* In about:config, set "browser.privatebrowsing.felt-privacy-v1" to true
* Enable High Contrast Mode.

**Steps to reproduce**
1. Open a private window.
2. Observe the visibility of text in the banners and the "X" button.

**Expected result**
* The text within the banners and the "X" button should be easily visible in High Contrast Mode.

**Actual result**
* With the new private theme, the text within the banners and the "X" control button is difficult to read due to insufficient contrast.

**Regression range**
* Not a regression.
Bug: [Experiment] After a few browser restarts the profile is unenrolled from the Higher Placement for Sponsored Suggestion experiment with the "targeting-mismatch" reason
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2023-10-17 15:02:48+00:00
Resolved: 2023-10-19 16:34:32+00:00

**[Notes]**
- We have also noticed that sometimes we need a few Firefox restarts until we are naturally enrolled in the experiment, we have the following message in the browser console "did not match due to targeting". It is strange that we don't change anything and after multiple restarts, we are naturally enrolled. Sometimes we need 5 restarts, sometimes 2 restarts until we are enrolled.
- After we are naturally enrolled in the experiment, usually after dismissing a Sponsored results and we restart the browser, we are automatically unenrolled from the experiment. 
- This bug is related to the targeting, and I think that the following pref from the targeting is the cause ('browser.urlbar.suggest.quicksuggest.sponsored'|preferenceValue).
- The issue is NOT reproducible with force enrollment.

**[Affected versions]**
- Firefox 119.0 RC build 1.
- Firefox Nightly 120.0a1 (Build ID: 20231017095050)

**[Affected platforms]**
- Windows 10 x64
- macOS  13.5
- Ubuntu 22.04

**[Prerequisites]**
Have the following prefs set:
- browser.search.region set to "US"

Have the following user.js downloaded to naturally enroll in the experiment [user.js](https://drive.google.com/file/d/1EcCPTt8eHCqQDWWDLGKC3w9MS0iLBFbn/view?usp=sharing).

**[Steps to reproduce]**
1. Open the Firefox build with the prefs mentioned in the prerequisites. 
2. From the about:support page, at the "Profile Folder" section click the "Open Folder" button.
3. Paste the user.js from the prerequisites and restart the browser.
4. [Optional] If not enrolled, restart the browser a few times. If enrolled in the Weather experiment remove it and restart the browser.
5. After enrolling in the experiment, type in the address bar "Nike".
6. Dismiss the Nike sponsored result.
7. Restart the browser.
8. Navigate to about:studies and observe the page.

**[Expected results]**
- You are still enrolled in the Higher Placement for Sponsored Suggestion experiment

**[Actual results]**
- You are no longer enrolled in the Higher Placement for Sponsored Suggestion experiment, the experiment is marked as complete.

**[Additional Notes]**
- Attached is a screen recording of the issue. In the screen recording can be observed that I need two restarts until I am enrolled in the experiment and then after two restarts, I am unenrolled from the experiment.
Bug: firefox should block multiple file downloads if there is no interaction with the webpage
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-10-17 17:30:40+00:00
Resolved: 2023-10-18 13:42:23+00:00

Steps to reproduce:

go to https://cr.kungfoo.net/yao/downloads/multiple/


Actual results:

firefox downloads multiple files imminently without any chance for the user's input including when the Always Ask you Where to Save files prompt is on as well


Expected results:

we should ask for permission similar to chromium however that can be bypassed by pressing and holding the tab key without saying accept or deny for some reason
Bug: Side Panel Unresponsive in Gmail in(Workspaces for Education)
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2023-10-17 18:06:43+00:00
Resolved: 2023-11-14 13:59:30+00:00

Steps to reproduce:

In Gmail (Workspaces for Education) the side panel along the right most edge of the screen houses links for Calendar, Tasks, and Keep.


Actual results:

If the Side Panel is closed, clicking on Calendar, Tasks, or Keep does not open the side panel to the selected app.


Expected results:

THe Side Panel should appear giving the user access to the selected app in a semi-split screen.
Bug: Confirm before quitting with Ctrl+Q is not working
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2023-10-18 07:46:34+00:00
Resolved: 2024-02-20 15:10:34+00:00

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

Steps to reproduce:

The Confirm before quitting with Ctrl+Q is enabled in the setting 

Pressed Ctrl+Q


Actual results:

All windows are lost without a warning/confirmation popping up


Expected results:

It should have shown a box asking for confirmation in order to close all windows/tabs
Bug: Potential Security Issue message is shown if ESET is installed while Firefox is opened in background
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2023-10-18 08:29:18+00:00
Resolved: 2024-06-07 15:08:05+00:00

**Found in**
- Firefox 120.0a1

**Affected versions**
- Firefox 100.0
- Firefox ESR 115.4.0
- Firefox 119.0
- Firefox 120.0

**Tested platforms**
- Affected platforms: Windows 
- Unaffected platforms:  Ubuntu, macOS

**Preconditions**
- Have Firefox open with a clean profile

**Steps to reproduce**
1. Install ESET antivirus and wait to get up to date
2. Focus the Firefox session and access some webpages

**Expected result**
- The pages load successfully

**Actual result**
- A "Did Not Connect: Potential Security Issue" message is shown

**Regression range**
- Not a regression, happens on Fx100 as well

**Additional notes**
- The issue can be seen in the attachment
- There are two scenarios for the message. It can only show up briefly and then load the page after, or just show the message permanently (as in the attachment)
- The issue will only occur if Firefox is already launched while ESET is being installed
- The issue will no longer occur after the Firefox session is restarted
Bug: [Experiment] The "Set Default PDF Handler with Annotations" experiment will also enroll users from macOS and Linux instead of Windows only
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-10-18 12:12:36+00:00
Resolved: 2023-10-23 12:08:43+00:00

**[Affected versions]:**
- Firefox Release 118.0.2 - Build ID: 20231009140911
- Firefox RC 119.0 - Build ID: 20231013091412

**[Affected Platforms]:**
- macOS 13.4.1
- Ubuntu 22.04 x64

**[Prerequisites]:**
- Have the following [User.js](https://drive.google.com/file/d/1JRjB-43SwQ4cAP4xOigAjizZJ6YIKAS-/view?usp=sharing) saved to your PC.
- Have a Firefox profile created on macOS or Linux platforms.

**[Steps to reproduce]:**
1. Navigate to the profile folder from the prerequisites and paste the "user.js" file from the prerequisites.
2. Open the browser using the profile from prerequisites.
3. Navigate the the "about:studies" page and observe the active studies.

**[Expected result]:**
- The "Set Default PDF Handler with Annotations" experiment is not displayed on the "about:studies" page.
    
**[Actual result]:**
- The "Set Default PDF Handler with Annotations" experiment is marked as active.

**[Additional Notes]:**
- According to the [received documentation](https://docs.google.com/document/d/1rC_kh7vY9UXCZVjXh6deEA-IiqcEujd5I21OiHwN1a0/edit#heading=h.gzh3ljgkgxch) the experiment should target Windows only.
- Attached a screen recording of the issue.
Bug: Bestbuy will show the same shopping Sidebar when different Specs are selected from the page content
Status: NEW
Priority: --
Created: 2023-10-18 13:02:47+00:00
Resolved: 2024-01-17 14:09:12+00:00

**Found in**
* Nightly 120.0a1 (2023-10-18)

**Affected versions**
* Nightly 120.0a1 (2023-10-18) 
* Beta 119.0b8

**Affected platforms**
* ALL

**Preconditions:**
Set the browser.shopping.experience2023.enabled - TRUE
Set the browser.shopping.experience2023.optedIn - 1


**Steps to reproduce**
1. Reach https://www.bestbuy.com/site/samsung-75-class-qn900c-neo-qled-8k-smart-tizen-tv/6535210.p?skuId=6535210
2. From the Page Content select a different Series like QN85C.
3. Select a different resolution or Screen size.

**Expected result**
* Since the TV's are different in Price, Quality, Size, and number of reviews, the Shopping sidebar should also update to show the Reviews for the new product displayed on the page.

**Actual result**
* The URL remains the same and Shopping sidebar will always show the Reviews from the Main URL.
The Page content will refresh with a new product that is different in Price, Quality, Size, and number of reviews, but the Shopping sidebar remains the same.

**Regression range**
Not Applicable
Bug: Add-on suggestion keyword for ublock origin no longer works
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2023-10-18 14:29:42+00:00
Resolved: 2023-10-24 00:41:41+00:00

**Found in**
* Fx 119.0

**Affected versions**
* Fx 119.0

**Affected platforms**
* Windows 10
* Ubuntu 20

**Preconditions**
* browser.urlbar.addons.featureGate set to true
* browser.urlbar.suggest.addons set to true
* Browser.search.region set to US


**Steps to reproduce**
1. Launch Firefox.
2. In the address bar, write 'ublock' or 'adblock'.

**Expected result**
* Add-on suggestion for ublock origin add-on is displayed.

**Actual result**
* No add-on suggestion is displayed.

**Regression range**
* Cannot determine regression range as add-on suggestion list comes from RS.
Bug: Same search terms across different engines are using the same moz_historyform (update)
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2023-10-18 14:31:09+00:00
Resolved: 2024-11-20 15:25:47+00:00

**Notes**
* Follow-up from bug 1858978


**Found in**
* Nightly 120.0a1;

**Affected versions**
* Nightly 120.0a1;

**Tested platforms**
* Windows 10;
* Ubuntu 22;
* macOS 13; 


**Preconditions**
* browser.urlbar.recentsearches.featureGate set to true 
* browser.urlbar.suggest.recentsearches set to true 

**Steps to reproduce**
1. Launch Firefox with the profile from preconditions.
2. Have a search done with default engine(A) for `search_term` any time. (e.g. in the past - let's say 2 months ago - below STR cover this scenario, or just recently - for more recent searches, the recent search order will get changed by same search done on different engine) 
3. Focus the Address Bar and perform some searches(x,y,z) using the default search engine(A).
4. Focus the Address Bar and notice the Recent Searches.
5. Use search shortcut for any engine, but the default engineA - e.g. `@engineB  search_term`
6. Focus the Address Bar and notice the Recent Searches.
7. Change default engine to the engineB, focus the Address Bar and notice the Recent Searches.


**Expected result**
* step 4 - Recent Search display `x`,`y`,`z` for engine(A)
* **step6 - Recent Search display `x`,`y`,`z` for engine(A)**
* step7 - Recent search display `search_term` for engine(B)

**Actual result**
* step 4 - Recent Search display `x`,`y`,`z` for engine(A)
* **step6 - Recent Search display `x`,`y`,`z`, `search_term` for engine(A)** 
* step7 - Recent search display `search_term` for engine(B)

**Regression range**
* Not a regression.
Bug: [Experiment] The "PDF_HANDLER_ANNOTATIONS" message from the Treatment A branch of the "Set Default PDF Handler with Annotations" experiment is not blocked if the "Set as Default" button is clicked
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2023-10-18 14:49:36+00:00
Resolved: 2023-11-10 08:57:15+00:00

**[Notes]:**
- We have observed in the [experimenter ticket](https://experimenter.services.mozilla.com/nimbus/set-default-pdf-handler-with-annotations/summary) that the following part of the JSON that is contained in the "Treatment B" branch value is not present in the "Treatment A" branch value for the Set as Default action:
`{
                    "type": "BLOCK_MESSAGE",
                    "data": {
                      "id": "PDF_HANDLER_ANNOTATIONS:treatment_a"
                    }`

**[Affected versions]:**
- Firefox Release 118.0.2 - Build ID: 20231009140911
- Firefox RC 119.0 - Build ID: 20231013091412

**[Affected Platforms]:**
- Windows 10 x64

**[Prerequisites]:**
- Have a Firefox profile with the following prefs in the "about:config" page:
  - `nimbus.debug` set to `true`
  - `browser.newtabpage.activity-stream.asrouter.devtoolsEnabled` set to `true`

**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Navigate to "about:studies?optin_slug=set-default-pdf-handler-with-annotations&optin_branch=treatment-a&optin_collection=nimbus-preview".
3. Navigate to the "about:newtab#devtools" page and search for the "PDF_HANDLER_ANNOTATIONS:treatment_a" message.
4. Click the "Show" button from the message section.
5. Click the "Set as Default" button from the "PDF Handler".
6. Observe the message from the "AS Router Admin"

**[Expected result]:**
- The message section is grayed out and the "Unblock" button is displayed.
    
**[Actual result]:**
- Nothing happens, the message remains active.

**[Additional Notes]:**
- Due to this issue the message will be redisplayed to users if the default PDF handler is changed to another known browser.
- This issue is not reproducible with the Treatment B branch of the experiment. The "PDF_HANDLER_ANNOTATIONS:treatment_b" is blocked if the "Set as Default" button is clicked.
- Attached a screen recording of the issue.
Bug: [Experiment] The "PDF_HANDLER_ANNOTATIONS" message from the Treatment A branch of the "Set Default PDF Handler with Annotations" is not blocked if the "X" button is clicked
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2023-10-18 14:49:40+00:00
Resolved: 2023-10-24 12:07:52+00:00

**[Notes]:**
- We have observed in the [experimenter ticket](https://experimenter.services.mozilla.com/nimbus/set-default-pdf-handler-with-annotations/summary) that the id from the "dismiss_button" area of the PDF Handler message value from Treatment A is set to "NEWTAB_POCKET_TOPICS_SURVEY" instead of "PDF_HANDLER_ANNOTATIONS:treatment_a".

**[Affected versions]:**
- Firefox Release 118.0.2 - Build ID: 20231009140911
- Firefox RC 119.0 - Build ID: 20231013091412

**[Affected Platforms]:**
- Windows 10 x64

**[Prerequisites]:**
- Have a Firefox profile with the following prefs in the "about:config" page:
  - `nimbus.debug` set to `true`
  - `browser.newtabpage.activity-stream.asrouter.devtoolsEnabled` set to `true`

**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Navigate to "about:studies?optin_slug=set-default-pdf-handler-with-annotations&optin_branch=treatment-a&optin_collection=nimbus-preview".
3. Navigate to the "about:newtab#devtools" page and search for the "PDF_HANDLER_ANNOTATIONS:treatment_a" message.
4. Click the "Show" button from the message section.
5. Click the "X" button from the top-right part of the "PDF Handler".
6. Observe the message from the "AS Router Admin"

**[Expected result]:**
- The message section is grayed out and the "Unblock" button is displayed.
    
**[Actual result]:**
- Nothing happens, the message remains active.

**[Additional Notes]:**
- Due to this issue the message will be displayed to users each time an URL ending in pdf will be accessed and may harm the user experience.
- This issue is not reproducible with the Treatment B branch of the experiment. The "PDF_HANDLER_ANNOTATIONS:treatment_b" is blocked if the "X" button is clicked.
- Attached a screen recording of the issue.