av9ash/GitBugs huggingface dataset:
Bug: The webcompar reporter tool's drop-down cannot be expanded by keyboard navigation
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2023-11-22 20:38:19+00:00
Resolved: 2023-11-28 17:11:38+00:00

**Found in**
* Beta v121.0b2

**Affected versions**
* Nightly v122.0a1
* Beta v121.0b2

**Tested platforms**
* Affected platforms: Windows 10
* Unaffected platforms: ?

**Steps to reproduce**
1. Flip:
ui.new-webcompat-reporter.enabled = TRUE
ui.new-webcompat-reporter.reason-dropdown = 1 (or 2, but not 0)
2. Load any webpage.
3. Open the webcompat reporter tool
4. Use keyboard navigation to reach and access the drop-down

**Expected result**
* The drop-down is reachable and expandable by the Enter/Space key.

**Actual result**
* The drop-down is reachable, but NOT expandable by the Enter/Space key.

**Regression range**
* Not a regression but a flaw of implementation.

**Additional notes**
* A reason can be selected on the drop-down by using the Up/Down Arrow keys, but it cannot be expanded.
* Other Operating Systems have not been tested; This report will be edited when others are tested as well.
Bug: Crash in [@ AsyncShutdownTimeout | quit-application-granted | DAPTelemetrySender: sending data]
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2023-11-23 09:40:10+00:00
Resolved: 2023-12-01 00:27:46+00:00

29 crash reports from 23 installations of Firefox 122.0a1 starting with build ID 20231122215037.

[Pushlog of the first affected build](https://hg.mozilla.org/mozilla-central/pushloghtml?changeset=b9fe9a49496aa38ca77c335f20236610ef01a582).

Simon, could you try to identify what causes this shutdown crash which mentions `DAPTelemetrySender.sys.mjs`?

Crash report: https://crash-stats.mozilla.org/report/index/cf44ec2f-d0c4-4ea8-b47b-e374d0231123

MOZ_CRASH Reason: ```[Parent 14012, Main Thread] ###!!! ABORT: file resource://gre/modules/DAPTelemetrySender.sys.mjs:88```

Top 10 frames of crashing thread:
```
0  xul.dll  MOZ_Crash  mfbt/Assertions.h:281
0  xul.dll  Abort  xpcom/base/nsDebugImpl.cpp:513
0  xul.dll  NS_DebugBreak  xpcom/base/nsDebugImpl.cpp:496
1  xul.dll  nsDebugImpl::Abort  xpcom/base/nsDebugImpl.cpp:129
2  xul.dll  XPTC__InvokebyIndex  
3  xul.dll  NS_InvokeByIndex  xpcom/reflect/xptcall/md/win32/xptcinvoke_x86_64.cpp:57
3  xul.dll  CallMethodHelper::Invoke  js/xpconnect/src/XPCWrappedNative.cpp:1627
3  xul.dll  CallMethodHelper::Call  js/xpconnect/src/XPCWrappedNative.cpp:1180
3  xul.dll  XPCWrappedNative::CallMethod  js/xpconnect/src/XPCWrappedNative.cpp:1126
4  xul.dll  XPC_WN_CallMethod  js/xpconnect/src/XPCWrappedNativeJSOps.cpp:966
```
Bug: Multiple impression telemetry are registered for the Opt-In section when is displayed at the bottom of the Address Bar panel
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2023-11-23 09:56:48+00:00
Resolved: 2023-12-04 13:26:03+00:00

**[Affected versions]:**
- Firefox Beta 121.0b2 - Build ID: 20231122091904
- Firefox Nightly 122.0a1 - Build ID: 20231121183118

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

**[Prerequisites]:**
- Have a Firefox 121 or 122 en* build installed.
- Have the following prefs in the "about:config" page:
  - browser.search.region set to US;
  - browser.urlbar.quicksuggest.contextualOptIn set to true
  - browser.urlbar.quicksuggest.contextualOptIn.topPosition set to false
- Have [Glean telemetry](https://testrail.stage.mozaws.net/index.php?/cases/view/2323256) configured.  

**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Click on the Address Bar.
3. Click any of the displayed results while the Opt-In section is displayed.
4. Navigate to "about:glean" and click on the "Apply settings and submit ping".
4. Navigate to the Glean debug page: https://debug-ping-preview.firebaseapp.com/.
5. Select your tag and verify the last event registered.

**[Expected result]:**
- Only one impression for "quick_suggest_contextual_opt_in" is registered.

**[Actual result]:**
- Three impression telemetry are registered for "quick_suggest_contextual_opt_in".

**[Notes]:**
- The issue is NOT reproducible for the Opt-In section displayed at the top, only one impression is registered.
- This issue can affect the data collected for the experiment when it will be launched. Considering this I will mark this issue as an S2. 
- Attached is a screen recording of the issue.
Bug: Perma [Tier-2] TEST-UNEXPECTED-PASS | browser/components/firefoxview/tests/browser/firefoxview-next/browser_syncedtabs_errors_firefoxview_next.js | We expect at least one assertion to fail because this test file is marked as fail-if in the manifest
Status: RESOLVED
Priority: P5
Resolution: DUPLICATE
Created: 2023-11-23 10:03:06+00:00
Resolved: 2023-11-24 06:02:37+00:00

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

---
```
[task 2023-11-23T09:09:05.814Z] 09:09:05     INFO - TEST-PASS | browser/components/firefoxview/tests/browser/firefoxview-next/browser_syncedtabs_errors_firefoxview_next.js | Correct message should show when there's a sync service error - 
[task 2023-11-23T09:09:05.814Z] 09:09:05     INFO - Leaving test bound test_sync_error
[task 2023-11-23T09:09:05.815Z] 09:09:05     INFO - Buffered messages finished
[task 2023-11-23T09:09:05.816Z] 09:09:05     INFO - TEST-UNEXPECTED-PASS | browser/components/firefoxview/tests/browser/firefoxview-next/browser_syncedtabs_errors_firefoxview_next.js | We expect at least one assertion to fail because this test file is marked as fail-if in the manifest. - 
[task 2023-11-23T09:09:05.816Z] 09:09:05     INFO - TEST-INFO | expected FAIL
[task 2023-11-23T09:09:05.816Z] 09:09:05     INFO - GECKO(19582) | MEMORY STAT | vsize 20143MB | residentFast 588MB | heapAllocated 395MB
[task 2023-11-23T09:09:05.817Z] 09:09:05     INFO - TEST-OK | browser/components/firefoxview/tests/browser/firefoxview-next/browser_syncedtabs_errors_firefoxview_next.js | took 1265ms
```
Bug: JAWS/ORCA does not read the webcompat reporter's description
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-11-23 12:32:18+00:00
Resolved: 2024-01-05 12:51:14+00:00

**Found in**
* Beta v121.0b2

**Affected versions**
* Nightly v121.0a1
* Beta v121.0b2

**Tested platforms**
* Affected platforms: Windows 10/11 + JAWS/NVDA; Ubuntu 22 + ORCA.
* Unaffected platforms: MacOS + VoiceOver (the messages can be read using CTRL+ALT+UP/DOWN)

**Steps to reproduce**
1. Launch JAWS, then Firefox
2. Make sure new webcopmpat feature is enabled:
ui.new-webcompat-reporter.enabled  = true
3. Load any webpage
4. Go to Hamburger Menu / Report broken site
4. Observe how JAWS reads the new webcompat reporter dialog.

**Expected result**
* The description is being read.

**Actual result**
* The description is not being read.

**Regression range**
* not a regression, but an implementation flaw.

**Additional information**
* The description is being read by NVDA.
Bug: [Experiment] The title from the "Pin to taskbar" screen is set to "Check your device" instead of "Check for a notification" as specified in Figma
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-11-23 12:45:20+00:00
Resolved: 2023-11-24 14:57:15+00:00

**[Affected versions]:**
- Firefox Release 120.00 - Build ID: 20231116134553

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

**[Prerequisites]:**
- Have a Firefox profile with the "nimbus.debug" pref set to true in the "about:config" page.

**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Navigate to "about:studies?optin_slug=windows-11-pinning-api-experiment&optin_branch=treatment-a&optin_collection=nimbus-preview".
3. Navigate to the "about:welcome" page.
4. Click the "Save and continue" button while the "Pin Firefox to taskbar" option is checked.
5. Observe the title from the "Pin to taskbar" screen.

**[Expected result]:**
- The screen title is: "Check for a notification".
    
**[Actual result]:**
- The screen title is set to "Check your device" one instead.

**[Additional Notes]:**
- Based on the [Figma documentation](https://www.figma.com/file/c83OEio9DhCQKuabx2tIEl/NUO-Experiments-H1%2FH2-2023?type=design&node-id=5165-6362&mode=design&t=K8EaFAVGeoDRD33C-0) the screen title should be set to "Check for a notification".
- Attached a screenshot of the issue.
Bug: NVDA/JAWS/ORCA do not read the webcompat reporter's confirmation message
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-11-23 13:02:29+00:00
Resolved: 2024-02-17 13:59:11+00:00

**Found in**
* Beta v121.0b2

**Affected versions**
* Nightly v122.0a1
* Beta v121.0b2

**Tested platforms**
* Affected platforms: Windows 10/11 + JAWS/NVDA; Ubuntu 22 + ORCA.
* Unaffected platforms: MacOS + VoiceOver (the messages can be read using CTRL+ALT+UP/DOWN)

**Steps to reproduce**
1. Launch JAWS, then Firefox
2. Make sure new webcopmpat feature is enabled:
ui.new-webcompat-reporter.enabled  = true
3. Load any webpage
4. Go to Hamburger Menu / Report broken site
5. Fill in some information and activate "Send" button.
4. Observe how the JAWS/NVDA reads the webcompat reporter's confirmation dialog.

**Expected result**
* The confirmation message is instantly being read.

**Actual result**
* The confirmation message is not read.

**Regression range**
* not a regression, but an implementation flaw.

**Additional information**
* This issue also occurs with NVDA and ORCA.
Bug: Set as default background color button does not match Figma
Status: RESOLVED
Priority: P3
Resolution: DUPLICATE
Created: 2023-11-23 14:28:54+00:00
Resolved: 2024-04-29 13:48:38+00:00

**Found in**
* 121.0b2


**Affected versions**

*122.0a1 (2023-11-23)
* 120.0b2







**Tested platforms**
* Affected platforms: Windows 10, Windows 11
* Unaffected platforms:  macOS 12, Ubuntu 22



**Preconditions**
* browser.mailto.dualPrompt:true
* browser.mailto.prompt.os: true
* browser.mailto.prompt.os: true
* new profile
* Firefox not set as default OS mailto application


**Steps to reproduce**
1. Open https://get.wireme.de/mailto-test.html and click the button.
2. Observe the Set as default button.



**Expected result** 
* The `Set as default` button has a blue background as in [Figma](https://www.figma.com/file/MTox8iIdh1xxJ5SfnpsczZ/MailTo-Handling?type=design&node-id=34-15020&mode=design&t=HRSj9wSxFShODNvx-0).
**Actual result**
* The `Set as default` button is not displayed as in [Figma](https://www.figma.com/file/MTox8iIdh1xxJ5SfnpsczZ/MailTo-Handling?type=design&node-id=34-15020&mode=design&t=HRSj9wSxFShODNvx-0).




**Regression**
* N/A, new feature.






**Additional notes**
* Attached a screen shot.
* Also, a blue information icon "i" is present on the prompts in the current Nightly and Beta and in Figma, it is not.
* The missing background color button can also be seen with Hight Contrast.
Bug: Interaction with the Firefox Suggest Opt-In section generates main Glean events with “unknown” values for the “results” and “selected_result” parameters
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2023-11-23 16:16:35+00:00
Resolved: 2023-11-29 15:01:36+00:00

**[Notes]:**
- This issue is reproducible with all types of Glean events: impression, engagement, and abandonment.
- This issue is reproducible when clicking any of the “Learn more” link and the “Allow suggestions” or “Not now” buttons from the Opt-In section.

**[Affected versions]:**
- Firefox Beta 121.0b2 - Build ID: 20231122091904
- Firefox Nightly 122.0a1 - Build ID: 20231123095534

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

**[Prerequisites]:**
- Have an en* Firefox build installed.
- Have the following prefs in the "about:config" page:
  - `browser.search.region` set to `US`;
  - `browser.urlbar.quicksuggest.contextualOptIn` set to `true`;
  - `browser.urlbar.quicksuggest.contextualOptIn.topPosition` set to `true`; 
  - `devtools.chrome.enabled` set to `true`; 

**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Navigate to the “about:glean” page and add a tag name in the first field from "About Testing".
3. Select “events” from the dropdown and click the “Apply settings and submit ping” button.
4. Run the following snippet in the Browser Console:
`Services.fog.setMetricsFeatureConfig(JSON.stringify({
"urlbar.abandonment": true,
"urlbar.engagement": true,
"urlbar.impression": true,
})
);`
5. Open a new tab and click inside the Address Bar.
6. Click the “Allow suggestions” button from the Opt-In section.
7. Go back to the “about:glean” page and click again the “Apply settings and submit ping” button.
8. Open the last event from https://debug-ping-preview.firebaseapp.com/pings/<tag from step 2>.
9. Observe the engagement event.

**[Expected result]:**
- The event contains specific values for each parameter.

**[Actual result]:**
- The  “results” and “selected_result” parameters have “unknown” values.

**[Additional notes]:**
- This issue is reproducible only when the Opt-In section is on Top.
- This issue is not reproducible when the Opt-In section is on the Bottom since the section is outside the results area and the event doesn't register the same way:
  - the engagement event is not registered at all and the impression and abandonment ones don't contain anything related to the Opt-In section nor any "unknown" values (event [example](https://debug-ping-preview.firebaseapp.com/pings/CF-1-DESKTOP/b197c8f5-1dd2-4f8e-882f-16d9c5801700)).
- Attached is a [screen recording](https://drive.google.com/file/d/1GUZxiSGyBvH0iZfT1Wnf-89-xVMJIQq6/view?usp=sharing) of the issue.
Bug: Slow rendering of a PDF with a lot of pages
Status: NEW
Priority: P3
Created: 2023-11-23 16:46:39+00:00
Resolved: 2024-03-15 12:50:51+00:00

The PDF is 140 MB and is copyrighted work, so it's not possible to link it here, but I can send it to somebody if needed.

What I'm doing is I'm scrolling down the document, using either the trackpad or the scrollbar.
Then I stop "somewhere" and wait.

On this computer this takes a few secondes for the page to appear. On an older computer this can take ~30 secondes.

Here is a profile: https://share.firefox.dev/3sOugp4
From looking at this profile, it looks like we're generating some pages repeatidly, just not the right one.
From looking at the screenshots and the dom worker track, it looks like the fourth-to-last block of work is responsible for displaying the relevant page. The next one displays the previous page, the next one the next page. The last one and all other blocks, I don't know.

So if I had to guess, I'd think that we're queuing rendering requests and handling all of them, whereas we should probably cancel most of them at one point (not the one currently rendering because that can be complicated), or at least move the relevant one near the top of the queue.
Bug: Abandonment tests are not correctly asserted
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2023-11-23 18:51:07+00:00
Resolved: 2023-11-29 05:04:12+00:00

In Bug 1865263, I refactored the test code but erroneously implemented the assertion checks for abandonment (they essentially all passed).

It is a test only bug which doesn't affect the telemetry reporting.
Bug: RTL - shopping sidebar container flickers on the right side when opening/closing the sidebar
Status: NEW
Priority: P3
Created: 2023-11-23 18:52:08+00:00
Resolved: 2023-11-30 16:57:01+00:00

STR:
1. Enable bidi mode in Browser Toolbox (alternatively: load Firefox in RTL language)
2. Make sure sidebar feature is enabled and profile is opted in
2. View product page ([example](https://www.amazon.com/SteelSeries-Arctis-Multi-System-Gaming-Headset/dp/B0B8Q4CR52/)) and ensure shopping sidebar is visible
3. Close sidebar with urlbar shopping icon or the close button on the sidebar

Expected:
- there should be no sudden flicker on the right side of the page when closing/opening the sidebar in RTL mode

Actual:
- there is a slight flicker on the right side of the page, which is very distracting visually

Notes:
- this issue probably existed for a while, but I believe that it will be way more obvious once [we show sidebar animations](bugzilla.mozilla.org/show_bug.cgi?id=1858762).
- I tested this on MacOS and can't recall at the moment if it also occurs on other platforms
Bug: Delete all passwords from Desktop and syncing does not remove them from other devices
Status: NEW
Priority: P3
Created: 2023-11-23 19:59:32+00:00
Resolved: 2024-12-23 21:59:31+00:00

User Agent: Mozilla/5.0 (Android 8.1.0; Mobile; rv:109.0) Gecko/119.0 Firefox/119.0

Steps to reproduce:

Prerequisites
1. Firefox Desktop (Ubuntu) attached to Sync account
2. Firefox Android (Android 10) on mobile phone attached to the same Sync account
3. Password sync enabled on both devices
4. Same password entries visible in Saved Logins on both devices

Steps
A. In Firefox Desktop go to Saved Logins > Delete All and confirm. Manually run sync by clicking on user profile in hamburger menu and choosing Sync now.
B. Uninstall Firefox Android on mobile phone using Play Store
C. Reinstall Firefox Android 119.1.1 on mobile phone using Play Store
D. Go to Firefox saved logins on mobile phone - no entries present 
E. Open Firefox on mobile phone and associate with Sync account.
F. Go to Firefox saved logins on mobile phone - password entries present 



Actual results:

Password entries appear in the phone at step F although they are completely removed from Firefox Desktop in step A and synced at step B.

Problem also occurs on Firefox Android 119.1.1 on my tablet when following the steps above.


Expected results:

Phone should show same entries as Desktop i.e. zero entries.
There is no Delete All in Saved Logins on Firefox Android and I have hundreds of entries.

So it seems that the only way to get rid of these is to completely delete my Mozilla account and lose bookmarks/history, which I'm not keen to do.

Is there a workaround for this? Thanks.
Bug: Progress icon does not appear for (re)analysis-in-progress messages in Storybook
Status: NEW
Priority: P3
Created: 2023-11-23 20:24:09+00:00
Resolved: 2023-11-23 20:26:04+00:00

STR:
1. Run `./mach storybook` (alternatively, run with `--no-open` if you don't want to open a new window)
2. In Storybook, go to Shopping > Default Shopping Message Bar component

Expected:
- reanalysis-in-progress and analysis-in-progress message bar types should show the progress icon in Storybook

Actual:
- the progress icon doesn't appear at all, although the percentages do

Note:
- it might be worth noting that the these two messages still use the now deprecated `message-bar` (see Bug 1855471). I wonder if it has something to do with that.
Bug: update runs during fullscreen video playback (netflix)
Status: UNCONFIRMED
Priority: --
Created: 2023-11-23 22:44:05+00:00
Resolved: 2023-12-19 17:08:30+00:00

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

Steps to reproduce:

watching netflix in fullscreen


Actual results:

in the middle of watching videos in fullscreen, firefox updated itself to version 120.0


Expected results:

updates should only be applied at a reasonable time. reasonable is:
 - when firefox is started
 - while running, but only if i am not in fullscreen and i confirmed it explicitly. after all i may loose all currently opened sessions, which might for example contain unsaved forms or progress, which is not really acceptable.
Bug: Pressing the Enter key twice on the Set as default button will display two confirmation messages
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2023-11-24 09:27:27+00:00
Resolved: 2024-04-24 10:35:39+00:00

**Found in**
* 121.0b3

**Affected versions**
* 121.0b3
* 122.0a1

**Affected platforms**
* Windows 10, Windows 11

**Preconditions**
 * browser.mailto.dualPrompt:true
* browser.mailto.prompt.os: true
* browser.mailto.prompt.os: true
* new profile
* Firefox not set as default OS mailto application

**Steps to reproduce**
1. Open https://get.wireme.de/mailto-test.html
2. Click "add random site" button to trigger the prompts
3. Reach the Set as default button on the first prompt using the Tab key
4. Hit Enter/Space key two times

**Expected result**
* Confirmation messages are displayed that Firefox and mail site are set as the default app for mailto links

**Actual result**
* Pressing the Enter key twice on the Set as default button will display two confirmation messages

**Regression range**
* New feature
Bug: Form layout misaligned in XFO/CSP error page
Status: NEW
Priority: P3
Created: 2023-11-24 09:34:44+00:00
Resolved: 2024-06-04 14:11:33+00:00

We show an error page when websites try to embed another website that doesn't want to be embedded (e.g., using X-Frame-Options or CSP frame-ancestors).

Steps to repeat:
1. Set up a web page that frames, e.g., google search `<iframe src="https://www.google.com" width="640px" height="480px">
</iframe>`
1.1. You can use this jsfiddle, but I don't know how stable that's going to be. https://jsfiddle.net/456w0p2b/
2. Observe the error page

What should happen:
- The checkbox should be somewhat properly aligned with the rest of the page.

What actually happens:
- It's left aligned without any left margin/padding.
Bug: Trackpad back gesture indicator appears on the wrong side of the screen
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2023-11-24 13:53:45+00:00
Resolved: 2023-11-25 09:20:17+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. Open a page in Firefox, then click a link so that there is a page to navigate back to.
2. Do a 2 finger swipe rightwards to trigger a back navigation.


Actual results:

The arrow indicator appears on the wrong (right-hand) side of the screen.


Expected results:

The arrow indicator appears on the left side of the screen.

The forward navigation indicator is unaffected.

Output from mozregression:
2023-11-25T00:41:08.344000: DEBUG : Found commit message:
Bug 1863917 - Use nesting in browser-shared.css. r=desktop-theme-reviewers,emilio

Differential Revision: https://phabricator.services.mozilla.com/D194324