av9ash/GitBugs huggingface dataset:
Bug: VoiceOver will not read the Extension notifications from Hamburger menu
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2021-04-06 19:34:14+00:00
Resolved: 2021-06-03 10:26:29+00:00

**Affected platforms**:
Platforms: macOS 11 Big Sur

**Preconditions**:
Reach about:config and set browser.proton.enabled = true
Install version 1.35.2 of Bitwarden – Free Password manager
Have a Voice order enabled

**Steps to reproduce**:
1. With Firefox Browser open wait for the add-on to automatically attempt to update itself. 
2. Check the add-on update banners in the Hamburger Menu.
3. Move the mouse cursor on top of the Notification and highlight the notification banner.

**Expected Result**:
Voice order is able to read the notification banner without issues.

**Actual Result**:
Voice order is unable to read the notification banner without issues.
Bug: Failure in browser/components/extensions/test/browser/browser_ext_menus.js with proton urlbar
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2021-04-06 21:29:49+00:00
Resolved: 2021-04-09 09:35:05+00:00

Graduating the urlbar causes a failure in browser/components/extensions/test/browser/browser_ext_menus.js, probably due to the fact page action extensions are now pinned?
Bug: Failure in browser/components/extensions/test/browser/browser_ext_pageAction_click_types.js with proton urlbar
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2021-04-06 21:31:51+00:00
Resolved: 2021-04-09 09:35:08+00:00

browser/components/extensions/test/browser/browser_ext_pageAction_click_types.js is failing with proton urlbar, probably due to the fact page actions are now pinned?
Bug: Failure in toolkit/components/extensions/test/browser/browser_ext_themes_autocomplete_popup.js with proton urlbar
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2021-04-06 21:37:34+00:00
Resolved: 2021-04-09 09:35:12+00:00

There's a failure in toolkit/components/extensions/test/browser/browser_ext_themes_autocomplete_popup.js when graduating the proton urlbar
Bug: Failure in browser/components/urlbar/tests/browser/browser_autocomplete_a11y_label.js with proton urlbar
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2021-04-06 21:39:14+00:00
Resolved: 2021-04-08 14:48:28+00:00

There's a failure in browser/components/urlbar/tests/browser/browser_autocomplete_a11y_label.js when graduating the proton urlbar.
Bug: Failure in browser/components/urlbar/tests/browser/browser_searchMode_no_results.js with proton urlbar
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2021-04-06 21:40:46+00:00
Resolved: 2021-04-08 09:58:22+00:00

There's a failure in browser/components/urlbar/tests/browser/browser_searchMode_no_results.js when graduating the proton urlbar
Bug: Failure in browser/components/urlbar/tests/browser/browser_view_resultTypes_display.js with proton urlbar
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2021-04-06 21:41:40+00:00
Resolved: 2021-04-08 14:48:28+00:00

There's a failure in browser/components/urlbar/tests/browser/browser_view_resultTypes_display.js when graduating the proton urlbar
Bug: Failures in browser/modules/test/browser/browser_PageActions.js with proton urlbar
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2021-04-06 21:44:13+00:00
Resolved: 2021-04-09 09:35:15+00:00

There's failures in browser/modules/test/browser/browser_PageActions.js when graduating the proton urlbar
Bug: Failure in browser/modules/test/browser/browser_PageActions_contextMenus.js with proton urlbar
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2021-04-06 21:45:04+00:00
Resolved: 2021-04-09 09:35:18+00:00

There's failures in browser/modules/test/browser/browser_PageActions_contextMenus.js when graduating the proton urlbar
Bug: Failure in browser/modules/test/browser/browser_PageActions_newWindow.js with proton urlbar
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2021-04-06 21:45:47+00:00
Resolved: 2021-04-09 09:35:20+00:00

There's failures in browser/modules/test/browser/browser_PageActions_newWindow.js when graduating the proton urlbar
Bug: Failure in browser/modules/test/browser/browser_UsageTelemetry_interaction.js with proton urlbar
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2021-04-06 21:48:11+00:00
Resolved: 2021-04-08 09:58:24+00:00

There's failures in browser/modules/test/browser/browser_UsageTelemetry_interaction.js when graduating the proton urlbar. Likely due to page actions no more existing or not in the meatball menu.
Bug: Failure in browser/components/uitour/test/browser_UITour4.js with proton urlbar
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2021-04-06 21:51:47+00:00
Resolved: 2021-04-24 23:27:35+00:00

There's failures in browser/components/uitour/test/browser_UITour4.js when graduating the proton urlbar.
Bug: Failure in browser/base/content/test/performance/browser_urlbar_keyed_search.js  with proton urlbar
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2021-04-06 21:52:46+00:00
Resolved: 2021-04-09 09:35:27+00:00

There's failures in browser/base/content/test/performance/browser_urlbar_keyed_search.js  when graduating the proton urlbar.
Bug: Failure in browser/base/content/test/performance/browser_urlbar_search.js with proton urlbar
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2021-04-06 21:53:40+00:00
Resolved: 2021-04-11 09:28:24+00:00

There's a failure in browser/base/content/test/performance/browser_urlbar_search.js when graduating the proton urlbar.
Bug: Hide spell check items in the context menu for login username fields (and disable spellcheck?)
Status: NEW
Priority: P2
Created: 2021-04-06 22:12:30+00:00
Resolved: 2021-04-09 14:53:44+00:00

A bit like bug 1692330, but now for spell check. When login fields are set up as `type=email`, we don't offer spell check options, but some login fields allow inputting a username (e.g. reddit, github) and we have a "check spelling" item and/or spellcheck suggestions if there's content.

This seems odd; login username fields aren't likely to benefit from spellcheck. Jared, do you know if there's a particular reason not to just hide all this UI and disable spellcheck in the field?
Bug: browser/base/content/test/performance/browser_appmenu.js fails under proton
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2021-04-06 22:39:46+00:00
Resolved: 2021-04-07 21:33:22+00:00

```
[task 2021-04-06T21:15:14.972Z] 21:15:14     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/performance/browser_appmenu.js | unexpected reflow at collectItems@resource:///modules/PanelMultiView.jsm hit 1 times
[task 2021-04-06T21:15:14.972Z] 21:15:14     INFO - Stack:
[task 2021-04-06T21:15:14.972Z] 21:15:14     INFO -   collectItems@resource:///modules/PanelMultiView.jsm:1509:30
[task 2021-04-06T21:15:14.973Z] 21:15:14     INFO -   descriptionHeightWorkaround@resource:///modules/PanelMultiView.jsm:1527:7
[task 2021-04-06T21:15:14.973Z] 21:15:14     INFO -   handleEvent@resource:///modules/PanelMultiView.jsm:1258:23
```


I'm 99% sure this is because we added wrapping to the sync item in the app menu in bug 1698062. Wrapping items cause us to hit descriptionheightworkaround code, which causes sync layout flushes.

I'm not sure what we want to do here. Mike/Emma, thoughts? We can add an exception but that is kind of sad because adding sync layout flushes is bad...
Bug: "Forget about this site" function uses all system RAM
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2021-04-06 22:46:41+00:00
Resolved: 2021-11-17 12:42:24+00:00

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

Steps to reproduce:

Used "Forget about this site" function in the history sidebar on a very commonly browsed domain such as gitHub.com or duckduckgo.com

I ran into this a bit earlier and commented in https://bugzilla.mozilla.org/show_bug.cgi?id=903777#c23 but I believe it is better as a separate issue.


Actual results:

Firefox uses around 200-300% CPU and uses consumes around +100MB/s of RAM for a few minutes it the system runs out of memory. For me this is 11GB of RAM.

Before the test Firefox was using 800MB of RAM (2 idle tabs and 1 new-page tab) and the system froze at 8.1GB of RAM (see picture).

I imagine it would finish if I had enough RAM (not sure how much it needs) because it is able to complete the function for sites that I visit less frequently. I use GitHub for work so I imagine there are hundreds of thousands of history items in there...


Expected results:

It shouldn't crash the computer and shouldn't use so much RAM.
Bug: Tab text looks blurry when moving to another monitor with different resolution
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2021-04-07 04:49:41+00:00
Resolved: 2021-04-07 19:30:39+00:00

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

Steps to reproduce:

I have dual monitor setup. Laptop display (1920 x 1080 scaling 125%) , and another external monitor display (1920 x 1080 scaling 100%). When I start Firefox it's on my laptop display (125% scaling), and then when I move it to external monitor display, I see text in Tabs (heading of website, or header) is blurry. It's not that much, as you can't read, but it's definitely correct display. I have tried doing same in with Chrome, latest Edge browser, and I don't see this problem there.


Actual results:

Text on tab heads looks blurry on second monitor with different scaling. If you see both pics, you would see the difference. The "NotBlurry.PNG" one is showing more robust and smooth fonts in the tabs, while in case of "BlurryTabs.PNG" fonts are not that robust and smooth.
Symptoms could vary more when resolution of monitor also different may be.
Bug: about:logins - Browser search highlight ignores default section text
Status: RESOLVED
Priority: P5
Resolution: INVALID
Created: 2021-04-07 05:43:49+00:00
Resolved: 2022-12-19 05:31:39+00:00

**Affected versions**
* 86.0.1, 89.0a1(2021-04-05);

**Affected platforms**
* Win 7;
* will confirm with other OSs when possible;

**Steps to reproduce**
1. Launch Firefox, access about:logins
2. Press the CTRL+F keys to trigger the search;
3. Type "log" inside the search input;
4. Enable the Highlight ALL option;
5. Press the Find Next occurrence button;

**Expected result**
* highlight applied on all occurrences;

**Actual result**
* left-section occurrences are not highlighted;

**Regression range**
* will check when time permits it;

**Additional notes**
* attached screenshot to illustrate the issue.
Bug: Fix some theme issues after bug 1701448
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2021-04-07 07:24:08+00:00
Resolved: 2021-04-08 12:41:06+00:00

* Actions menu icons can be too large (on Windows for instance)
* panel list font on Windows is inconsistent in add-ons manager and about:logins
Bug: Site permission panel is missing a number of Proton styles
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2021-04-07 08:50:27+00:00
Resolved: 2021-05-10 07:42:07+00:00

**Affected versions**
* Firefox 89.0a1

**Affected platforms**
* Windows 10 x64
* Ubuntu 18.04 x64
* macOS 10.15

**Precondition**
The following prefs are set to true in about:config:
- browser.proton.enabled
- browser.proton.doorhangers.enabled (for preliminary testing this also required, until the work is moved to the main pref)

**Steps to reproduce**
1. Go to https://permission.site/.
2. Click on the "Location" button.
3. Click on the "Allow" button.
4. Click on the site permission icon.

**Expected result**
* There is no arrow before "Last access..."
* The "Last access..." string is smaller than the "Access your location" string.
* The Allowed/Blocked string is inside a grey rectangle.  

**Actual result**
* There is an arrow before "Last access..."
* The "Last access..." string is too big.
* The Allowed/Blocked string is not inside a grey rectangle. 

**Regression range**
* This is not a regression. 

**Additional notes**
* Please look at the attached image. This is the one from the specs.
Bug: Checkboxes and radio buttons from about preferences are cut out while the browser window is resized
Status: NEW
Priority: P3
Created: 2021-04-07 09:53:23+00:00
Resolved: 2024-01-18 10:27:51+00:00

**Affected versions**
* 89.0a1 (20210406152948)
* 88.0b8 

**Affected platforms**
* Windows10x64
* macOS 11
* macOS 10.15.7
* Ubuntu 20.04

**Steps to reproduce**
1. Launch FF 
2. Go to about preferences
3. Resize the window lesser than half of screen
4. Navigate the options using TAB key form the keyboard

**Expected result**
* Navigating the options from the about:preferences section using the TAB key from the keyboard , while the browser's window is resized , should render no issues  with checkboxes and radio buttons.

**Actual result**
* Navigating the options from the about:preferences section using Tab key from the keyboard , while the browser's window is resized , will render all the checkboxes and the radio buttons to be cut out.

**Suggested Severity**
*  I would suggest an S3 for this issue, as resizing the browser window can be encountered numerous times in regular user usage, while multitasking.

**Notes**
* This issue occurs for Light, Dark and Alpenglow themes.
* This issue is not Proton specific, however it would greatly improve the overall aesthetics of the feature.
Bug: Remove sync layout flush for hamburger menu opening with proton
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2021-04-07 10:08:17+00:00
Resolved: 2021-05-22 05:36:39+00:00

As discussed in bug 1703405, this is a result of the sync item now potentially wrapping and the `descriptionHeightWorkaround` code running for it. Some options we could investigate to fix it:

1. if we know the width available for the text beforehand (which I think we do, because the width of the panel is fixed?), ensure it is set directly on the element to ensure the XUL code for the preferred height of the element gets it right first time.
2. switch the element in question to an HTML equivalent that wraps (possibly combined with (1)) and ensure we don't hit it in the descriptionHeightWorkAround code.
3. switch everything in the main view to non-XUL flexbox and see if that helps.
Bug: Perma browser/base/content/test/sync/browser_contextmenu_sendpage.js | Ids in context menu match expected values when Gecko 89 merges to Beta on 2021-04-19
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2021-04-07 11:13:20+00:00
Resolved: 2021-04-08 15:10:54+00:00

* [central-as-beta simulation](https://treeherder.mozilla.org/jobs?repo=try&group_state=expanded&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel%2Crunnable&revision=06348556fe158efad7514661e358e326a24fbdb1&selectedTaskRun=YytfCWryR7qfkmfFtYY3aQ.0)
* [How to run these simulations](https://wiki.mozilla.org/Sheriffing/How_To/Beta_simulations#TRUNK_AS_EARLY_BETA)
* [Failure log](https://treeherder.mozilla.org/logviewer?job_id=335686117&repo=try)

TEST-UNEXPECTED-FAIL | browser/base/content/test/sync/browser_contextmenu_sendpage.js | Ids in context menu match expected values -

This code got added in bug 1702980.

Please also update the check to use `equal` and also specify an identifying message of the failed check (the elements which don't match will already get logged with this) for easy identification of the issue, see [this code](https://searchfox.org/mozilla-central/rev/be413c29deeb86be6cdac22445e0d0b035cb9e04/testing/modules/Assert.jsm#263-276).
Bug: pop out player resizing creates black borders
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2021-04-07 11:40:42+00:00
Resolved: 2021-04-08 13:58:06+00:00

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

Steps to reproduce:

1. pop out a video
2. resize the pop out so it becomes really small 
3. resize the pop out back to a normal size


Actual results:

when the pop out player is resized back to a normal size it will have black borders to the side of it


Expected results:

it should just resize to it's normal size without the black borders attached
Bug: First unselected tab after tab strip scroll button exceeded the frame and a line separator is displayed
Status: RESOLVED
Priority: P2
Resolution: INVALID
Created: 2021-04-07 13:17:31+00:00
Resolved: 2021-04-13 02:17:17+00:00

### Preconditions
In about:config set:
browser.proton.enabled = true

### Affected versions
Firefox 89.0a1 

### Affected platforms
Windows 10 x64
Windows 7 x64
macOS 10.15
Ubuntu 20.04

### Steps to reproduce
1. Open Firefox.
2. Open many tabs till tab strip scroll buttons appear.
3. observe the first unselected tab after or before any of the scroll buttons.

### Expected result
- A line is separating the first unselected tab from the strip scroll button.
- First letter from the first unselected tab exceeded the frame. 

### Actual Result
- The line shouldn't be displayed which separates the first unselected tab from the strip scroll button.
- First letter from the first unselected tab shouldn't exceeded the frame.
Bug: [Win10] White line on top of the browser while using dark theme and browser is unfocussed
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2021-04-07 13:33:25+00:00
Resolved: 2021-04-16 13:56:05+00:00

This was opened on request on [bug 1700873 comment 20](https://bugzilla.mozilla.org/show_bug.cgi?id=1700873#c20)

*Affected versions*
* 88.0b8 (20210406185740)

*Affected platforms*
* Windows 10x64




*Steps to reproduce*
1. Open Firefox and select the dark theme.
2. Unfocus the browser and observe the top part.




*Expected result*
* Browser is displayed as expected.

*Actual result*
* White line is displayed while unfocused, grey line while focused.

*Regression range*
* Pushlog from bug 1700873: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b3fd546349160dfa293982cace9ba0f289d7788f&tochange=e5ee2e40acc0271d1e6032ab7e6058469cd7eef9


*Notes*
* Attached a screen recording.
* Also a grey line can be seen when the browser is focused too.
* Firefox Nightly it seems to be fixed see bug's 1700873 [comment 13](https://bugzilla.mozilla.org/show_bug.cgi?id=1700873#c13) for more details.
Bug: xlsx and xls file changing to pdf extention
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2021-04-07 14:14:22+00:00
Resolved: 2021-04-27 14:09:48+00:00

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

Steps to reproduce:

I am trying to download a files from browser which have xlsx or xls extention.

Which is returning a excel blob data with - 

content-disposition: form-data; name="Content-Disposition"; filename="Party wise sample count Date-wise.xlsx"
content-type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet



Actual results:

Mozilla is appending pdf extention to the file.


Expected results:

Extention should not have changed.
Bug: Hovering the "X blocked" in the protections panel doesn't activate hover state on the "Protections Dashboard" menuitem
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2021-04-07 15:01:54+00:00
Resolved: 2021-04-15 04:20:15+00:00

STR:
1. In this bugzilla page, open the Protections panel
2. Hover the "Protections Dashboard" text itself => hover state active
3. On the same menuitem, hover the "X block" text => no hover state
Bug: The buttons in the "Report a Broken Site" UI in the protections panel are styled incorrectly
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2021-04-07 15:16:39+00:00
Resolved: 2021-04-17 09:53:00+00:00

Also resetting the margin-inline of the URL field to 0 could be nice, to make it flush with the rest of the elements.
Bug: The icons are missing from FxA  notifications for  Finish Account Setup / You've been disconnected
Status: NEW
Priority: P2
Created: 2021-04-07 15:16:42+00:00
Resolved: 2021-05-06 11:07:04+00:00

**Affected platforms**:
Platforms: macOS 11 - Big Sur

**Preconditions**:
Reach about:config and set browser.proton.enabled = true

**Step to reproduce**:
1. Launch the Firefox Browser and Create a new account without verifying it.
2. Reach the FxA Notification from the Hamburger menu and from the User Account option.
3. Restart the Browser and reach the FxA Notification from the Hamburger menu and from the User Account option.
4. Login to FxA with a valid account and reach the FxA Notification from the Hamburger menu and from the User Account options.

*Expected result**:
The correct icons should be displayed for FxA create without finish,  FxA disconnected and  login a valid FxA .

**Actual result**:
There are no icons displayed for FxA create without finish,  FxA disconnected and FxA login with a valid account.
Bug: FxA toolbar monogram avatar is barely visible while using the browser light theme
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2021-04-07 15:19:41+00:00
Resolved: 2021-04-12 14:58:51+00:00

#### Tested with:

Release 87
Beta 88.0b8
Nightly 89.0a1 (2021-04-07)
#### Tested on:

Windows 10

#### Preconditions:
Set up the following prefs in about:config:
- identity.fxaccounts.autoconfig.uri to https://accounts.stage.mozaws.net
- browser.newtabpage.activity-stream.fxaccounts.endpoint to https://accounts.stage.mozaws.net
-identity.fxaccounts.auth.uri to https://api-accounts.stage.mozaws.net/v1
-identity.fxaccounts.remote.oauth.uri to https://oauth.stage.mozaws.net/v1
-identity.fxaccounts.remote.profile.uri to https://profile.stage.mozaws.net/v1
-identity.fxaccounts.remote.root to https://accounts.stage.mozaws.net/
-identity.sync.tokenserver.uri to https://token.stage.mozaws.net/1.0/sync/1.5

#### Steps:

  1. Launch firefox and sign in to FxA.
  2. Change the browser theme to Light.
  3. Click on the FxA toolbar avatar.

#### Actual result:

The FxA toolbar monogram avatar is barely visible while browser light theme is applied (see the video recording attached).
#### Expected result:
The FxA toolbar monogram avatar should remains visible.

Note 1: This is not reproducible with context-fill enabled.
Note 2: This is not reproducible in Release 87.
Bug: Proton: Custom theme missing border and search suggestion/oneoffs separator.
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2021-04-07 15:24:58+00:00
Resolved: 2021-04-27 19:53:14+00:00

**Affected versions**

Firefox 88 beta 8
Nightly 89.0a1  

**Affected platforms**

Win 7 64-bit, Mac 10.14, Ubuntu 20. windows 10 64bit

**Preconditions**
user.js with
  user_pref("browser.proton.enabled", true);
  user_pref("browser.proton.toolbar.enabled", true);
  user_pref("browser.proton.urlbar.enabled", true);


**Steps to reproduce**

1.launch firefox
2.install "black matte red" theme  https://addons.mozilla.org/en-US/firefox/addon/matte-black-red/
3.type something in url bar

**Expected result**
 
there should be a horizontal line above one offs, and below search suggestions

**Actual result**
I dont see any line, the line is visible with proton off. 
 

Notes: this issue is also found on Alpenglow theme too
Bug: Missing proton-styled outlines on some elements in the protections panel, when tabbing to them
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2021-04-07 15:27:08+00:00
Resolved: 2022-04-01 12:57:19+00:00

On Windows, currently tabbing to the following elements displays a dotted outline instead of the protonized outline:
1. Info icon (i) at the top of the panel
2. "More info" text when expanding the info icon
3. "Site fixed? Send report" when disabling ETP on the page
4. ETP toggle

On Windows the dotted outline is because of:
https://searchfox.org/mozilla-central/rev/be413c29deeb86be6cdac22445e0d0b035cb9e04/toolkit/themes/windows/global/toolbarbutton.css#29
Removing it doesn't have to happen in this bug imo because it's more of a global thing that can affect other UIs, so it can be addressed in a different bug.