av9ash/GitBugs huggingface dataset:
Bug: "Manage extensions" button changes color when right-clicked, in unified extensions menu
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-10-10 23:53:06+00:00
Resolved: 2022-10-12 19:07:32+00:00

STR:
1. Set `about:config` pref `extensions.unifiedExtensions.enabled` to `true` and restart Firefox.
2. Install some extension, e.g. this one:
https://addons.mozilla.org/en-US/firefox/addon/multi-account-containers/
3. Click the Unified Extensions button to open its menu.
[EDIT: adding some additional steps here per comment 3]
4. Press Tab to cycle through the menu items until "Manage extensions" gains focus, and then press Tab again so that it loses focus.
5. (optional) close and reopen the menu.
6. Right-click the "Manage extensions" button at the bottom of the menu.

ACTUAL RESULTS:
The button changes color to indicate that it was clicked, but it doesn't otherwise behave as if it were clicked (i.e. nothing happens).

EXPECTED RESULTS:
No color change.

~If you compare to the very-similar UX for "Manage bookmarks" and "Manage history" (at the bottom of the Hamburger Menu's Bookmarks & History submenus), there is no color-change when you right-click these "Manage..." buttons.  Same goes for the "History" Toolbar menu item. So this is something specific to this Unified Extensions Menu's "Manage" button which is inconsistent with our other similar UX.~
[UPDATE: this was from me not recognizing that I had done STR step 4 for the extensions menu.  If I do that step for the History toolbar menu item, for an apples-to-apples comparison, then indeed I can repro this there as well.]
Bug: With Dark Mode, websites are dark but tabs and Awesome Bar are light.
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2022-10-11 02:11:03+00:00
Resolved: 2023-01-18 17:29:28+00:00

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

Steps to reproduce:

Opened Firefox after booting into Windows.

I also tried setting Firefox to Light Mode and back to Dark Mode.


Actual results:

The Awesome bar and tab bar were light themed.


Expected results:

The Awesome Bar and tabs should follow the theme set, in this case; Dark Mode.
Bug: nsCookieBannerService.cpp:137:7: error: ‘NS_NewRunnableFunction’ was not declared in this scope
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2022-10-11 07:18:01+00:00
Resolved: 2022-10-12 09:52:58+00:00

Steps to reproduce:

Solaris build fails with:
```
20:06.24 /builds/psumbera/mozilla-central-build/toolkit/components/cookiebanners/nsCookieBannerService.cpp: In member function ‘nsresult mozilla::nsCookieBannerService::Init()’:
20:06.24 /builds/psumbera/mozilla-central-build/toolkit/components/cookiebanners/nsCookieBannerService.cpp:137:7: error: ‘NS_NewRunnableFunction’ was not declared in this scope
20:06.24   137 |       NS_NewRunnableFunction("CookieBannerListService init startup",
20:06.24       |       ^~~~~~~~~~~~~~~~~~~~~~
20:06.24 /builds/psumbera/mozilla-central-build/toolkit/components/cookiebanners/nsCookieBannerService.cpp:139:27: error: ‘Idle’ is not a member of ‘mozilla::EventQueuePriority’
20:06.24   139 |       EventQueuePriority::Idle);
20:06.24       |                           ^~~~
20:06.30 /builds/psumbera/mozilla-central-build/toolkit/components/cookiebanners/nsCookieBannerService.cpp:136:17: error: ‘NS_DispatchToCurrentThreadQueue’ was not declared in this scope
20:06.30   136 |   nsresult rv = NS_DispatchToCurrentThreadQueue(
20:06.30       |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
The first bad revision is:
changeset:   637340:de07e2b641d8
user:        Paul Zuehlcke <pbz@mozilla.com>
date:        Mon Oct 10 08:00:26 2022 -0700
description:
	Bug 1784868 - Defer CookiebannerListService init to prevent early main-thread IO. r=timhuang

	Differential Revision: https://phabricator.services.mozilla.com/D158941
Bug: [Experiment] The “Sign in” button from “about:welcome” is the wrong color in the Control branch of the MR experiment
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-10-11 12:08:49+00:00
Resolved: 2022-10-12 16:39:38+00:00

**[Affected Versions]:**
- Firefox RC 106.0 (Build ID: 20221010110315)

**[Affected Platforms]:**
- Windows 10x64
- macOS 11.6.6
- Linux Mint 20.2

**[Prerequisites]:**
- Have a new profile created but not opened yet.
- Have this [user.js file](https://drive.google.com/file/d/1QiB8fip9xK_IbASaUsTn5CxHewpeMafd/view?usp=sharing) copied to the Profile Folder.
- Have a system theme that will have Firefox use the Light theme by default.

**[Steps to reproduce]:**
1. Open the profile from prerequisites using the -p –first-startup syntax.
2. Observe the “Sign in” secondary button from the first “about:welcome” page.

**[Expected result]:**
- The secondary button is white.

**[Actual result]:**
- The secondary button uses the colors of buttons - dark blue for the light theme and light blue for dark theme.

**[Regression Window]:**
Last good revision: b1c9c49674265306fdd706306472fb32a3555eb3
First bad revision: f25371470479192740e16f8b1f8dd385353c9776
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b1c9c49674265306fdd706306472fb32a3555eb3&tochange=f25371470479192740e16f8b1f8dd385353c9776

**[Notes]:**
- Attached is a recording of the issue.
- The issue is also reproducible if the old onboarding is forced using the `browser.aboutwelcome.templateMR` set to `false`.
- The issue is NOT reproducible on Firefox Release 105.0.2 (Build ID: 20221003135607).
Bug: Twitter Bring tab to front when opening links
Status: UNCONFIRMED
Priority: --
Created: 2022-10-11 17:24:20+00:00
Resolved: 2022-10-14 10:07:37+00:00

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

Steps to reproduce:

Opening my twitter home page, I click with the middle mouse wheel on a tweet, the tweet opens in a new tab and automatically (although I set it to off "Bring tab to front when opening links, images or content media in a new tab ") is moved to the new tab.


Actual results:

I am taken to the new tab I opened earlier. - Bring tab to front when opening links in a new tab.


Expected results:

I should stay on the main twitter page, deciding when to open the tabs clicked previously (with the middle wheel mouse)
Bug: The MR onboarding split screen's main section is missing a shadow
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2022-10-11 19:37:41+00:00
Resolved: 2022-11-24 10:07:07+00:00

The main content section in MR onboarding screens doesn't have a shadow, which looks a little funky since the secondary section does have one. Especially in the responsive layout, where the main section is several times larger than the secondary section. I added a screenshot with the contrast enhanced to make it more noticeable.

That might have been done to prevent the main section's shadow casting on the secondary section, since it's not easy to cast a single shadow for the whole screen without changing the DOM. But we could also prevent that by using `clip-path` to clip the shadow on the adjacent edges.

Another approach would be to add a `::before` pseudo-element on the screen with the dimensions of both sections combined, and cast the shadow from there instead. Something kind of like the `#urlbar-background` in the browser chrome.
Bug: When using the text tool in pdf.js the cursor switches to a pointer after making the first text box
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2022-10-12 00:58:17+00:00
Resolved: 2022-10-19 18:15:11+00:00

Steps to reproduce the problem:
1. Choose the text annotation tool on PDF
2. Create a text box
3. Mouse cursor switches to a regular pointer instead of a caret which makes placing subsequent text boxes in the right location difficult.
Bug: Save Page As not saving displayed page
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-10-12 04:08:07+00:00
Resolved: 2022-11-11 13:05:38+00:00

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

Steps to reproduce:

Save Page As


Actual results:

Firefox seems to go download the page


Expected results:

It should save the currently displayed page.
Why? Because the page could have changed. Reddit, for example, constantly has pages being modified and such. If I load a page, keep it open in the browser, then the page is changed, I click save page as and save it I get the new updated page and not what I'm seeing visually. I can't recover what I'm seeing and don't even know that I'm downloading the updated page.

This is not the behavior that one should have for Save Page As. It should save what one see's and expects. If one wants the current page one can refresh then save page as immediately afterwards.

The method means that if a page is changed external to the browser it will save that change even if, say, the page is deleted... one will download the error message rather than what firefox contains within the browser which may be more useful.
Bug: Autoplay settings text for allowed or blocked status overflows due to narrow column width
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2022-10-12 07:39:13+00:00
Resolved: 2023-11-27 13:12:23+00:00

**Found in**
* 107.0a1 (20221011160345)

**Affected versions**
* 107.0a1 (20221011160345)
* 106.0 (20221010110315) - the text is displayed properly because of bug 1793558 but shortening the Status box will cause the text to be clipped
* 105.0.3 (20221007134813) - the text is displayed properly because of bug 1793558 but shortening the Status box will cause the text to be clipped





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


**Steps to reproduce**
1. Open https://strifer.link/html-video-autoplay-test/.
2. Change the status to Allow or Block Audio and viddeo from the URL bar.
3. Open about:preferences#privacy > Autoplay and observe the status text.

**Expected result**
* The text has the correct font size and the entire text is displayed after bug 1793558 is fixed.

**Actual result**
*  The text is bigger and after bug 1793558  is fixed the text is clipped.


**Regression range**
* Last good revision: 5d4ec1262b2e579217133d276309e6ccdce1c28a
17:58.41 INFO: First bad revision: b2bdddc979f368917b07162504961bc5690fff8a
17:58.41 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=5d4ec1262b2e579217133d276309e6ccdce1c28a&tochange=b2bdddc979f368917b07162504961bc5690fff8a 
Potential regressor: bug 1784488.
I will set bug 1784488 as a regressor because increasing the text size will display a clipped text after fixing bug 1793558.


**Additional notes**
* Attached a screenshot with the issue.
* `Allow Audio and Video` and `Block Audio and Video` options are cut of even if the dropdown is opened.
Bug: Save Changes and Cancel buttons are slightly clipped for the Autoplay Permissions
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2022-10-12 08:17:07+00:00
Resolved: 2022-11-02 22:44:08+00:00

**Found in**
* 107.0a1 (20221011160345)

**Affected versions**
* 107.0a1 (20221011160345)
* 106.0 (20221010110315)
* 105.0.3 (20221007134813) 





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


**Steps to reproduce**
1. Open about:preferences#privacy and click on Setting for Autoplay from the Permissions area.
2. Observe the `Cancel` and `Save Changes` buttons.


**Expected result**
* The buttons are displayed as expected.

**Actual result**
*  The buttons are slightly cut off on the bottom side.


**Regression range**
* Last good revision: 5d4ec1262b2e579217133d276309e6ccdce1c28a
17:58.41 INFO: First bad revision: b2bdddc979f368917b07162504961bc5690fff8a
17:58.41 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=5d4ec1262b2e579217133d276309e6ccdce1c28a&tochange=b2bdddc979f368917b07162504961bc5690fff8a 
Potential regressor: bug 1784488. 

**Additional notes**
* Attached a screenshot with the issue.
Bug: Missing padding for the elements inside autoplay notification panel
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2022-10-12 09:07:03+00:00
Resolved: 2022-10-26 00:38:46+00:00

**Found in**
* Latest Nightly 107.0a1

**Affected versions**
* Nightly 107.0a1
* Firefox 106.0 RC
* Firefox 105.0.3 RC

**Tested platforms**
* Affected platforms: Windows 10, Windows 11
* Unaffected platforms: macOS 11.6 and Ubuntu 18.04

**Steps to reproduce**
1. Visit https://strifer.link/html-video-autoplay-test/
2. Click the autoplay permission notification from the URL bar
3. Click the dropdown inside the permission notification

**Expected result**
* The items inside the dropdown are displayed correctly and in a visually pleasant way.

**Actual result**
* The items inside the dropdown have almost no padding on the right side compared to the left side.

**Regression range**
* First bad: 561ed5ccdd2400934cb05151dbf8dbe105bfc963
* Last good: 64212702d9f0d6410362b209dcf0348cb3acb452
* Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=64212702d9f0d6410362b209dcf0348cb3acb452&tochange=561ed5ccdd2400934cb05151dbf8dbe105bfc963
* Potentially regressed by: I suspect that fixing bug 1729854 caused this but I might be wrong.

**Additional notes**
* On macOS and Ubuntu this is not an issue, only on Windows.
* Some other notification with the same dropdown could be affected, not sure which other notifications have a similar dropdown as autoplay though, I tried some other ones that I know like mic, webcam, geolocation etc but they don't have the same structure.
Bug: [macOS] Firefox is not recognized as a recommended app to launch PDF files
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-10-12 10:35:15+00:00
Resolved: 2022-12-07 20:35:27+00:00

**Found in**
- Firefox 106.0

**Affected versions**
- Firefox 106.0
- Firefox 107.0a1

**Tested platforms**
- Affected platforms: macOS 13
- Unaffected platforms: Windows 11, Ubuntu 22.04

**Steps to reproduce**
1. Install firefox as .pkg
2. Right click any PDF file and select Open With -> Other
3. Search for Firefox in the list

**Expected result**
- Firefox is seen as a Recommended PDF app like Safari or Chrome

**Actual result**
- Firefox can't be selected

**Regression range**
- Will see for a regression

**Additional notes**
- The issue can be seen in the following [attachment](https://drive.google.com/file/d/1fS-rlnUqExlChj6pK8fy_frTTpy6Qo6f/view?usp=sharing)
- By selecting "All applications" from the Enable settingand choosing Firefox the following message will be shown "It's not known if this applicatioon can open the PDF file".
Bug: When using Max/Min tool to start bookmark toolbar Firefox hangs eventually
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2022-10-12 14:42:26+00:00
Resolved: 2022-11-28 16:39:46+00:00

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

Steps to reproduce:

Open firefox.  Bookmark toolbar does not appear automatically.  Go up to where minimize,  Expand, Close tools are and hit expand.  Page refreshes and bookmark toolbar appears.  At some point, the Firefox will hang and need Task Manager to close.  


Actual results:

Can move main page up and down and videos or info on open tabs continue but can't do anything with the tabs, close, open new video, go to new page.


Expected results:

Firefox doesn't freeze when bookmark toolbar page is opened.  Or page with bookmark toolbar should open when first started.   Hanging has become a big issue
Bug: Dropdown menu from button Options in notification banner does not show correctly
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2022-10-12 15:03:29+00:00
Resolved: 2022-12-19 10:54:43+00:00

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

## Steps to reproduce
1. In a new profile, install Firefox Translations.
2. Go to a page that can be translated to trigger the notification banner. E.g. https://es.wikipedia.org/wiki/Wikipedia:Portada.
3. Click `Options` on the banner.
4. Observe the dropdown menu.

## Actual result
Last item is overlapped by a down chevron scroll button. Hovering on the button does not scroll down enough to show all the text.

## Expected result
There is no need for the scroll button.

## Regression
Last good Nightly: 2022-09-01
First bad Nightly: 2022-09-02
pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=136f13b75057ef4c2419dba0d63e913d502c7458&tochange=050487abb54ae6d2c7d6a78b5de60ac6efbab9ba

Bisecting autoland builds:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=33a3e6eafcdb8acb7ccf6f8d2372a1a566a6b2dc&tochange=3477776b80ac0035ec6b285b21931b06261bae15

This should be regressed by bug 1734220.

## Notes
I don't know if bug 1788595 or https://github.com/mozilla/firefox-translations/issues/496 would fix this bug.

There is another unrelated bug regarding button `Translate this tab automatically as you browse` which I filed bug 1794817.
Bug: Colorways Reminder Feature Callout message impression being reset, causing message to reappear (not respecting lifetime of 1)
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-10-12 17:33:41+00:00
Resolved: 2022-10-31 13:47:46+00:00

Users occasionally see a repeat of the colorways reminder feature callout after dismissing it, even though the lifetime of the message is set to 1.
Bug: Menu items in toolbar panels start blinking when you right-click them, **only after** they've been tabbed across
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-10-12 17:45:10+00:00
Resolved: 2025-02-16 06:19:52+00:00

(not entirely sure whether this is a DOM focus-handling bug, vs. a frontend bug, vs. a style system bug, vs. something else.  Starting off in Toolbars&Customization, and CC'ing some folks who might have thoughts)

STR:
1. Use "Customize Toolbar" to place the History menu-button (looks like a little clock) on your toolbar.

2. Click the History icon on your toolbar (the one you just placed) to open its menu, and mouse over the bottom option, called "Manage History". Right click it and verify that there's no visual effect from that right-click action.

3. Now, with the menu still open, press "Tab" to cycle through that menu's options. Make sure that "Tab" traverses across that final "Manage History" option (though you can leave it focusing some other menu item).

4. Close and reopen the menu (e.g. by clicking elsewhere and clicking the toolbar icon again.)

4. Once again, mouse over "Manage HIstory" and right-click. What happens?

EXPECTED RESULTS:
No visual change for the right-click action, just as in step 2.

ACTUAL RESULTS:
The menu item flashes (showing its `:active` styling I think), just as it would if I left-clicked it.

It seems that tabbing across this menu item causes some persistent change that makes it flash its active style when right-clicked, despite the fact that the right-click action doesn't actually activate it in any way.
Bug: Server not found page suggests connecting to the page I tried to connect to.
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-10-12 19:22:10+00:00
Resolved: 2022-10-12 19:41:48+00:00

I had some temporary network issue, I think a DNS issue, and the error page presented was a little confusing saying "We can’t connect to the server at www.speedtest.net. Did you mean to go to www.speedtest.net?" The latter address was a link to the exact page that I was trying to load.

Eemeli, since bug 1734217 transitioned netError to fluent recently I'm wondering if this issue was introduced there?
Bug: Intermittent browser/base/content/test/general/browser_domFullscreen_fullscreenMode.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2022-10-12 19:41:34+00:00
Resolved: 2022-11-08 17:03:09+00:00

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

---
```
[task 2022-10-12T18:01:27.320Z] 18:01:27     INFO - TEST-PASS | browser/base/content/test/general/browser_domFullscreen_fullscreenMode.js | The fullscreen state of the chrome should match - 
[task 2022-10-12T18:01:27.321Z] 18:01:27     INFO - > Enter DOM fullscreen in fullscreen mode
[task 2022-10-12T18:01:27.322Z] 18:01:27     INFO - Buffered messages finished
[task 2022-10-12T18:01:27.323Z] 18:01:27     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/general/browser_domFullscreen_fullscreenMode.js | Test timed out - 
[task 2022-10-12T18:01:27.324Z] 18:01:27     INFO - GECKO(2267) | JavaScript error: resource:///actors/DOMFullscreenParent.jsm, line 206: Error: TelemetryStopwatch: key "FULLSCREEN_CHANGE_MS" was already initialized
[task 2022-10-12T18:01:27.325Z] 18:01:27     INFO - Console message: [JavaScript Error: "Error: TelemetryStopwatch: key "FULLSCREEN_CHANGE_MS" was already initialized" {file: "resource:///actors/DOMFullscreenParent.jsm" line: 206}]
[task 2022-10-12T18:01:27.326Z] 18:01:27     INFO - handleEvent@resource:///actors/DOMFullscreenParent.jsm:206:28
[task 2022-10-12T18:01:27.327Z] 18:01:27     INFO - 
[task 2022-10-12T18:01:27.327Z] 18:01:27     INFO - GECKO(2267) | MEMORY STAT | vsize 12184MB | residentFast 796MB | heapAllocated 449MB
[task 2022-10-12T18:01:27.328Z] 18:01:27     INFO - TEST-OK | browser/base/content/test/general/browser_domFullscreen_fullscreenMode.js | took 90281ms
```