av9ash/GitBugs huggingface dataset:
Bug: Microphone permissions request does not display if gUM called from a redirected iframe
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2022-12-13 01:42:14+00:00
Resolved: 2023-01-02 22:03:02+00:00

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

Steps to reproduce:

1. Build a webpage that calls getUserMedia (gUM) in order to get just the user's microphone.
2. Build another webpage (I believe it needs to be on a separate domain/subdomain) which does noting but redirect to the first page.
3. Build another webpage which includes an iframe with microphone permissions, and a src linking to the second page.
4. Upon loading the third page, expect to see a permissions door hanger asking you to grant access to your microphone.


Actual results:

The permissions door hanger never opens. The gUM promise will stall and never resolve or reject because the user has never responded to the request. A microphone icon is shown in the chrome, where the door hanger should be, but clicking it does nothing.

This can be reproduced by running example 2 in this jsfiddle I created. I used TinyURL to simulate a redirect to an otherwise working example:
https://jsfiddle.net/MitchTalmadge/vnhqdwka/4/


Expected results:

A microphone permissions request door hanger should open, asking the user to allow access to their microphone.
Bug: Separators in FxA panel view should be toolbarseparators, not menuseparators
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2022-12-13 08:16:15+00:00
Resolved: 2022-12-14 03:41:23+00:00

The colors of menuseparators and toolbarseparators are different. The `#PanelUI-remote-tabs-separator` above the synced tabs deck is a toolbarseparator, as separators in panels normally are. But if you connect multiple devices, the device lists will be [separated by a menuseparator](https://searchfox.org/mozilla-central/rev/a0d4f8f112c5c792ae272bf6ce50763ddd23ffa2/browser/base/content/browser-sync.js#154).
Bug: The address bar flickers when typing an Intervention card string that has a Quick action as well
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2022-12-13 09:42:32+00:00
Resolved: 2023-11-22 11:18:34+00:00

**Found in**
* 109.0b1 

**Affected versions**
* 110.0a1 (2022-12-12)
* 109.0b1
* 108.0	


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





**Steps to reproduce**
1. Open Firefox and type `refresh firefox` inside the address bar.
2. Observe the address bar while typing.


**Expected result**
* No flickering is displayed.

**Actual result**
* Address Bar flickers.

**Regression range**
* This started happening with the implementation of Quick Actions: bug 1778132.

**Additional notes**
* Attached a screen recording of the issue.
* Closing and reopening the Adress Bar will make the issue reproduce again.
* There is an enhancement logged for quick actions and intervention that might fix this issue as well (bug 1794092).
Bug: The Callout Tour for pdf.js is wrongly positioned on Firefox RTL locale builds
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-12-13 09:58:48+00:00
Resolved: 2023-01-05 12:44:57+00:00

**[Affected versions]:**
- Nightly 110.0b1 
- Firefox Beta 109.0b1

**[Affected Platforms]:**
- Mac 12.4
- Windows 10 x64
- Linux Mint 20

**[Prerequisites]:**
- Have a Firefox RTL build extracted/installed (eg: ar build).
- Have the "nimbus.debug" set to true in about:config.
- Be enrolled in any of the experiment branches. You can force enroll by navigating to the following links: [Treatment A](about:studies?optin_slug=pdfjs-feature-callout&optin_branch=treatment-a&optin_collection=nimbus-preview) or [Treatment B](about:studies?optin_slug=pdfjs-feature-callout&optin_branch=treatment-b&optin_collection=nimbus-preview).

**[Steps to reproduce]:**
1. Open the Firefox browser with the profile from the prerequisites.
2. Navigate to a PDF link, eg: [TestPDFFile](https://www.clickdimensions.com/links/TestPDFfile.pdf).
3. Observe the Callout Tour for pdf.js.

**[Expected result]:**
- The Callout Tour for pdf.js is positioned in the left part pointing to the Text icon.

**[Actual result]:**
- The Callout Tour for pdf.js is positioned in the right part pointing to nothing in the toolbar.

**[Notes]:**
- The issue is also reproducible for the second screen.
- Attached is a screenshot of the issue.
Bug: On Firefox locales with long strings the title of the PDF callout message overlaps with the "X" button
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-12-13 10:33:56+00:00
Resolved: 2022-12-16 14:27:28+00:00

**[Affected versions]:**
- Firefox Beta 109.0b1 - Build ID: 20221212143511

**[Affected Platforms]:**
- Windows 10 x64
- macOS 12.6
- ubuntu 20.04 x64

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

**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Navigate to `about:studies?optin_slug=pdfjs-feature-callout&optin_branch=treatment-b&optin_collection=nimbus-preview`.
3. Navigate to an URL ending in ".pdf" (e.g. https://www.africau.edu/images/default/sample.pdf).
4. Observe the PDF callout message.

**[Expected result]:**
- All the elements from the PDF callout message are visible.

**[Actual result]:**
- The callout title overlaps with the "X" button.

**[Additional Notes]:**
- This issue is also reproducible on Firefox "de" locale.
- Attached a screenshot of the issue.
Bug: Firefox Suggest does not honor the setting to disable search suggestions in private windows
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-12-13 10:55:09+00:00
Resolved: 2022-12-14 16:23:27+00:00

I have the related setting in about:preferences disabled, but I see a couple of suggestions by "Firefox Suggest" in my private browser window, which is a bit surprising.

Is this the intended behaviour?
Bug: Firefox view "Learn how" link for SUMO page doesn't work
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-12-13 11:07:05+00:00
Resolved: 2022-12-21 14:21:45+00:00

**Found in**
* Firefox 109.0b1

**Affected versions**
* Firefox 109.0b1
* Firefox Nightly 110.0a1

**Tested platforms**
* Affected platforms: Windows 10x64, macOS 10.12, Ubuntu 18.4
* Unaffected platforms: none

**Steps to reproduce**
1. Open Firefox view tab and continue to sign in with a Firefox account
2. Log into Sync with valid credentials on another device and go through with the firefox view onboarding process for Tab Pickup 
3. Perform the onboarding process, click on the "Learn how" link when progress is at 33% and 66%

**Expected result**
* The "Learn how" link correctly redirects the user to the SUMO page.

**Actual result**
* Firefox view "Learn how" link for SUMO page doesn't work

**Regression range**
* First bad: 2022-12-07
* Last good: 2022-12-06
* Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=8e09abeeb445553bd956d537bcf54fcdf812bb52&tochange=8d20cccc1dc681d05d412be763ee5a0602a47a4a
* Potentially regressed by:  Bug 1803505 - Simplify the tab-pickup-container initialization. r=sclements
Bug: [Experiment] The PDF Feature Callout messages are not pointed to their specific icons if an infobar message is displayed
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-12-13 13:08:57+00:00
Resolved: 2023-01-10 16:50:15+00:00

**[Affected versions]:**
- Firefox Beta 109.0b1 (Build ID: 20221212143511)

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

**[Prerequisites]:**
- Have the latest version of Firefox Beta 109 installed.
- Have created and opened a Firefox profile between 6 weeks and 3 months old.
- Have the Firefox browser not set as default.
- Have the “nimbus.debug” pref set to true in the “about:config” page.
- Have the "Always check if Firefox is your default browser" option from the “about:prefererences” unchecked.

**[Steps to reproduce]:**
1. Force enroll in the Treatment A branch of the experiment using the following link: about:studies?optin_slug=pdfjs-feature-callout&optin_branch=treatment-a&optin_collection=nimbus-preview
2. Open a new tab and restart the browser.
3. Ensure that the “Set as default” infobar is displayed.
4. Navigate to a PDF URL (e.g. https://www.clickdimensions.com/links/TestPDFfile.pdf) in the same tab.
5. Observe the top-right part of the page.

**[Expected result]:**
- The first message of the PDF Feature Callout message points to the Text icon.

**[Actual result]:**
- The first message of the PDF Feature Callout message points to the info bar.

**[Notes]:**
- This issue is also reproducible in the Treatment B of the experiment.
- The second message of the PDF callout also points to the info bar.
- Attached is a screenshot of the issue.
Bug: do not show Show tab previews in the Windows taskbar not honored
Status: NEW
Priority: --
Created: 2022-12-13 16:06:15+00:00
Resolved: 2023-02-15 21:26:21+00:00

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

Steps to reproduce:

I did nothing different other than allow FireFox to update to V. 108


Actual results:

As soon as V. 108 loaded I lost my tabs on top of the page and it displayed only current tab on the taskbar.  I can no longer just click to select a different tab.  Unchecking Show tab previews in the Windows taskbar does not change this.


Expected results:

1st.  You should not have made a new change a DEFAULT choice.  An end user should retain control over their own device.
2nd.  The choice to turn off this "choice" should turn it off and revert the view to what the USER prefers, not what your developers prefer, should be honored and turn off the taskbar tab preview BUG.
Bug: The memory used by the Privileged Content process increases by about 5MB every 5 minutes
Status: NEW
Priority: P3
Created: 2022-12-13 16:24:36+00:00
Resolved: 2023-06-05 23:18:33+00:00

I captured a profile of Firefox doing nothing for about an hour. I was surprised by the shape of the memory track for the Privileged Content process. I then captured another similar profile with the 'native allocations' feature enabled, which shows which memory is retained:
https://share.firefox.dev/3YjpISs

The memory is from these lines: https://searchfox.org/mozilla-central/rev/a0d4f8f112c5c792ae272bf6ce50763ddd23ffa2/browser/components/newtab/lib/cache-worker.js#179-182 About half of it is the .replace call, and about half is the JSON.stringify call.

I'm not sure what the cause is, it could either be some code of the worker somehow keeping a reference forever. Or it could be the garbage collector not being triggered in the DOM worker, for some reason.

Independently of the memory use concern, I wonder if this code really needs to run every 5 minutes when there's exactly nothing happening in Firefox.
Bug: msgs with multiple groups only get impressions written to one group
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-12-13 16:45:55+00:00
Resolved: 2023-02-07 19:20:49+00:00

If a message has multiple entries listed in the `groups` array, only one of them will get an impression written.  Which group gets written is deterministic, and I suspect it's the last one read in from the groups provider, but I need to verify that.
Bug: Save Image Crashes Firefox
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2022-12-13 18:29:09+00:00
Resolved: 2023-01-06 14:50:19+00:00

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

Steps to reproduce:

Left click on image found on web and select saveas.


Actual results:

About half of the time, attempting to save an image crashes Firefox


Expected results:

Should have completed by opening Windows Explorer and prompting for directory and file name/type.
Bug: Regression: Bookmarks Bar Folder Menus Outline is broken
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2022-12-13 18:54:13+00:00
Resolved: 2022-12-20 09:28:00+00:00

Nightly 110.0a1 (2022-12-13) (64-Bit)
MacOS 10.15.7 & 12.6.1

1.) Create a folder on the Bookmarks Bar
2.) Click on it, so that the menu opens
3.) Take a look at the border of the menu

Actual: Outline is broken.

Expected: A perfect outline.

This is a regression in Nightly 110. It works fine in Stable 108.

A screenshot actual vs expected is attached.

Thanks for checking.
Bug: I've got net new update on firefox desktop, and all my tabs was gone, I can only see arrows and plus icons
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-12-14 03:20:17+00:00
Resolved: 2023-01-12 18:36:34+00:00

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

Steps to reproduce:

Firefox updated on background, I open Firefox


Actual results:

I can create tabs, use them and so on, but I can't see them
Bug: "List All Tabs" down arrow button generate a choppy slow fade in animation before showing up the tab list
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2022-12-14 03:58:39+00:00
Resolved: 2023-07-06 14:58:44+00:00

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

Steps to reproduce:

After updated to Firefox 108 (Linux Mint 21, Mate Desktop + Compiz, Ryzen 2200G computer here), the "List All Tabs" down arrow become sluggish.


Actual results:

It now takes 1 second or maybe more to fade in and show the tab list drop down, with low frame rate choppy animation.


Expected results:

Before update, there is no perceived delay, slowness or choppiness when opening that drop down tab list.
Bug: Mouse wheel scrolling does not work when X-Mouse control is active
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-12-14 08:08:58+00:00
Resolved: 2022-12-16 14:29:30+00:00

Steps to reproduce:

Windows 11 22h2
I have using X-Mouse button control to remap additional mouse buttons (copy/paste).
2.19.2, https://www.highrez.co.uk.
Actually button remaps works. Only page scrolling stops working.
Only button remapping is activated (intercepted) in X-mouse button control.


Actual results:

After 109(beta) update mouse wheel scrolling stops working when X-Mouse control is active.
After rollback to 108 - everything is ok.
Bug: PDF takes 40 seconds to render.
Status: NEW
Priority: P3
Created: 2022-12-14 09:46:53+00:00
Resolved: 2023-01-02 13:37:31+00:00

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

Steps to reproduce:

Open the attached PDF.


Actual results:

PDF takes 40 seconds to render.


Expected results:

PDF should render quickly, it appears instant in Adobe.
Bug: Caret browsing shortcut (F7) UI can hardlock the process
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-12-14 09:54:10+00:00
Resolved: 2023-01-11 01:06:18+00:00

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

Steps to reproduce:

So like a lot of "grand" discoveries this one comes thanks to my cat Mr Potato Cat..

He likes to lie on the top of my keyboards, oft resulting in him holding down F7, potentially for minutes at a time.


Actual results:

Either the UI is opening like 50000 times, or at that point clicking anything doesn't work even though it animates like it is being interracted with correctly.

The checkbox to not show it again also will not select when in this state.

The UI either becomes totally unresponsive or opens so many that you could never close them all out.

There is no resolution but to close the browser entirely. When doing so, it does not exit cleanly so when reopening it, it will state "it's already running do you want to close that old process?"


Expected results:

Only one instance of this component should ever be present.
Alternatively the checkbox should be functional in this state (not sure why it's not tbh) so the user can just select that and press no and it closes all prompts with that answer.

Ideally from my standpoint it'd also be best to have the component within some kind of overlay container/layer above the page -- so it's still "page blocking" as the alert is now (probably by design) which would instead mean one instance per tab/page.
Bug: Selenium test fails because of blocking hint "Type less, find more: Search Google right from your address bar."
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-12-14 14:09:37+00:00
Resolved: 2022-12-19 13:41:59+00:00

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

Steps to reproduce:

I run automatic Selenium tests using the official firefox driver for macOS ARM 64.


Actual results:

Firefox starts as it shoulds, then, especially after updates, all tests fail, because Firefox stops working with the hint:
"Type less, find more: Search Google right from your address bar."
The hint has to be accepted with "OK".

End-Result: All tests fail.

PS: Screenshot text is the same error, but in german.


Expected results:

Firefox doesn't show any hints in full automatic mode. So that the Selenium tests _always_ run through.
Bug: The bookmarks menu shows less and less as you move the mouse around
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2022-12-14 15:02:13+00:00
Resolved: 2023-01-26 14:17:32+00:00

With today's Nightly add the Bookmarks menu to the toolbar, open the menu, and move the mouse around over it. The more you hover over menus the more parts of the menu vanish.

Tested with a new profile.

Mozregression: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=6002e93434a2e65a900fbceec1b88322a74ef94e&tochange=06c21393dcc748b7ed2006c1a550919518630e95

(That doesn't look right. I'll explore the changes and possibly try mozregression again.)
Bug: XPCOMGlueLoad error for file /usr/lib/firefox/libnssutil3.so: /usr/lib/firefox/libnssutil3.so: cannot open shared object file: No such file or directory Couldn't load XPCOM.
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-12-14 15:03:31+00:00
Resolved: 2022-12-14 21:39:21+00:00

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36

Steps to reproduce:

After to update ( apt dist-upgrade) on Linux Debian bookworm (sid) 6.0.0-6-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.12-1 (2022-12-09) x86_64 GNU/Linux, firefox don't start.


Actual results:

Launching firefox from the terminal does not start and gives me this error:

XPCOMGlueLoad error for file /usr/lib/firefox/libnssutil3.so: /usr/lib/firefox/libnssutil3.so: cannot open shared object file: No such file or directory Couldn't load XPCOM.
Bug: Intermittent TV browser/base/content/test/contextMenu/browser_contextmenu_linkopen.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2022-12-14 15:23:43+00:00
Resolved: 2023-01-31 17:00:48+00:00

**Filed by:** ctuns [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=399629521&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/K77fhGv0QGKURg0UNZ7c5A/runs/0/artifacts/public/logs/live_backing.log
**Reftest URL:** https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/K77fhGv0QGKURg0UNZ7c5A/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

---
```
[task 2022-12-14T14:36:01.185Z] 14:36:01     INFO - TEST-PASS | browser/base/content/test/contextMenu/browser_contextmenu_linkopen.js | Should have opened a private window. - 
[task 2022-12-14T14:36:01.185Z] 14:36:01     INFO - Waiting for the opened window/tab to close
[task 2022-12-14T14:36:01.185Z] 14:36:01     INFO - Buffered messages logged at 14:36:00
[task 2022-12-14T14:36:01.186Z] 14:36:01     INFO - Console message: [JavaScript Warning: "This page is in Quirks Mode. Page layout may be impacted. For Standards Mode use “<!DOCTYPE html>”." {file: "https://example.com/" line: 0}]
[task 2022-12-14T14:36:01.186Z] 14:36:01     INFO - Leaving test bound test_select_text_link
[task 2022-12-14T14:36:01.187Z] 14:36:01     INFO - Buffered messages finished
[task 2022-12-14T14:36:01.187Z] 14:36:01     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/contextMenu/browser_contextmenu_linkopen.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - 
[task 2022-12-14T14:36:01.188Z] 14:36:01     INFO - GECKO(3076) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2022-12-14T14:36:01.188Z] 14:36:01     INFO - GECKO(3076) | MEMORY STAT | vsize 16097MB | residentFast 327MB | heapAllocated 149MB
[task 2022-12-14T14:36:01.188Z] 14:36:01     INFO - TEST-OK | browser/base/content/test/contextMenu/browser_contextmenu_linkopen.js | took 55020ms
[task 2022-12-14T14:36:01.189Z] 14:36:01     INFO - checking window state
[task 2022-12-14T14:36:01.196Z] 14:36:01     INFO - GECKO(3076) | Completed ShutdownLeaks collections in process 3076
[task 2022-12-14T14:36:01.197Z] 14:36:01     INFO - TEST-START | Shutdown
```
Bug: When I split Firefox with another application in win 11 the toolbar extensions overlap.
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2022-12-14 15:45:59+00:00
Resolved: 2023-02-10 18:20:07+00:00

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

Steps to reproduce:

Nothing. Updated 10 108.0 and split the firefox windows with zoom.


Actual results:

The toolbar overlapped.


Expected results:

They should have looked normal.
Bug: Some desktop devices disappear from send tab list
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2022-12-14 16:37:44+00:00
Resolved: 2023-02-02 15:43:42+00:00

We are getting reports of some desktop devices disappearing from mobile send tab list after we filtered the list to only include active devices (devices active in the last 21 days)

See: https://github.com/mozilla-mobile/fenix/issues/28035

My theory is that since last access data for session tokens doesn't propagate well into SQL database, the latest data for the user's devices is stored in the redis store, but is kicked out of the redis store at a faster rate than 21 days.


However, the fact the some users need to go to their settings menu or sign out/sign in tells me that it's possible the redis store for the device data is not updated either.

The fix here is most likely a server fix, in an ideal world the last access timestamp would be written back, but that's infeasible given how many users we have.

A good solution would probably ensure that our redis store **actually** hold the information and are updated as often as we think they are (on every use of the API)