av9ash/GitBugs huggingface dataset:
Bug: The Highlights from recent reviews card will shrink to fit the available space when clicking the Show More button
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-11-29 13:55:34+00:00
Resolved: 2023-12-15 08:16:09+00:00

**Found in**
* Nightly 122.0a1 (2023-11-29)

**Affected versions**
* Nightly 122.0a1 (2023-11-29)
* Beta 121.0b5

**Affected platforms**
* ALL

**Preconditions:**
browser.shopping.experience2023.enabled - true
browser.shopping.experience2023.optedIn = 0

**Steps to reproduce**
1. Reach https://www.amazon.com/Kirkland-Signature-Ibuprofen-200-Tablets/dp/B01M7ZP3N7/ref=sr_1_1?crid=MSJ2R7CS53LX&keywords=ibuprofen&qid=1701265020&sprefix=ib%2Caps%2C328&sr=8-1
2. Resize the Shopping sidebar to the largest size.
3. Click the Show more button.

**Expected result**
*  The Show more button should expand the Highlights from recent reviews card instead of shrinking it. If there is too much available space it should remain the same.

**Actual result**
* Hitting the Show more button from the Highlights of recent reviews card will cause the Card to shrink instead of expanding.
Please note that with a normal size the issue does not occur. The card will expand a bit instead of shrinking. I think the problem is that the show more button will not be displayed according to the available space by default.

**Regression range**
Not Applicable
Bug: The focus remain stuck the entire Firefox session after focusing any of the buttons from the Search OneOffs section while the Opt-In section is displayed at the bottom
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-11-29 15:38:19+00:00
Resolved: 2023-12-04 15:07:16+00:00

**[Affected versions]:**
- Firefox Beta 121.0b4 - Build ID: 20231120154937
- Firefox Nightly 122.0a1 - Build ID: 20231129050021

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

**[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

**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Open click in the Address Bar.
3. Press the down arrow key until the "Not not" button is focused.
4. Open a new tab and click the Address Bar.
5. Observe the behavior.

**[Expected result]:**
- No buttons are focused.

**[Actual result]:**
- The "Not Now" button remains focused, and the focus cannot be dismissed.

**[Regression]**
- This issue is not reproducible with Firefox Beta 121.0b4. Using mozregression tools we have found the following:
-Last good revision: 413cc418d2da5d2e324b2c5081e11214ac50f3fd
-First bad revision: 5a9dc4e73f4690603070bfeefb4eac9b5260bbb7
-Pushlog: [Link](https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=413cc418d2da5d2e324b2c5081e11214ac50f3fd&tochange=5a9dc4e73f4690603070bfeefb4eac9b5260bbb7)

Based on this pushlog it seems that Bug 1866069 introduced this issue.

**[Notes]:**
- The following error is displayed after reaching the "Not Now" button:
  - handleEvent resource:///modules/UrlbarInput.sys.mjs:553               UrlbarController.sys.mjs:691:19
TypeError: element is null19 UrlbarSearchOneOffs.sys.mjs:194:39
- The issue is NOT reproducible for the Opt-In section displayed at the top.
- THe issue is still reproducible even after the Opt-In section is dismissed. You need to restart the browser in order to lose focus.
- Attached is a screen recording of the issue.
Bug: [Firefox Suggest Contextual Opt-in][macOS] The title and the text description from the Opt-In UI cannot be accessed by a screen reader software on macOS
Status: ASSIGNED
Priority: P2
Created: 2023-11-29 15:38:59+00:00
Resolved: 2023-12-15 21:28:58+00:00

**[Affected versions]:**
- Firefox Beta 121.0b1 - Build ID: 20231120154937
- Firefox Nightly 122.0a1 - Build ID: 20231122095244

**[Affected Platforms]:**
- macOS 13.1

[Prerequisites]:
- Have a Screen Reader software installed and enabled (I have used VoiceOver on macOS).
- Have a Firefox profile with the following prefs in the "about:config" page:
browser.urlbar.quicksuggest.contextualOptIn set to true
browser.search.region set to US

**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Open a New Tab and click the "Address Bar".
3. Navigate through the "Address Bar" dropdown and observe the behavior.

**[Expected result]:**
- All the elements from the "Opt-In" section are successfully recognized by the screen reader software.

**[Actual result]:**
- Only the buttons and the "Learn more" hyperlink from the "Opt-In" section are recognized by the screen reader software.

**[Notes]:**
- This issue is reproducible regardless if the "Opt-In" section is displayed at the top or at the bottom of the "Address Bar" doorhanger.
This issue is not reproducible on Windows 10 x64 with the built-in screen reader (Narrator) and also on Linux using Orca. All the elements are correctly recognized by the screen reader.
Bug: Intermittent TV browser/components/urlbar/tests/unit/test_richsuggestions_order.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: FIXED
Created: 2023-11-29 16:41:16+00:00
Resolved: 2023-12-04 06:57:56+00:00

**Filed by:** ctuns [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=438170102&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Nb96_uiKTn29U1OWscvUKg/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/Nb96_uiKTn29U1OWscvUKg/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

---
```
[task 2023-11-29T16:25:50.266Z] 16:25:50     INFO -  TEST-PASS | browser/components/urlbar/tests/unit/test_richsuggestions_order.js | took 12585ms
[task 2023-11-29T16:25:50.275Z] 16:25:50     INFO -  TEST-START | browser/components/urlbar/tests/unit/test_richsuggestions_order.js
[task 2023-11-29T16:26:02.288Z] 16:26:02  WARNING -  TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/unit/test_richsuggestions_order.js | xpcshell return code: 0
[task 2023-11-29T16:26:02.288Z] 16:26:02     INFO -  TEST-INFO took 12013ms
[task 2023-11-29T16:26:02.288Z] 16:26:02     INFO -  >>>>>>>
[task 2023-11-29T16:26:02.289Z] 16:26:02     INFO -  PID 5370 | *** You are running in chaos test mode. See ChaosMode.h. ***
[task 2023-11-29T16:26:02.289Z] 16:26:02     INFO -  PID 5370 | [Parent 5370, Main Thread] WARNING: Couldn't get the user appdata directory. Crash events may not be produced.: file /builds/worker/checkouts/gecko/toolkit/crashreporter/nsExceptionHandler.cpp:2886
[task 2023-11-29T16:26:02.289Z] 16:26:02     INFO -  (xpcshell/head.js) | test MAIN run_test pending (1)
[task 2023-11-29T16:26:02.289Z] 16:26:02     INFO -  (xpcshell/head.js) | test run_next_test 0 pending (2)
[task 2023-11-29T16:26:02.289Z] 16:26:02     INFO -  (xpcshell/head.js) | test MAIN run_test finished (2)
[task 2023-11-29T16:26:02.290Z] 16:26:02     INFO -  running event loop
[task 2023-11-29T16:26:02.290Z] 16:26:02     INFO -  browser/components/urlbar/tests/unit/test_richsuggestions_order.js | Starting setup
[task 2023-11-29T16:26:02.290Z] 16:26:02     INFO -  (xpcshell/head.js) | test pending (2)
[task 2023-11-29T16:26:02.290Z] 16:26:02     INFO -  (xpcshell/head.js) | test run_next_test 0 finished (2)
[task 2023-11-29T16:26:02.291Z] 16:26:02     INFO -  PID 5370 | [WARN  rkv::backend::impl_safe::environment] `load_ratio()` is irrelevant for this storage backend.
[task 2023-11-29T16:26:02.291Z] 16:26:02     INFO -  "Extension attached"
[task 2023-11-29T16:26:02.291Z] 16:26:02     INFO -  TEST-PASS | browser/components/urlbar/tests/unit/test_richsuggestions_order.js |  - Search provider extension should be running - "running" == "running"
```
Bug: The @name mention feature in O365 stopped working since last week
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2023-11-29 17:40:51+00:00
Resolved: 2024-02-16 14:58:06+00:00

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

Steps to reproduce:

In Office365, when using the @name for comment feedback, I encounter an error "can't search right now".


Actual results:

Cannot share comments


Expected results:

The person who's name is listed will get an email to review.
Bug: Update Shopping Sidebar default width to use pixel value
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2023-11-29 17:57:32+00:00
Resolved: 2023-12-06 10:48:10+00:00

Scope of this bug is to update shopping sidebar default width to 320px instead of 26.67em

See https://bugzilla.mozilla.org/show_bug.cgi?id=1865351#c19
Bug: Tab tearing now requires a delay to tear
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-11-29 20:41:33+00:00
Resolved: 2023-12-12 15:36:45+00:00

Having this same issue, exactly as described, that doesn't seem to have ever been fixed.

+++ This bug was initially created as a clone of Bug #1714815 +++

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

Steps to reproduce:

Quickly drag a tab away from the toolbar to tear off a tab to a new window.


Actual results:

The tab is just focused.


Expected results:

A new window is opened with the dragged tab as the only tab.
Bug: Investigate how a FXVIEW-CATEGORY-BUTTON in the Firefox View tests needs to be updated to pass a11y_checks
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2023-11-29 21:18:45+00:00
Resolved: 2024-02-01 00:18:44+00:00

In the Firefox View side navigation component, the `<fxview-category-button>` elements with `role="tab"` include `<button aria-hidden="true" tabindex="-1">` which are ultimately receiving clicks from the mochitests. This hacky markup is providing as-expected behavior for the end users who are interacting with tabs within a tablist - as expected.

But on the markup side, this implementation uses those inaccessible (via `aria-hidden`) buttons, which causes the a11y-checks failures and would likely cause automatic HTML tests to flag this approach too, because it is not an expected pattern and, in general, we do not want this to be reused in any other component.

Since it is working, we would likely not need to re-markup the entire component _in this specific case_, but we would need to add comments in the test files, describing that this is a one-off instance and to `setEnv` to tell Tier 2 a11y-checks that as well.
Bug: menubar color is off in inactive windows with browser.theme.windows.accent-color-in-tabs.enabled
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2023-11-29 21:56:04+00:00
Resolved: 2023-12-20 08:13:31+00:00

1. When accent color on title bars is enabled, the inactive title bar background becomes light gray for almost all apps that respect accent colors. There's a good reason for this, the accent colored title bar means foreground and stands out much better against light gray background windows. Fx and Chrome are exceptions to this rule. Both use a lighter shade of the accent color for background windows. This is worse than the windows default. When the goal is to clearly differentiate foreground from background, higher contrast (blue vs light gray) is better that low contrast (darker blue vs lighter blue). Fx should stop copying Chrome and go with the more sensible windows default.
2. When the menu bar is shown, the inactive title bar buttons are almost invisible. The menu text is better but still could use improvement.
Bug: Bookmark tab... | Add bookmark | Location extremely slow (reloads all bookmarks every time?)
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2023-11-30 10:02:35+00:00
Resolved: 2023-12-03 18:27:05+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) Have lots of bookmarks, or you won't notice it (I have more than 300k)
2) Right-click a tab
3) In the pop-up menu, click "Bookmark tab..."
4) In the "Add bookmark" dialog, under "Location", click "Choose"
5) Watch Firefox become unresponsive and your hard drive activity spike for (in my case) almost a minute
6) Close the "Add bookmark" dialog, go back to step (2) and do it again. Same thing again, no matter how often you do it.




Actual results:

Firefox becomes unresponsive and hard drive activity spikes, apparently reloading the entire bookmark database every time.

Profiler data:
https://share.firefox.dev/47WZIk0


Expected results:

Until yesterday's update, selecting a bookmark location in "Bookmark tab..." only took a few seconds at most. That was acceptable.
Bug: When using the text tool, the initial positioning should be lower than it is now
Status: NEW
Priority: P3
Created: 2023-11-30 12:21:03+00:00
Resolved: 2024-03-15 12:50:15+00:00

STR:
1.  Open a PDF.
2. Use the text tool.
3. Click somewhere.

=> notice that the edit box is slightly too high. The reason is that the cursor's hotspot is at the top left, but it looks like it's centered left. So as a user I expect that the vertical center of the edit box is at the position of the vertical center of my mouse cursor, but instead the vertical center of the edit box is at the position of the top left of the mouse cursor.
Bug: "Always ask you where to save files" doesn't work on some sites
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-11-30 12:43:56+00:00
Resolved: 2023-11-30 13:20:00+00:00

Despite the fact my Firefox has the "Always ask you where to save files" option enabled, for some time (at least a few months) on many sites this is not respected and the file is saved to Downloads and immediately opened. One example is Gmail; this happens when I try to save a PDF attachment.

This doesn't happen in Safari or Chrome.

I'm using macOS Sonoma 14.1.1 (23B81) on a MacBook Pro with the M2 Pro chip.
Bug: Translation popup shows even in kiosk mode
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2023-11-30 13:16:13+00:00
Resolved: 2024-01-19 17:02:23+00:00

Steps to reproduce:

I would like to run Firefox in kiosk mode, and give the user an uninterrupted view of the website I'm displaying. As such, I would like to hide all popups/dialogs.

As a test, you can run this command: `firefox --new-instance --kiosk 'https://www.vrt.be/vrtnws/nl/' -P kiosk`.


Actual results:

When visiting a page in a different language than the system language (the example above is Dutch), Firefox will ask to translate the page with a popup that obscures part of the page.


Expected results:

Firefox does not offer to translate and shows the webpage without any popups or dialogs.

I realize I can set `browser.translations.automaticallyPopup` to `false` but I expect Firefox to respect kiosk mode and not show any popup.
Bug: Firefox certificate viewer unable to parse altNames in digital certificate
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2023-11-30 16:40:37+00:00
Resolved: 2024-12-17 08:14:47+00:00

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

Steps to reproduce:

1.Mutating a certificate.
2.Running the browser to parse the mutated certificate file.
3.Observing the results.


Actual results:

Firefox unable to parse altNames in digital certificate.
Firefox's certificate viewer does not display altNames.
However, Chrome can parse and display it, which causes a difference.


Expected results:

Firefox can parse the altNames in digital certificates correctly.
Bug: Firefox beta 121.0b4 deleted my default profile out of nowhere, I lost all my extensions, settings, history, cookies, everything..
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2023-11-30 16:51:12+00:00
Resolved: 2024-02-13 13:14:09+00:00

Steps to reproduce:

I opened up firefox as usual, and was greeted with the welcome screen (which is weird considering I didn't do a fresh install or anything like that). 


Actual results:

I was shocked and weirded out, so I visited about:profiles to see that for some reason a new profile was created. I was like "okay?" and then I saw that my usual regular profile that I had been using everyday was still there, I clicked on "open this profile in a new window" and boom, I was devastated to see that my usual profile too had reported back to me the fresh install screen (aka welcome to firefox). 


Expected results:

When I searched for firefox from my search, and opened it up, I should've been greeted by nothing else apart from my home screen that had greeted me in my default profile.
Bug: Clicking outside a PDF's page no longer commits drawings
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2023-11-30 16:59:52+00:00
Resolved: 2024-02-16 14:33:22+00:00

Steps to reproduce the problem:
1. Draw something on top of a page
2. Click outside the page to commit the drawing

Before bug 1866850, clicking outside the page committed the drawing.
Bug: Sometimes when switching tabs it crashes and you need to restart the program to continue switching tabs
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2023-11-30 20:33:58+00:00
Resolved: 2023-11-30 20:38:18+00:00

Steps to reproduce:

I don’t know the exact recipe for reproduction. Sometimes happened when switching between program windows


Actual results:

There was a freeze and then the tabs did not switch correctly. When I tried to switch, the new tab was displayed with glitches. This was temporarily corrected if you clicked on the program icon in the program panel, but when switching to another tab, the incorrect display occurred again. The only thing that helped was restarting the program.


Expected results:

No freezing and correct operation of tab switching
Bug: Restoring focus to toolbarbuttons when screenshots UI exits doesnt work
Status: NEW
Priority: P2
Created: 2023-12-01 00:05:20+00:00
Resolved: 2024-10-24 01:12:45+00:00

In bug 1820015 we implement a "restore focus to previous element" function which attempts to put focus back where it was before you opened the screenshots UI. This was modeled from similar behavior in [panel.js](https://searchfox.org/mozilla-central/rev/d84469b005106c5ab0f65e283f71c1415ce76c54/toolkit/content/widgets/panel.js#231-284) This works fine for some elements like `<browser>`, `<tab>`s, and the address bar. But does not work for any of the `<toolbarbutton>`s. Neither `element.focus()` or `Services.focus.setFocus(element, FLAGS)` result in the element receiving focus.
Bug: The new webcompat reporter tool dialog is not being read out by NVDA, when it is opened
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-12-01 00:16:44+00:00
Resolved: 2024-01-05 13:07:13+00:00

**Tested platforms**
* Affected platforms: Windows 10/11 + NVDA; 
* Unaffected platforms: ?

**Steps to reproduce**
1. Launch NVDA, then Firefox
2. Make sure new webcopmpat feature is enabled:
ui.new-webcompat-reporter.enabled  = true
3. Load any webpage
4. Navigate to the MenuBar/Help/Report broken site or Url bar/Tracking protection/Report broken site
5. (while the Bug #1866519 is being resolved, it is appropriate to press `Tab` key once to move the focus within the dialog)

**Expected result**
* When focus is moved into the tool dialog, the role (dialog) and accessible name (the on-screen title) are announced by the NVDA and right after that the screen reader proceeds with reading out the entire content of the dialog (so the user is aware what is included in the newly opened panel)
* then the focused element is announced by NVDA
* The user could navigate the dialog's controls while pressing `Tab`  or the full content while pressing `Down/Up` arrows

**Actual result**
* When focus is moved into the tool dialog, only the focused element and the title of the dialog with the footer buttons are being announced, the form (in the middle of the panel) are not announced
* User could navigate by pressing `Tab` (when focused the form, `up/down` arrows won't move back to the title or down to the footer controls) , but arrows would only read the top and the bottom of the content
Bug: Direct opening of PDF attachments broken
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2023-12-01 12:18:49+00:00
Resolved: 2023-12-07 14:49:11+00:00

Please note that this regression doesn't mean a total loss of functionality, a PDF attachment will just fallback to trigger the (browser) save-dialog rather than being opened in a new tab.

This broke in https://github.com/mozilla/pdf.js/pull/17060, and is being fixed in https://github.com/mozilla/pdf.js/pull/17363.
Bug: Translation does not translate article title
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2023-12-01 13:54:04+00:00
Resolved: 2023-12-13 13:44:38+00:00

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

Steps to reproduce:

Open the following webpage
https://www.bild.de/news/inland/news-inland/nostradamus-dunkle-vorhersagen-fuer-2024-neuer-europa-herrscher-ki-und-china-86251498.bild.html

And click on Translate icon in address bar.
Dialogue appears and you hit Translate button.


Actual results:

The article is translated. The article title is now. It is removed.


Expected results:

The article title must be translated. The article title must not be deleted.
Bug: PDF files from local ZIP(jar:file://...) should be shown successfully
Status: UNCONFIRMED
Priority: --
Created: 2023-12-02 02:03:40+00:00
Resolved: 2024-02-13 14:05:15+00:00

Steps to reproduce:

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

open attached sample in FF using 'jar:file://...' hyperlink, navigate 'index.htm'

on the page click PNG and PDF links.


Actual results:

PDFs are not shown. link navigation within tab stucks instead and the tab must be closed/reopened to continue with hyperlinks.

from another side, PNG link works as expected. the PDFs can be successfully downloaded('Save link as') or when ZIP is unpacked, successfully navigated and rendered.


Expected results:

clicking PDF link should successfully render (available) PDF document from local ZIP or report correct error message(e.g. when the file isn't available or damaged or so) and never stuck.