av9ash/GitBugs huggingface dataset:
Bug: Google maps share location after blocking it
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-09-14 15:35:32+00:00
Resolved: 2020-09-17 15:51:48+00:00

**Suggested severity**
* S3

**Affected versions**
* 80.0
* 81.0b9
* 82.0a1 (2020-09-14)

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

**Steps to reproduce**
1. Launch Firefox.
2. Go to https://www.google.ro/maps
3. Share location and check the “Remember this decision”
4. Go to about:preferences#privacy
5. From the Permissions section click on the Location “Settings…” button
6. Block the location share and save changes.
7. Go back to https://www.google.ro/maps and try share again the location

**Expected result**
* The message "Google Maps does not have permission to use your location." is displayed at the bottom of the page.

**Actual result**
*  The location is shared again

**Regression range**
* This is not a recent regression since I can reproduce it on Firefox 80.0. I’ll try to find the regression range asap.

**Additional notes**
* If you don’t refresh the page after blocking location from permissions the message is displayed and the location isn’t shared.
* See the attached screen record.
Bug: AFAIK it has been showing gray screen instead recently,but my firefox still showing white
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2020-09-14 15:58:10+00:00
Resolved: 2022-10-19 16:31:31+00:00

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

Steps to reproduce:

install and apply dark theme and darkreader plugin.open a new web site.


Actual results:

initial loading content page color is white


Expected results:

should be gray
Bug: Intermittent browser/base/content/test/tabs/browser_tabCloseSpacer.js | Close button hasn't moved - {"left":918,"top":8,"width":20,"height":20} deepEqual {"left":858,"top":8,"width":20,"height":20} - JS frame
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2020-09-14 19:02:27+00:00
Resolved: 2023-06-28 12:01:02+00:00

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

---
```
[task 2020-09-14T13:47:47.139Z] 13:47:47     INFO - TEST-PASS | browser/base/content/test/tabs/browser_tabCloseSpacer.js | Close button hasn't moved - {"left":858,"top":8,"width":20,"height":20} deepEqual {"left":858,"top":8,"width":20,"height":20} - 
[task 2020-09-14T13:47:47.140Z] 13:47:47     INFO - Buffered messages finished
[task 2020-09-14T13:47:47.140Z] 13:47:47     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/tabs/browser_tabCloseSpacer.js | Close button hasn't moved - {"left":918,"top":8,"width":20,"height":20} deepEqual {"left":858,"top":8,"width":20,"height":20} - JS frame :: chrome://mochitests/content/browser/browser/base/content/test/tabs/browser_tabCloseSpacer.js :: <TOP_LEVEL> :: line 33
[task 2020-09-14T13:47:47.140Z] 13:47:47     INFO - Stack trace:
[task 2020-09-14T13:47:47.140Z] 13:47:47     INFO - chrome://mochitests/content/browser/browser/base/content/test/tabs/browser_tabCloseSpacer.js:null:33
[task 2020-09-14T13:47:47.140Z] 13:47:47     INFO - Not taking screenshot here: see the one that was previously logged```
Bug: Intermittent TV tier 2  browser/components/urlbar/tests/browser/browser_separatePrivateDefault_differentEngine.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2020-09-14 20:07:34+00:00
Resolved: 2020-10-13 17:03:55+00:00

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

---
```
```
Bug: When I leave a full screen video firefox by pressing control+t the address bar does not highlight itself.
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-09-14 20:57:34+00:00
Resolved: 2020-09-15 06:08:25+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:80.0) Gecko/20100101 Firefox/80.0
Bug: There is no pointer Lock warning shown while requesting lock on an iframe
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2020-09-15 00:47:37+00:00
Resolved: 2020-10-21 12:16:54+00:00

Similar to bug 1580506, but happens on iframe.

STR: 
Click on the canvas area inside the iframe (the element with a blue border).

Actual Result:
We should see a warning showing up that the website has taken control of your cursor and you can get it back, but it doesn't show up.

Expected Result:
No warning showing up.
Bug: Firefox stops working if I press the Screenshot shortcut for more than 5 seconds
Status: NEW
Priority: P3
Created: 2020-09-15 06:16:21+00:00
Resolved: 2023-01-19 23:11:07+00:00

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

Steps to reproduce:

Click Ctrl+Shift+S for more than 5 seconds


Actual results:

Firefox was frozen on the "Take a screenshot screen"


Expected results:

Firefox should take a screenshot and not freeze
Bug: Intermittent browser/base/content/test/popups/browser_popup_frames.js | Test timed out -
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2020-09-15 06:23:36+00:00
Resolved: 2021-02-16 17:03:31+00:00

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

---
```
>[task 2020-09-15T05:22:28.763Z] 05:22:28     INFO - TEST-INFO | screenshot: exit 0
[task 2020-09-15T05:22:28.763Z] 05:22:28     INFO - Buffered messages logged at 05:21:43
[task 2020-09-15T05:22:28.763Z] 05:22:28     INFO - Entering test bound 
[task 2020-09-15T05:22:28.763Z] 05:22:28     INFO - Buffered messages finished
[task 2020-09-15T05:22:28.763Z] 05:22:28     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/popups/browser_popup_frames.js | Test timed out - 
[task 2020-09-15T05:22:28.764Z] 05:22:28     INFO - GECKO(10372) | MEMORY STAT | vsize 2104319MB | vsizeMaxContiguous 66901509MB | residentFast 269MB | heapAllocated 76MB
[task 2020-09-15T05:22:28.764Z] 05:22:28     INFO - TEST-OK | browser/base/content/test/popups/browser_popup_frames.js | took 45063ms
[task 2020-09-15T05:22:28.764Z] 05:22:28     INFO - Not taking screenshot here: see the one that was previously logged
[task 2020-09-15T05:22:28.764Z] 05:22:28     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/popups/browser_popup_frames.js | Found a tab after previous test timed out: http://example.com/ - 
[task 2020-09-15T05:22:28.769Z] 05:22:28     INFO - checking window state

*[task 2020-09-15T05:21:43.675Z] 05:21:43     INFO - TEST-START | browser/base/content/test/popups/browser_popup_frames.js*```
Bug: Permafailing browser/components/urlbar/tests/browser/browser_searchMode_engineRemoval.js | Test timed out when Gecko 82 merges to Beta on 2020-09-21
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2020-09-15 12:06:51+00:00
Resolved: 2020-09-18 14:12:17+00:00

*Central as Beta:* https://treeherder.mozilla.org/#/jobs?repo=try&revision=3f527b9e7d3dd625c89c9a426171ba6fef9e8821&searchStr=browser-chrome&group_state=expanded&selectedTaskRun=adKiZ8M_RCOSSSS98B7uIw.1

*Failure log:* https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=315733256&repo=try&lineNumber=10508

>[task 2020-09-15T11:36:45.855Z] 11:36:45     INFO - TEST-PASS | browser/components/urlbar/tests/browser/browser_searchMode_engineRemoval.js | Found one-off button for search mode - {"engine":{"_name":"Test","_loadPath":"[other]addEngineWithDetails:Test@test.engine","description":"undefined","__searchForm":"undefined","_iconURL":"","_metaData":{"order":1},"_urls":[{"params":[],"rels":[],"resultDomain":"example.com","template":"http://example.com/?search={searchTerms}"}],"_isAppProvided":false,"_orderHint":"undefined","_telemetryId":null,"_updateInterval":null,"_updateURL":null,"_iconUpdateURL":null,"_extensionID":"Test@test.engine","_locale":"default","_definedAliases":[],"_hasPreferredIcon":null,"queryCharset":"windows-1252"},"_inheritedElements":{".button-icon":{}},"initializedAttributeInheritance":true} == true - 
[task 2020-09-15T11:36:45.856Z] 11:36:45     INFO - Awaiting for the urlbar panel to open
[task 2020-09-15T11:36:45.856Z] 11:36:45     INFO - Buffered messages logged at 11:35:22
[task 2020-09-15T11:36:45.856Z] 11:36:45     INFO - Console message: [JavaScript Error: "Unknown Collection "main/nimbus-desktop-experiments"" {file: "resource://services-settings/RemoteSettingsClient.jsm" line: 160}]
[task 2020-09-15T11:36:45.856Z] 11:36:45     INFO - UnknownCollectionError@resource://services-settings/RemoteSettingsClient.jsm:160:5
[task 2020-09-15T11:36:45.856Z] 11:36:45     INFO - sync@resource://services-settings/RemoteSettingsClient.jsm:470:13
[task 2020-09-15T11:36:45.856Z] 11:36:45     INFO - 
[task 2020-09-15T11:36:45.856Z] 11:36:45     INFO - Buffered messages finished
[task 2020-09-15T11:36:45.856Z] 11:36:45     INFO - TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/browser/browser_searchMode_engineRemoval.js | Test timed out - 
[task 2020-09-15T11:36:45.856Z] 11:36:45     INFO - GECKO(3354) | MEMORY STAT | vsize 3684MB | residentFast 481MB | heapAllocated 141MB
[task 2020-09-15T11:36:45.864Z] 11:36:45     INFO - TEST-OK | browser/components/urlbar/tests/browser/browser_searchMode_engineRemoval.js | took 90067ms
Bug: Mozilla didn't restart my tabs on restart
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-09-15 13:03:04+00:00
Resolved: 2020-09-15 13:27:17+00:00

User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:80.0) Gecko/20100101 Firefox/80.0
Firefox for Android
Bug: Duplication of submissions in javascript events
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2020-09-15 13:58:47+00:00
Resolved: 2020-10-19 12:07:08+00:00

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

Steps to reproduce:

Many tests with javascript onsubmit events.


Actual results:

Duplicate submission of forms.


Expected results:

Single submission of forms.
Bug: Things going through UrlbarInput.search() are often considered typed.
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2020-09-15 14:04:45+00:00
Resolved: 2020-09-26 09:28:47+00:00

I'm not sure whether this is a problem for telemetry, but most things invoking gURLBar.search end up in search mode with entry: "typed", even if this can actually be invoked by the newtab handoff, a command, the touchbar or other.
See https://searchfox.org/mozilla-central/search?q=urlbar.search%28&path=&case=false&regexp=false

It may be worth checking which values we get for various operations involving search().
Bug: Some mouse-hovered Urlbar elements aren't annouced to screen readers
Status: RESOLVED
Priority: P2
Resolution: WONTFIX
Created: 2020-09-15 14:43:14+00:00
Resolved: 2020-09-17 21:14:53+00:00

**Tested on**
Firefox nightly 82.0a1 and affects:
Windows10 64bit using nvda
MacOS 10.15  using voiceover
Ubuntu 18.04

**Description**
One-offs and new search shortcut feature is not compatible with screen readers.  


**Steps to reproduce**

Install screen reader
Launch firefox
type for any word in url bar
Hover mose over search results
Hover mouse over one-offs
Click a one-off example (duckduckgo)
Hover mose over search mode box on the URL bar (duckduckgo box)

**Expected result**
screen reader should tell you where you are and what you are hovering and clicking.

**Actual result**
On windows 10: I am able to hear the one-offs, and the search mode box, but not the search suggestions.
On mac0s: i am not able to hear anything when i hover on thr search suggestions, nor one.offs, nor search mode box.
On ubuntu: i am not able to hear anything when i hover on thr search suggestions, nor one.offs, nor search mode box.
Bug: Intermittent browser/base/content/test/permissions/browser_permissions_handling_user_input.js | Test timed out -
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2020-09-15 14:45:45+00:00
Resolved: 2020-10-13 17:04:05+00:00

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

---
```
>[task 2020-09-15T13:46:32.007Z] 13:46:32     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/permissions/browser_permissions_handling_user_input.js | Test timed out - 
[task 2020-09-15T13:46:32.007Z] 13:46:32     INFO - GECKO(1476) | MEMORY STAT | vsize 3022MB | residentFast 341MB | heapAllocated 93MB
[task 2020-09-15T13:46:32.008Z] 13:46:32     INFO - TEST-OK | browser/base/content/test/permissions/browser_permissions_handling_user_input.js | took 90075ms
[task 2020-09-15T13:46:32.008Z] 13:46:32     INFO - Not taking screenshot here: see the one that was previously logged
[task 2020-09-15T13:46:32.009Z] 13:46:32     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/permissions/browser_permissions_handling_user_input.js | Found a tab after previous test timed out: https://example.com/browser/browser/base/content/test/permissions/permissions.html - 
[task 2020-09-15T13:46:32.012Z] 13:46:32     INFO - GECKO(1476) | [Child 1813: Main Thread]: I/DocShellAndDOMWindowLeak ++DOCSHELL 0x7fea84c55800 == 1 [pid = 1813] [id = {3f8c1cfc-7158-444b-b71f-d3077b2ecb73}]
[task 2020-09-15T13:46:32.012Z] 13:46:32     INFO - GECKO(1476) | [Child 1813: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 1 (0x7feaa1293180) [pid = 1813] [serial = 36] [outer = (nil)]
[task 2020-09-15T13:46:32.013Z] 13:46:32     INFO - GECKO(1476) | [Child 1813: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 2 (0x7fea84c5c000) [pid = 1813] [serial = 37] [outer = 0x7feaa1293180]
[task 2020-09-15T13:46:32.014Z] 13:46:32     INFO - checking window state

*[task 2020-09-15T13:45:01.683Z] 13:45:01     INFO - TEST-START | browser/base/content/test/permissions/browser_permissions_handling_user_input.js*```
Bug: Alias gets readded to addressbar after being translated into search-mode indicator
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2020-09-15 15:16:57+00:00
Resolved: 2020-10-14 10:01:26+00:00

##### [Sugested Severity:]
S4

##### [Description:]
An edge case when the @shortcut is translated to search-mode indicator and the @alias is readded.

##### [Environment:]
Ubuntu 20.04 / Windows 10 / Mac 10.13.6
82.0a1 2020-09-15


##### [Steps:]
1. Open Firefox.
2. New tab.
3. type @google+space -> alias gets transformed into search-mode indicator.
4. Press + to create a new tab.
5. Navigate back to the step 3 tab.

##### [Actual Result:]
google search mode-indicator + @google present in the tab.

##### [Expected Result:]
google search mode-indicator

##### [Regression Range]
On 81.0 2020-09-14, flipping the Browser.urlbar.update2.* prefs, the issue doesn't reproduce, so I'd guess it's a regression caused by bug 1647890.

I'll get back with a confirmed regression range at a later point.
Bug: Search start-up service intialization browser console error
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2020-09-15 15:41:49+00:00
Resolved: 2020-10-12 09:28:35+00:00

##### [Sugested Severity:]
S4 until investigated

##### [Description:]
First startup + fast type @ in the address bar

##### [Environment:]
Ubuntu 20.04 / Windows 10 
82.0a1 2020-09-15


##### [Steps:]
1. Create a new profile.
2. At fist start-up fast type @ in the addressbar.

##### [Actual Result:]

Error: Something tried to use the search service before it's been properly intialized. Please examine the stack trace to figure out what and where to fix it:
_ensureinitialized@resource://gre/modules/searchservice.jsm:233:15
getenginebyname@resource://gre/modules/searchservice.jsm:1408:10
setsearchmode@resource:///modules/urlbarinput.jsm:1270:34
seturi@resource:///modules/urlbarinput.jsm:364:12
onlocationchange@chrome://browser/content/browser.js:5289:15
calllisteners@chrome://browser/content/tabbrowser.js:832:31
_callprogresslisteners@chrome://browser/content/tabbrowser.js:846:22
_callprogresslisteners@chrome://browser/content/tabbrowser.js:5826:46
onlocationchange@chrome://browser/content/tabbrowser.js:6239:14
SearchService.jsm:233:15

[Note:]
1. It's a bit intermittent, so a slow PC would help.
2. This might also be a search shortcuts (bug 1644572) related issue, but blocking post-modernization first for investigation.
Bug: Search Settings may attempt to be written whilst the search service is still initialising
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2020-09-15 16:30:44+00:00
Resolved: 2020-09-18 09:53:16+00:00

I noticed this whilst checking tests for errors - the changes added in bug 1642995 to set the new search order, may cause us to attempt to write the initialisation file before the service has initialised.

As a result, the search data may be incomplete.

Really, the settings should just prevent trying to save whilst initialisation or reloading engines is in progress.
Bug: Intermittent browser/components/preferences/tests/browser_browser_languages_subdialog.js | leaked 2 window(s) until shutdown [url = about:preferences#general]
Status: RESOLVED
Priority: P5
Resolution: DUPLICATE
Created: 2020-09-15 16:52:04+00:00
Resolved: 2020-09-28 06:12:09+00:00

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

---
```
>[task 2020-09-15T15:46:08.147Z] 15:46:08     INFO - TEST-INFO | Main app process: exit 0
[task 2020-09-15T15:46:08.147Z] 15:46:08     INFO - TEST-INFO | Confirming we saw 844 DOCSHELL created and 844 destroyed log strings.
[task 2020-09-15T15:46:08.147Z] 15:46:08     INFO - TEST-INFO | Confirming we saw 2059 DOMWINDOW created and 2059 destroyed log strings.
[task 2020-09-15T15:46:08.147Z] 15:46:08    ERROR - TEST-UNEXPECTED-FAIL | browser/components/preferences/tests/browser_browser_languages_subdialog.js | leaked 2 window(s) until shutdown [url = about:preferences#general]
[task 2020-09-15T15:46:08.147Z] 15:46:08     INFO - TEST-INFO | browser/components/preferences/tests/browser_browser_languages_subdialog.js | windows(s) leaked: [pid = 1674] [serial = 50], [pid = 1674] [serial = 52]
[task 2020-09-15T15:46:08.147Z] 15:46:08     INFO - TEST-INFO | browser/components/preferences/tests/browser_browser_languages_subdialog.js | This test created 0 hidden window(s)
[task 2020-09-15T15:46:08.147Z] 15:46:08     INFO - TEST-INFO | browser/components/preferences/tests/browser_browser_languages_subdialog.js | This test created 1 hidden docshell(s)

*[task 2020-09-15T15:46:05.098Z] 15:46:05     INFO - TEST-START | Shutdown*```
Bug: Automatic Audio/Video playback should be disabled during Session Restore
Status: NEW
Priority: --
Created: 2020-09-15 17:24:39+00:00
Resolved: 2023-11-17 16:43:38+00:00

Steps to reproduce:
* Open a page with video or audio
* Allow automatic playback
* (optional) Pause Video
* Restart Firefox

Expected Results
* Session is restored but **no** automatic playback of audio or video

Actual Results
* Session is restored and video/ audio starts automatically
* This is especially bad with multiple windows where you have to search which window caused the sound
* I restarted Firefox while in a VideoConference today with the result of other participants having the honor to listen to Ken Block driving an Electric Rally Cross Car
* Since with that others can listen to your video/audio by accident, this is also a bit of a privacy issue
Bug: Theme icons not displayed in multistage welcome
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2020-09-15 18:44:20+00:00
Resolved: 2020-09-23 11:26:51+00:00

STR:

1. Build latest m-c
2. Open about:welcome
3. Navigate to theme screen by clicking 'start setup'

Expected
1. On theme screen themes icons shows inside respective tiles

Actual
Theme icons are not visible ( See attached) with error in console as "Security Error: Content at resource://activity-stream/aboutwelcome/aboutwelcome.css may not load or link to chrome://mozapps/content/extensions/default-theme.svg"
Bug: Remove maintenance service UpdateLogs directory from Firefox uninstaller
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2020-09-15 20:14:23+00:00
Resolved: 2020-10-26 18:39:35+00:00

Bug 1654913 was supposed to make the maintenance service uninstaller start removing the `UpdateLogs` directory, but because of bug 1665193 anything that isn't a new install (made since 80) won't pick up the change to the maintenance service uninstaller. But changes to the Firefox uninstaller always get picked up, so also removing the directory from there (when it's empty) would get us around this problem and actually really finally fix the bug.
Bug: strange line below active tab in Alpenglow theme
Status: RESOLVED
Priority: P3
Resolution: WORKSFORME
Created: 2020-09-15 20:44:05+00:00
Resolved: 2022-01-05 18:57:47+00:00

There is a strange grey line below the active tab in the Alpenglow theme. Neither the other bundles themes nor one of the other themes from addons.mozilla.org I tried have such a line and it looks out of place so I guess it's not intended.

OS: macOS Big Sur Beta and macOS 10.13, didn't test on other operating systems. Firefox Beta 81 and Firefox Nightly 82 are affected.
Bug: Managed bookmarks UI increases browser.xhtml size unnecessarily
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2020-09-16 00:28:50+00:00
Resolved: 2020-10-07 18:19:22+00:00

The managed bookmarks button is always present in the DOM, as is the context menu popup, which offers broadly the same options as the normal places context menu popup but has been duplicated, for reasons that I do not fully understand.

However, for 90% of users neither is ever used.

These nodes should not be in the initially loaded DOM.