av9ash/GitBugs huggingface dataset:
Bug: [Hero Layout] Small cards domain has line-height of 20px
Status: NEW
Priority: P3
Created: 2020-05-06 12:41:21+00:00
Resolved: 2024-03-04 12:18:40+00:00

**[Affected versions]:**
- Firefox Beta 77.0a1 Build ID 20200505174119;

**[Affected Platforms]:**
- Windows 10;
- Mac OS 10.14;
- Ubuntu 18.04 x64;

**[Prerequisites]:**
- Have a Firefox Beta 77 build installed;
- Have a new profile created;
- Have the following prefs set in about:config
--Browser.search.region to “US”
--Browser.newtabpage.activity-stream.discoverystream.spocs-endpoint to https://spocs.getpocket.com/spocs?country=US&region=US-CA 
--Browser.newtabpage.activity-stream.discoverystream.config to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":true,"layout_endpoint":"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=hero-layout","unused_key":"unused_2"}

**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Open about:newtab page.
3. Tap “F12” key to open the browser Inspector.
4. Observe the line-height of cards domain.

**[Expected result]:**
Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1628045#c6 line-height in small cards should be 19px. 

**[Actual result]:**
Line-height for small cards domain is 20px.
Bug: [Hero Layout] Small cards have different heights as expected, at 696px/936px width containers, when sponsored label is displayed on 1 and 2 lines
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-05-06 13:01:26+00:00
Resolved: 2020-06-11 19:32:01+00:00

**[Affected versions]:**
- Firefox Beta 77.0a1 Build ID 20200505174119;

**[Affected Platforms]:**
- Windows 10;
- Mac OS 10.14;
- Ubuntu 18.04 x64;

**[Prerequisites]:**
- Have a Firefox Beta 77 build installed;
- Have a new profile created;
- Have the following prefs set in about:config
-- Browser.search.region to “US”
-- Browser.newtabpage.activity-stream.discoverystream.spocs-endpoint to https://spocs.getpocket.com/spocs?country=US&region=US-CA 
-- Browser.newtabpage.activity-stream.discoverystream.config to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":true,"layout_endpoint":"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=hero-layout","unused_key":"unused_2"}

**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Open about:newtab page.
3. Tap “F12” key to open the browser Inspector.
4.     
 a. Have the **696px-width container** visible and: 
-- observe small cards height when the sponsored label is on 1 row (title on 2 rows)
-- observe small cards height when the sponsored label is on 2 rows (title on 2 rows)
 b. Have the **936px-width container** visible and :
-- observe small cards height when the sponsored label is on 1 row (title on 2 rows)
-- observe small cards height when the sponsored label is on 2 rows (title on 2 rows)

**[Expected result]:**
Based on the [specs] (https://www.figma.com/file/3c4TF1eRf8y2DhwySP4lkA/Firefox-77-Spec?node-id=0%3A1 ) 
- 696px-width container
-> sponsored label is on 1 row (title on 2 rows) => card height is 194px
-> sponsored label is on 2 rows (title on 2 rows) =>card height is 212px
- 936px-width container
-> sponsored label is on 1 row (title on 2 rows) => card height is 222px
-> sponsored label is on 2 rows (title on 2 rows) =>card height is 240px

**[Actual result]:**
- 696px-width container
-> sponsored label is on 1 row (title on 2 rows) => card height is 185px
-> sponsored label is on 2 rows (title on 2 rows) => card height is 204px
- 936px-width container
-> sponsored label is on 1 row (title on 2 rows) => card height is 222px
-> sponsored label is on 2 rows (title on 2 rows) => card height is 234px

**[Notes]:**
This issue generates different values, than those from specs, for Hero card height for both cases: 
- we expect a increase of the Hero card height of **15px** for 936px-width container and the real value is 12px;
- we expect a increase of the Hero card height of **18px** for 639px-width container and the real value is 19px;
Bug: Open tabs lose container association on restart
Status: UNCONFIRMED
Priority: --
Created: 2020-05-06 13:39:52+00:00
Resolved: 2024-02-27 17:45:07+00:00

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

Steps to reproduce:

- Create a container
- Open various tabs in that container
- Quit the browser without closing the tabs or hiding the container
- Restart the browser



Actual results:

- The tabs are still present, but they are *not* associated with any container.
- I haven't seen this happen with closed containers (i.e. closed containers keep their tabs).


Expected results:

The tabs should have retained their association with the container.
Bug: [Hero Layout] Padding (height) for Hero card is 12px instead of 16px
Status: RESOLVED
Priority: P3
Resolution: WONTFIX
Created: 2020-05-06 14:09:28+00:00
Resolved: 2023-04-28 13:39:32+00:00

**[Affected versions]:**
- Firefox Beta 77.0a1 Build ID 20200505174119;

**[Affected Platforms]:**
- Windows 10;
- Mac OS 10.14;
- Ubuntu 18.04 x64;

**[Prerequisites]:**
- Have a Firefox Beta 77 build installed;
- Have a new profile created;
- Have the following prefs set in about:config
--Browser.search.region to “US”
--Browser.newtabpage.activity-stream.discoverystream.spocs-endpoint to https://spocs.getpocket.com/spocs?country=US&region=US-CA 
--Browser.newtabpage.activity-stream.discoverystream.config to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":true,"layout_endpoint":"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=hero-layout","unused_key":"unused_2"}

**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Open about:newtab page.
3. Tap “F12” key to open the browser Inspector.
4. Observe the padding for the Hero card.

**[Expected result]:**
- Hero card padding is 16px/16px.

**[Actual result]:**
- Hero card padding is 16px/12px.
Bug: Separate startpage locking from homepage locking
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2020-05-06 16:11:31+00:00
Resolved: 2020-05-13 21:49:54+00:00

Currently because of the way browser.startup.page is set, if you lock the homepage so users can't change it, it also means they can't turn restore previous session on/off.

In policy, we should make it possible to lock the homepage but still allow the user to turn restore previous session on/off.
Bug: Unable to type into address bar when Firefox starts
Status: UNCONFIRMED
Priority: P3
Created: 2020-05-06 16:58:20+00:00
Resolved: 2025-02-28 01:45:46+00:00

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

Steps to reproduce:

I do not know what happened to get Firefox into this state, but I have pinned down the exact line in my profile state that causes it.


Actual results:

Upon opening Firefox, I was unable to type into the address bar. The address bar became focussed (blue border), but pressing keys did not cause characters to appear. I am on macOS 10.15.3.

Reinstalling Firefox did not fix the issue, but deleting my profile folder did, at the cost of removing all my data and customisations.

If anyone else is having this issue, deleting the file "xulstore.json" file in the profile is sufficient to fix the issue without losing any important data - just some information on window sizes.

I was able to pinpoint the single line within the file that causes the issue. My file is attached. Editing line 118 of this file to change "fullscreen" to "" was sufficient to fix the issue for me.


Expected results:

Firefox should not be able to get into this state.
Bug: since the last update my laptop keeps crashing when i have more than 3 tabs open, its happening about every 2 to 3 hrs now
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2020-05-06 17:28:01+00:00
Resolved: 2020-05-25 09:42:54+00:00

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:76.0) Gecko/20100101 Firefox/76.0

Steps to reproduce:

restart


Actual results:

restarted untill a started opening tabs and new windows


Expected results:

it never crashed thats for sure, it worked perfect without any crashes
Bug: 2 step verification codes doesnt work
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2020-05-06 17:32:08+00:00
Resolved: 2020-05-26 13:00:02+00:00

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

Steps to reproduce:

I set up 2 step verification with google authenticator


Actual results:

When i try to login into my account on new device, and enter the verification code google authenticator generates, it never accepts it


Expected results:

it should let me in my account
Bug: Firefox will not sync on my Mac
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2020-05-06 18:18:09+00:00
Resolved: 2020-05-07 22:27:45+00:00

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

Steps to reproduce:

Initiated 'Sync Now' command.  Have tried to delete & re-install Firefox on Mac, to no avail.


Actual results:

Nothing


Expected results:

Open Tabs, Bookmarks and Extensions should have synced with my W10 Desktop,  W10 Lenovo Laptop & my Linux Desktop.
Bug: Bookmark manager need to delete twice to remove entry
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2020-05-06 18:19:19+00:00
Resolved: 2022-02-23 07:40:22+00:00

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

Steps to reproduce:

1. Menu bar -> Bookmarks -> Show All Bookmarks
2. Select entry or entries in the right panel
3. Right click to bring up context menu, click "Delete"



Actual results:

The deleted bookmark show up again in half a second.

Delete again and they are gone.


Expected results:

Delete once and not show up by itself.
Bug: Keyboard focus can be broken with arrow-key navigation to search engines.
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-05-06 19:14:55+00:00
Resolved: 2020-05-06 19:38:17+00:00

STRs are: New tab, type "somestring" into the awesomebar, then down-arrow until you are highlighting one of your search engine options. Then, click on the "somestring" with the mouse. With the cursor caret flashing wherever you clicked it, try navigating with your arrow keys. Result is, you aren't moving the cursor around, you're still moving the highlit selection around, not the cursor as you'd expect. You can triple-click the "somestring" to get back to being able to type into the awesomebar, but I don't think I can navigate that with the arrow keys. 

I'm on current nightly, current Win10. I'm not sure if this has accessibility implications, but it might. I can reproduce at will.
Bug: Google Meet Grid View has vanished as an extension.
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2020-05-06 19:31:06+00:00
Resolved: 2020-06-18 05:09:27+00:00

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

Steps to reproduce:

Tried to add Google Meet Grid extension onto a new computer. It is on all of my other synced devices. 

Tried looking for extension, and received message that link could not be found.

Tried sending link from a computer that has the extension to the new computer, and got the same message.


Actual results:

No attempts to search for the link were fruitful.

Trying to send a copy of the link from the existing extension on a computer that has the link led me to the same message - the link does not exist.


Expected results:

I want the grid button to sow on my google meet events
Bug: Switching urlbar text direction and then back causes the domain to be de-emphasized, and with always a fading out effect
Status: NEW
Priority: P3
Created: 2020-05-06 21:26:44+00:00
Resolved: 2024-05-27 15:36:10+00:00

STR:
1. Latest Nightly, Windows 10
2. Set `intl.uidirection` to `1` and restart
3. Open any url
4. Focus the urlbar and switch text direction to the left (via LeftCtrl+LeftShift)
5. Switch text direction back to the right (RightCtrl+RightShift)
6. Unfocus the urlbar

AR:
The domain text is de-emphasized (i.e. all of the url is the same color), and the url is with a fading out effect even if the url does not overflow the urlbar.
AKAICT only restart fixes this.

ER:
Domain text should be empasized and without fading out effect when not needed.

Note that this can also be reproduced in LTR UI if on step 4 you switch text direction to the right and unfocus.
Bug: Intermittent browser/components/sessionstore/test/<test>.js | application crashed [@ nsContentSecurityUtils::AssertAboutPageHasCSP]
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2020-05-06 22:55:13+00:00
Resolved: 2024-10-09 12:03:51+00:00

**Filed by:** dkeeler [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=301083368&repo=try
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/RUUxCK0dRV6SuvOUNmkqWw/runs/0/artifacts/public/logs/live_backing.log

---
Bug: Blue border inside of search bar
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2020-05-07 05:03:25+00:00
Resolved: 2020-05-12 02:43:50+00:00

Steps to reproduce:

1. Enable search bar.
2. Focus search bar

What happens:

Blue box/border appears inside of search box.

Expected result:

Prior to regression.

12:52.46 INFO: No more inbound revisions, bisection finished.
12:52.46 INFO: Last good revision: 842955b61f01c2d859484ae9aa155e4ea59561b5
12:52.46 INFO: First bad revision: 0010e22f0dafa5d3f8b7fe095dd0ca51b745d38b
12:52.46 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=842955b61f01c2d859484ae9aa155e4ea59561b5&tochange=0010e22f0dafa5d3f8b7fe095dd0ca51b745d38b
Bug: Some users are confused about which password/PIN to enter in the OS re-auth dialog from about:logins
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2020-05-07 06:26:53+00:00
Resolved: 2021-01-31 13:53:16+00:00

Some users think it's asking for a Firefox Account (FxA) password and others don't know what PIN Windows is asking for. There aren't that many SUMO complaints yet so it's hard to know how widespread this is from that data alone. It's also possible this issue is more of a problem on Windows since the string is different/better on macOS.

Some SUMO questions: https://support.mozilla.org/en-US/questions/firefox?owner=all&tagged=passwords-os-auth&show=all

We are also seeing over 25% of user who have been prompted who haven't succeeded to authenticate yet.

Current strings for Windows: https://searchfox.org/mozilla-central/rev/dc4560dcaafd79375b9411fdbbaaebb0a59a93ac/browser/locales/en-US/browser/aboutLogins.ftl#111-112,117-118,123-124

```
# This message can be seen by attempting to edit a login in about:logins
about-logins-edit-login-os-auth-dialog-message = Verify your identity to edit the saved login.
…
# This message can be seen by attempting to reveal a password in about:logins
about-logins-reveal-password-os-auth-dialog-message = Verify your identity to reveal the saved password.
…
# This message can be seen by attempting to copy a password in about:logins
about-logins-copy-password-os-auth-dialog-message = Verify your identity to copy the saved password.
```

The new strings ideally shouldn't specify that a "password" is required since the default mode of the dialog may be for one of the other Windows Hello authentication methods such as the fingerprint reader, PIN, facial recognition, etc.

Perhaps this is worth uplifting a hard-coded new unlocalized en-US string though I don't know what our locale breakdown is.
Bug: Favicons may be incorrect for some search engines when the specified locale is different to the Firefox locale
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2020-05-07 07:25:54+00:00
Resolved: 2020-05-12 14:22:13+00:00

In the search service we override which locale is loaded for an add-on and use the manifest for the locale we want. This lets us be more flexible around how search engines are deployed.

In Yandex's case (I think the only case) we have two engine icons, one for the en engine, one for ru.

When the locale is different from the in-use locale, we're picking up the default icon `yandex-en.ico` rather than `yandex-ru.ico`.

I think this only affects a single Yandex distribution (yandex-uk). Petrua reported this in bug 1635154 comment 6.
Bug: Many sync pings are missing device IDs
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2020-05-07 08:43:31+00:00
Resolved: 2020-05-11 09:10:21+00:00

I've many sync pings for my personal account which have, say:

```
"devices": [
    {
      "id": "00000000000000000000000000000000",
      "type": "desktop",
      "os": "Darwin",
      "version": "77.0a1"
    },
    {
      "id": "00000000000000000000000000000000",
      "type": "desktop"
    }
  ],
...
"uid": "2b...",
```

The ping reports a sync did happen (so we should have a token) and given we report the uid, we should be able to report the device IDs.

This is true for all recent pings, then they start appearing (on May 2). Without digging deeper and without real evidence, I'm suspecting bug 1604844
Bug: skip plugin installation permission
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-05-07 09:43:05+00:00
Resolved: 2020-05-08 21:37:00+00:00

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

Steps to reproduce:

In Firefox ESR 68.7 version
1) User permissions to install plugins have been blocked
Via: I apply the false variable to the xpinstall.enabled rule and block it
It is verified that it is not allowed to install plugins.
2) Sync of Firefox is started, and plugins are automatically installed despite being blocked, by this any user can install plugins despite being blocked this option


Actual results:

Plugins can be installed, despite being restricted


Expected results:

That no plugins were installed
Bug: React slider component interacting with other slider components - on firefox desktop in firefox mobile view.
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2020-05-07 09:57:40+00:00
Resolved: 2020-06-02 17:50:22+00:00

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

Steps to reproduce:

After loading https://material-ui.com/components/slider/ in mobile view (and select any phone) and clicking around randomly slider interact with each other as if they would be one single component. This is only happening on firefox desktop in mobile view (ctrl+shift+m) but not on the actual firefox mobile app on our smartphones. Also, this is not only happening on their website, but on others too.


Actual results:

Slider components are interacting with each other in a way as if they would be the same component (their values are all the same and when moving one of the sliders' thumb, all other slider thumbs are moving too).


Expected results:

Slider components should not be interacting with each other and moving one slider thumb should not affect any other slider components.
Bug: Clicking URL bar does not automatically copy
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2020-05-07 11:21:50+00:00
Resolved: 2020-05-15 13:02:35+00:00

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

Steps to reproduce:

Clicking the URL bar on Fedora 32.


Actual results:

The URL gets selected but not copied to the clipboard.

I believe that this started happening in Firefox 75, after upgrading to Fedora 32.


Expected results:

Clicking on the URL bar should select and copy the URL to the clipboard.
Bug: A pinned Top Site is wrongly unpinned if the “Delete from History” option is selected
Status: NEW
Priority: P5
Created: 2020-05-07 12:05:29+00:00
Resolved: 2021-07-02 13:41:01+00:00

**[Notes]:**
- A user might expect “Delete from History” to only delete the Top Site from History and not overwrite their previously made choices/changes like pinning or title/url editing.

**[Affected Versions]:**
- Firefox Nightly 78.0a1 (Build ID: 20200506215114)
- Firefox Beta 77.0b2 (Build ID: 20200505174119)
- Firefox Release 76.0 (Build ID: 20200429185419)
- Firefox Release 75.0 (Build ID: 20200403170909)

**[Affected Platforms]:**
- Windows 10 (x64)
- macOS 10.15
- Ubuntu 18.04 (x64)

**[Prerequisites]:**
- Have a newly created Firefox profile.

**[Steps to reproduce]:**
1. Start the Firefox Browser with the profile from prerequisites and open a new tab.
2. Hover the “reddit” top site and click the (...) context menu.
3. Select the “Pin” option from the context menu.
4. Click the “reddit” top site and restart the browser.
5. Open a new tab and hover the “reddit” top site.
6. Select the “Delete from History” option.
7. Restart the browser and observe the state of the “reddit” top site.

**[Expected results]:**
- The “reddit” top site is pinned.

**[Actual results]:**
- The “reddit” top site is unpinned.

**[Additional Notes]:**
- Attached is a recording of the issue.
Bug: nightly uses 170% cpu, 5x power
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2020-05-07 14:11:19+00:00
Resolved: 2020-06-02 17:49:23+00:00

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

Steps to reproduce:

Updated nightly. Relaunched nightly.


Actual results:

Power consumption increased five-fold for idling Nightly. CPU usage increased to 175%.


Expected results:

Same or less power consumption
Bug: Intermittent browser/base/content/test/general/browser_bug495058.js | about:sessionrestore: uri loaded in detached tab - "about:blank" == "about:sessionrestore" - JS frame :: chrome://mochitests/content/browser/browser/base/content/test/general/browser
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2020-05-07 16:57:34+00:00
Resolved: 2020-07-21 17:02:56+00:00

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

---

task 2020-05-07T15:50:05.186Z] 15:50:05     INFO - TEST-PASS | browser/base/content/test/general/browser_bug495058.js | about:blank: placeholder text is present - "Search with Google or enter address" == true - 
[task 2020-05-07T15:50:05.186Z] 15:50:05     INFO - Buffered messages finished
[task 2020-05-07T15:50:05.187Z] 15:50:05     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/general/browser_bug495058.js | about:sessionrestore: uri loaded in detached tab - "about:blank" == "about:sessionrestore" - JS frame :: chrome://mochitests/content/browser/browser/base/content/test/general/browser_bug495058.js :: <TOP_LEVEL> :: line 32
[task 2020-05-07T15:50:05.187Z] 15:50:05     INFO - Stack trace:
[task 2020-05-07T15:50:05.188Z] 15:50:05     INFO - chrome://mochitests/content/browser/browser/base/content/test/general/browser_bug495058.js:null:32
[task 2020-05-07T15:50:05.189Z] 15:50:05     INFO - chrome://mochikit/content/browser-test.js:Tester_execTest/<:1055
[task 2020-05-07T15:50:05.190Z] 15:50:05     INFO - chrome://mochikit/content/browser-test.js:Tester_execTest:1095
[task 2020-05-07T15:50:05.190Z] 15:50:05     INFO - chrome://mochikit/content/browser-test.js:nextTest/<:918