av9ash/GitBugs huggingface dataset:
Bug: Intermittent browser/base/content/test/general/browser_contentAltClick.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2024-01-20 02:33:11+00:00
Resolved: 2025-02-03 12:10:14+00:00

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

---
```
[task 2024-01-20T00:33:35.146Z] 00:33:35     INFO - TEST-PASS | browser/base/content/test/general/browser_contentAltClick.js | Downloaded link in iframe. - 
[task 2024-01-20T00:33:35.146Z] 00:33:35     INFO - Console message: [JavaScript Error: "Error: No DOM node set for aPlacesNode.
[task 2024-01-20T00:33:35.146Z] 00:33:35     INFO - node.type: 0. node.parent: [xpconnect wrapped nsINavHistoryResultNode @ 0x11e8f6580 (native @ 0x11caf2340)]" {file: "chrome://browser/content/places/browserPlacesViews.js" line: 116}]
[task 2024-01-20T00:33:35.146Z] 00:33:35     INFO - _getDOMNodeForPlacesNode@chrome://browser/content/places/browserPlacesViews.js:116:13
[task 2024-01-20T00:33:35.147Z] 00:33:35     INFO - nodeTitleChanged@chrome://browser/content/places/browserPlacesViews.js:499:20
[task 2024-01-20T00:33:35.147Z] 00:33:35     INFO - 
[task 2024-01-20T00:33:35.147Z] 00:33:35     INFO - Leaving test bound test_alt_click_in_frame
[task 2024-01-20T00:33:35.147Z] 00:33:35     INFO - Buffered messages finished
[task 2024-01-20T00:33:35.148Z] 00:33:35     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/general/browser_contentAltClick.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 2024-01-20T00:33:35.148Z] 00:33:35     INFO - GECKO(2044) | MEMORY STAT | vsize 16584MB | residentFast 515MB | heapAllocated 188MB
[task 2024-01-20T00:33:35.149Z] 00:33:35     INFO - TEST-OK | browser/base/content/test/general/browser_contentAltClick.js | took 92660ms
```
Bug: Firefox causing Win 11 to restart following sleep
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2024-01-20 20:34:04+00:00
Resolved: 2024-02-09 13:29:36+00:00

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

Steps to reproduce:

1) Boot into Win11 Pro.
2) Start Firefox 121.0.1
3) Restore all previous open tabs in Firefox
4) Start Visual Studio which then start WSL (Windows Sub System for Linux)
5) Put computer to Sleep


Actual results:

Instead of waking up normally, Win11 did a complete re-start which resulted in critical errors in Event Viewer. Downgrading Firefox to Version 120.0.1 fixes the sleep reboot problem with all other things unchanged. 

Attached are SysInfo and Events logs information


Expected results:

Windows should wake up normal instead of a complete reboot
Bug: Impossible to leave search bar with shift+tab
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2024-01-20 22:05:28+00:00
Resolved: 2024-01-29 09:42:46+00:00

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

Steps to reproduce:

Focus the search bar and press shift+tab.


Actual results:

The search menu closes and reopens and focus remains in the search bar.


Expected results:

Focus should move to the previous control in the navigation bar. If the aim is to be consistent with the url bar, you would press esc to close the menu, which does happen, and then press shift+tab. But, doing this just reopens the menu.
Bug: After closing a tab that was reopened using ctrl-shift-t, we don't put the right tab on foreground
Status: NEW
Priority: P3
Created: 2024-01-21 12:50:41+00:00
Resolved: 2024-01-23 15:44:02+00:00

STR:
1. Have some tabs open.
2. Close one tab.
3. Select a tab that's not one of the adjacent tabs from the one that was just closed.
4. Press ctrl-shift-T => this reopens tab closed at step 2.
5. Press ctrl-w => this closes the tab that was just reopened at step 4, and selects an adjacent tab.

Instead it should select the tab that was selected at step 3. Why? Because that's the behavior when using ctrl-T to open a blank tab, where closing it will come back to the previously selected tab. Note: does this behavior depend on a pref?

I'm on Nightly but I think this behavior happens for some time now.
Bug: firefox with sync prefs.js is ansi instead utf-8
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2024-01-21 13:05:41+00:00
Resolved: 2024-02-08 13:28:34+00:00

Steps to reproduce:

create a fresh profile -> prefs.js is UTF-8
sync it, close firefox -> prefs.js is ANSI
convert prefs.js to UTF-8, 
run and close firefox with sync -> prefs is again ANSI

due this about:support section "important modified settings" is quirked, see image


Actual results:

prefs.js is written in ANSI format with sync


Expected results:

prefs.js should stay utf-8 with sync
Bug: Default search bar and link behavior is defaulting to HTTP
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-01-21 22:42:30+00:00
Resolved: 2024-01-23 17:11:27+00:00

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

Steps to reproduce:

After a fresh install of Firefox, start the browser.  On the new tab screen, start entering an address in the unified search/address bar such as:
"nfl.org"
WIthout the leading https:// and www specified, it seems the "Visit" option (not from Suggestions or History yet) the default is to visit the website as "http://".

I'm unsure how deep into the logic of links this may go, if there are other vector opportunities from JS/HTML to redirect a browser and have it default to http.  This may lead to timeouts due to server not redirecting.


Actual results:

http is being defaulted to, when website designers and users would expect default to be https from address bar.


Expected results:

https should always be the default with http as a fallback.  The standard should be to default to https and only if explicitly written should http be used.  This seems to be resolved with HTTPS-Only mode, however, this still feels like poor form.
Bug: windows lost on exit
Status: RESOLVED
Priority: P2
Resolution: DUPLICATE
Created: 2024-01-22 11:37:18+00:00
Resolved: 2024-04-29 16:06:56+00:00

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

Steps to reproduce:

Exit Firefox 121.01 while multiple windows open (set to retain windows)


Actual results:

When restarted, often 1 complete window will have disappeared. Does not appear in recently closed windows or tabs


Expected results:

Should remember all windows!  I have 20, lose 1 typ lost per closure. Looks like an off-by-1 bug.
Bug: Tab hover card changes window order
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2024-01-22 15:02:38+00:00
Resolved: 2024-03-28 13:52:26+00:00

Hello!

STR:
1. In Nightly on macOS set `browser.tabs.cardPreview.enabled` to `true`
2. Open two windows and position them in a way that they overlap and the tab strip of the partially covered window is still visible
3. On the window that is covered by the other, hover over a tab until the tab preview appears.
(the video makes it a lot clearer I think)

Expected result:
The tab preview appears, but the window is still covered by the other window.

Actual result:
The window where the tab preview shows up is being moved on top of all others.
Bug: Firefox uses title content as acc name when an image has an empty alt
Status: RESOLVED
Priority: P3
Resolution: DUPLICATE
Created: 2024-01-22 15:46:12+00:00
Resolved: 2024-01-22 23:48:50+00:00

When an image has an empty alt attribute (alt or alt="") it signifies that the image should be ignored by a screen reader and that the role should not be exposed in the acc tree https://w3c.github.io/html-aam/#el-img-empty-alt, and it has no accessible name https://w3c.github.io/html-aam/#img-element-accessible-name-computation This works correctly in Chrome Version 120.0.6099.225 (Official Build) (64-bit) but not in Firefox 121.0.1 (64-bit)

steps to reproduce:
1. open https://cdpn.io/pen/debug/wvOeOqz
2. look at the accessibility tree and note that in Firefox the accessible name for the image in the first case is derived from the title attribute.
Bug: In Bookmarks Library, when I right click on a web link, I do not see the option to open in a private window.  If I click to open, open in a new tab, or in a new window, they all open in a private window.
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2024-01-22 21:31:27+00:00
Resolved: 2024-01-23 19:47:50+00:00

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

Steps to reproduce:

In the Bookmarks Library after opening a Firefox non-private window, I find a link under History.  When I right-click on a link, I only see Open, Open in New Tab, and Open in New Window; I do not see Open in New Private Tab or Window. 


Actual results:

 Each time I click Open, Open in New Tab, or Open in New Window, any and all links open in a Private Window.


Expected results:

The web link should open in a new tab in the non-private window I already have open or open in a new non-private window.
Bug: Make RemoteSettings devtools environment available in the Suggest Rust backend
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2024-01-23 00:12:38+00:00
Resolved: 2024-01-30 20:27:21+00:00

Now, as we have not passed any RemoteSettings configuration, the devtools environment is not applied to Rust component.
* https://searchfox.org/mozilla-central/rev/c130c69b7b863d5e28ab9524b65c27c7a9507c48/browser/components/urlbar/private/SuggestBackendRust.sys.mjs#168-171
* https://searchfox.org/mozilla-central/rev/c130c69b7b863d5e28ab9524b65c27c7a9507c48/third_party/rust/remote_settings/src/client.rs#34-38

In this bug, passing RemoteSettings configuration explicitly to Rust, we will make the devtools environment as well available in Rust.
Bug: mobile doesn't use most files installed in defaults/settings
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2024-01-23 00:57:44+00:00
Resolved: 2024-04-09 16:03:42+00:00

Per mobile/android/installer/package-manifest.in, the only files used from dist/bin/defaults/settings are:
```
defaults/settings/last_modified.json
defaults/settings/blocklists/gfx.json
defaults/settings/main/password-recipes.json
defaults/settings/security-state/onecrl.json
```

As such, all the other files that are in dist/bin/defaults/settings shouldn't be in dist/bin in the first place in mobile builds (apparently thunderbird installs them, but maybe that's a result of cargo culting rather than a deliberate choice).
Bug: Bug about "Open application menu"
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-01-23 02:51:06+00:00
Resolved: 2024-01-25 14:26:14+00:00

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

Steps to reproduce:

When I start Firefox and open "Open application menu" for the first time


Actual results:

 "Report broken site" is displayed 


Expected results:

 "Report broken site" will disappears quickly (less than 0.5 seconds)
Bug: Re-pinning tabs with a notification dot will keep the notification dot on the taskbar icon even after clearing the notification
Status: NEW
Priority: --
Created: 2024-01-23 09:12:04+00:00
Resolved: 2024-02-07 20:23:36+00:00

STR:
1. Log in to https://twitter.com/ (preferably to have some accounts followed so notifications are available)
2. Notice the tab favicon has a notification dot
3. Pin the tab to taskbar
4. Notice the taskbar icon has a notification dot
5. Unpin the tab
6. Clear the notifications
7. Re-pin the tab
8. Observe the pinned taskbar icon still has the notification dot

Expected:
Re-pinning a tab which has had all notifications cleared should no longer show the notification dot on the pinned taskbar icon

Actual:
Tabs re-pinned after clearing notifications still show the notification dot on the icon

Note: Uninstalling the site and then re-pinning it will still keep the notification dot on the taskbar icon.
Bug: Pinned tab is positioned in front of the main Firefox instance when “Launch with Firefox” is enabled
Status: NEW
Priority: P3
Created: 2024-01-23 09:40:13+00:00
Resolved: 2024-11-11 12:29:35+00:00

Preconditions:
1. “Launch with Firefox” is enabled in the main extension panel

STR:
1. Access https://www.wikipedia.org/
2. Pin the tab to taskbar
3. Notice the order of the icons on the taskbar: main Firefox instance icon and then the pinned tab
4. Close the pinned taskbar tab
5. Restart the main Firefox instance
6. Observe the pinned taskbar tab is in front of the main Firefox instance

Expected:
Since the pinned tab launches after Firefox is launched, I would expect that the main Firefox instance be in front of the pinned tab on the taskbar.

Actual:
Pinned tabs icons are in front of the main Firefox instance on the taskbar when they get launched with Firefox.
Bug: Slow launch of pinned tabs when launched either by themselves or with Firefox
Status: NEW
Priority: P4
Created: 2024-01-23 09:53:13+00:00
Resolved: 2024-11-11 12:29:07+00:00

Preconditions:
1. “Launch with Firefox” is enabled in the main extension panel

STR:
1. Access https://www.wikipedia.org/
2. Pin the tab to taskbar
3. Close the pinned tab window and launch it again from the taskbar
4. Notice the tab is fairly slow to launch
5. Close the pinned tab window
6. Restart the main Firefox instance 
7. Observe the pinned tab is once more slow to launch even when launching with Firefox

Expected:
Lower launch times for pinned tabs.

Actual:
Pinned tabs are a bit slow to launch.
Bug: Lower quality/resolution icons for moved/pinned tabs for certain websites
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-01-23 10:26:12+00:00
Resolved: 2024-01-23 16:48:22+00:00

STR:
1. Access https://www.volkswagen.ro/, https://edition.cnn.com/, https://www.sport.ro/ in separate tabs
2. Pin the tabs to taskbar
3. Notice the taskbar icons for the pinned tabs are lower quality/resolution

Expected:
Higher quality/resolution icons for the pinned tabs

Actual:
Some websites, when pinned show a low quality/resolution icon on the taskbar.

Note: There certainly are more websites that could be affected, the ones above are just a few I stumbled upon when browsing.
Bug: Top pick alignment is broken
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2024-01-23 10:43:21+00:00
Resolved: 2024-01-29 08:30:46+00:00

From adw:

>The text as a whole needs to be center-aligned with the icon, and the url should be baseline-aligned with the titleI’m testing with top picks/navigational suggestions. They can be turned on with these prefs:
>
>    browser.urlbar.quicksuggest.enabled
>    browser.urlbar.quicksuggest.dataCollection.enabled
>    browser.urlbar.suggest.quicksuggest.nonsponsored
Bug: Tab previews often seem to be captured too early
Status: RESOLVED
Priority: P3
Resolution: DUPLICATE
Created: 2024-01-23 13:22:58+00:00
Resolved: 2024-05-13 16:03:57+00:00

Quite often when I look at tab previews I find a preview that looks half rendered. Maybe the screenshot was taking while the page was still loading or something? Here is an example of the preview for WhatsApp's web interface. I see this for other sites too but WhatsApp seems to be reasonably reproducible.
Bug: Allow to disable 'Go To Tab' with hotkeys (Ctrl+1 ... 8)
Status: NEW
Priority: --
Created: 2024-01-23 17:27:08+00:00
Resolved: 2024-01-25 15:04:50+00:00

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

Steps to reproduce:

I updated to the latest version of Firefox.




Actual results:

After the update - when I click Ctrl+1, Ctrl+2, Ctrl+3 - Firefox is switching my tabs.


Expected results:

Firefox should not be affected by Ctrl+1, Ctrl+2, Ctrl+3.
I use those keys for other purpose. I need to have possibility to disable this new behavior.

I know that this issue was reported, but it was reported 16 years  
https://bugzilla.mozilla.org/show_bug.cgi?id=432137
Bug: Cloudflare problem
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2024-01-23 18:11:38+00:00
Resolved: 2024-01-24 21:57:41+00:00

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

Steps to reproduce:

Latest Firefox incompatible with any site that uses cloudflare.


Actual results:

Go to url
get message:
Your browser is out of date!
Update your browser to view this website correctly.

This has been happening regularly for the past 2 months


Expected results:

Should not get error message,
Should be directed to requested page
Bug: Intermittent browser/components/enterprisepolicies/tests/browser/browser_policy_disable_feedback_commands.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2024-01-23 18:43:59+00:00
Resolved: 2024-02-21 12:00:49+00:00

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

---
```
[task 2024-01-23T17:37:02.735Z] 17:37:02     INFO - TEST-PASS | browser/components/enterprisepolicies/tests/browser/browser_policy_disable_feedback_commands.js | The `This isn’t a deceptive site` item should be disabled - 
[task 2024-01-23T17:37:02.739Z] 17:37:02     INFO - Console message: [JavaScript Error: "NS_ERROR_NOT_AVAILABLE: Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIChannel.contentType]" {file: "resource://devtools/client/jsonview/Sniffer.sys.mjs" line: 50}]
[task 2024-01-23T17:37:02.739Z] 17:37:02     INFO - getMIMETypeFromContent@resource://devtools/client/jsonview/Sniffer.sys.mjs:50:49
[task 2024-01-23T17:37:02.740Z] 17:37:02     INFO - 
[task 2024-01-23T17:37:02.740Z] 17:37:02     INFO - Buffered messages finished
[task 2024-01-23T17:37:02.741Z] 17:37:02     INFO - TEST-UNEXPECTED-FAIL | browser/components/enterprisepolicies/tests/browser/browser_policy_disable_feedback_commands.js | Test timed out - 
[task 2024-01-23T17:37:02.741Z] 17:37:02     INFO - GECKO(1869) | Completed ShutdownLeaks collections in process 1869
[task 2024-01-23T17:37:02.741Z] 17:37:02     INFO - TEST-START | Shutdown
[task 2024-01-23T17:37:02.741Z] 17:37:02     INFO - Browser Chrome Test Summary
[task 2024-01-23T17:37:02.741Z] 17:37:02     INFO - Passed:  283
[task 2024-01-23T17:37:02.742Z] 17:37:02     INFO - Failed:  1
[task 2024-01-23T17:37:02.742Z] 17:37:02     INFO - Todo:    0
[task 2024-01-23T17:37:02.743Z] 17:37:02     INFO - Mode:    e10s
[task 2024-01-23T17:37:02.743Z] 17:37:02     INFO - *** End BrowserChrome Test Results ***
```
Bug: Sometimes we show multiple stacked "You must enable DRM" notifications at the same time
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-01-23 18:56:34+00:00
Resolved: 2024-02-02 09:19:39+00:00

When visiting https://www.yahoo.com/ in a fresh profile today, I sometimes see two "You must enable DRM" prompts at once. See attached screenshot.  (I'm guessing two isn't a hard limit; maybe we might show an unbounded number of these, in an extremely pathological case?)

We should probably have a mechanism to enforce that we only show one iteration of this notification at a time.

I encountered this in Firefox Nightly 124.0a1 (2024-01-23) (64-bit) on Ubuntu 22.04
Bug: Firefox on macOS and the macOS Finder report different file sizes of downloaded files
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-01-23 19:44:51+00:00
Resolved: 2024-02-02 13:20:14+00:00

Steps to reproduce:

download a file (around 10 MB or larger to see the difference - larger files create larger differences) using Firefox on macOS and compare the reported file size in Firefox (in the downloads pop up window or the "Show all downloads" page) and the macOS Finder


Actual results:

reported file sizes don't match


Expected results:

reported file sizes should match. Firefox should follow the OS system standard that it's installed on. On macOS (and maybe iOS and other OSes - but not on Windows) that is to report file download sizes in decimal bytes (i.e. 1 KB = 1000 bytes, 1 MB = 1 million bytes, etc...) rather than binary bytes (i.e. 1 KB = 1024 bytes, 1 MB = 1 048 576 bytes, etc...)
Bug: Firefox for Linux not registered as a handler for PDF files
Status: NEW
Priority: --
Created: 2024-01-23 20:57:08+00:00
Resolved: 2024-02-02 17:24:07+00:00

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

Steps to reproduce:

Try to open a PDF file with the app.


Actual results:

Firefox did not show up in the list of recommended apps.


Expected results:

Firefox does show up.

This should be fixed by adding `application/pdf` to the `MimeType` key in Firefox's desktop entry.
Bug: xss found in firefox buildin pdf embedder
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-01-24 00:24:57+00:00
Resolved: 2024-05-30 18:19:25+00:00

here is step to do 
step-> as shown in video i made malicious pdf just load that pad in 115.6.0esr (64-bit)of linux 
attachment is below
Bug: Adjust the position of some buttons in about:asrouter#devtools-targeting
Status: NEW
Priority: P3
Created: 2024-01-24 00:28:46+00:00
Resolved: 2024-02-12 15:23:04+00:00

The "Evaluate" button next to the targeting box is vertically centered. This is kind of annoying since if your evaluation result is really long, it'll wrap onto many lines, and the button will get moved down to the vertical center of all that text. I saw this when evaluating `addonsInfo` on my nightly profile, which has many extensions. I think the button should be moved up to the top of the container.

I also noticed the "Copy parameters" button below it is awkwardly positioned.

And the "Expire cache" button should have a wider right margin, so there's more space between it and the text next to it.

Suggest P3 priority.
Bug: Cross device information error: Firefox View sync time set to initial time of the Unix timestamp
Status: NEW
Priority: P3
Created: 2024-01-24 01:53:49+00:00
Resolved: 2024-07-25 09:39:49+00:00

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

Steps to reproduce:

 View cross device recent activity pages 


Actual results:

 The displayed other devices are duplicated and the last access time is incorrect 


Expected results:

 The other devices displayed should be non repetitive and have the correct timing