av9ash/GitBugs huggingface dataset:
Bug: RTAMO flow is broken on Firefox Release
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2021-03-11 13:00:18+00:00
Resolved: 2022-03-07 11:35:18+00:00

[Affected versions]:
86.0/20210222142601

[Steps to reproduce]:

1. Access AMO prod on a browser different from Firefox (example: Microsoft Edge) and afterwards the page of a recommended add-on (for example uBlock Origin)
2. Click on the “Only with Firefox – Get Firefox Now” green button 
3. On the newly opened page, click on the blue “Download Firefox” button
Note: Firefox will be downloaded, installed and will start after the installation is complete
4. Observe that the Multi Stage about:welcome page is displayed and not the RTAMO about:welcome page, as it should

[Expected results]:
The RTAMO about:welcome page should be displayed.

[Actual results]:
The Multi Stage about:welcome page is displayed.

NOTES:
1. The RTAMO flow works as expected on the latest Unbranded Release, Nightly and Beta with AMO prod, stage and dev.
2. Tests were performed on Windows 10 x64 in accordance to the steps from here: https://gist.github.com/pdehaan/71028fb23b3f3d36f8dc55a6cfd2643e
3. Tested Firefox Release 83 and 85.0.2 and the issue is also present on those versions as well, which most likely indicates that all Release versions are affected.
Bug: Search bar text pushes other elements down in Compact mode
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2021-03-11 13:41:02+00:00
Resolved: 2021-03-25 02:01:42+00:00

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

### Steps to reproduce
1. Use a new profile. No proton related stuff is enabled.
2. Set UI density to `Compact`.
3. Add search bar to the toolbar.
4. Type something in search bar.

### Actual result
When there is text in the bar:
1. Search bar is stretched to the bottom for 1px.
2. Content window is pushed down for 1px.
3. Some other text elements are also pushed down.

Please refer to the attached video.

### Notes
1. `Normal` and `Touch` density are not affected.
2.  Typing in address bar does not exhibit the issue.

This is regressed by bug 1696628. Bug 1697293 does not fix it.
Bug: Downloads panel with failed download shown after every restart
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2021-03-11 15:45:05+00:00
Resolved: 2025-03-02 14:51:29+00:00

The last thing I tried to download was a PDF served from an insecure, HTTP site. Firefox blocked this download and showed the "potential security risk" error (even if it took me a while to figure out what was happening).

Now, every time I restart (Nightly 88 as of this writing), Firefox always shows the download dialog.  I suspect it is because of the failed download, but haven't tried to download something else in case my current state is helpful for debugging.

Image attached shows state of Firefox, including downloads panel, after a restart.
Bug: about dialog download progress stopped working
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2021-03-11 17:51:56+00:00
Resolved: 2021-07-12 17:20:54+00:00

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

Steps to reproduce:

When you open the about dialog and either check for or if there is an upgrade available clicking the update to begin download it does not show the progress of the download.


Actual results:

The download progress is not working it will download but does not show the progress of the download.


Expected results:

It should show the download in progress. it just sits there and once the download is completes starts the installation.
Bug: (Proton) the tab width changes when opening/closes tabs
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2021-03-11 18:31:11+00:00
Resolved: 2021-04-22 08:19:03+00:00

STR:

1. open at least two tabs
2. close a tab
3. open a new tab
4. repeat the steps 2 and 3 a few times.

Expected:

No change of the tab width.

Actual:

The tab width changes. You can observe the close icon of the tab left of the closed tab to see the change.

This video demonstrates the issue:
https://www.youtube.com/watch?v=b_PxDikohQE

It's a very recent regression (I noticed it in yesterday's Nightly build for the first time).
Bug: Restoring a crashed tab does not restore the page that was being viewed
Status: NEW
Priority: --
Created: 2021-03-11 19:42:04+00:00
Resolved: 2021-04-29 09:02:28+00:00

I noticed this crash in nightly buildid 20210311093001, the release channel doesn't seem to be affected. Fission was enabled.

STR:
1. Browse to https://www.mozilla.org
2. In the same tab browse to https://www.thunderbird.net
3. Now browse to about:crashcontent to crash the underlying process
4. Click on "Restore this tab"

Expected result: the tab is restored and https://www.thunderbird.net is shown
Actual result: the tab is restored and https://www.mozilla.org is shown
Bug: v86.0.1 [desktop] duplicate "Highlights" picture-tile bug
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2021-03-11 20:32:31+00:00
Resolved: 2021-06-15 15:00:11+00:00

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

Steps to reproduce:

I was searching .


Actual results:

I got two identical pictures in two "Highlights" tiles -- one was correct for the search -- the other one wasn't .



Expected results:

I SHOULD have gotten two different tile-pictures .
Bug: "List all tabs" does not include pinned tabs in the list
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2021-03-11 20:56:27+00:00
Resolved: 2021-10-13 07:19:27+00:00

On Nightly 88.0a1 (2021-03-10), on macOS 11.2.3, the "List all tabs" tab list does not include pinned tabs. See screenshot.
Bug: bookmark in bookmarks toolbar flickers instead of showing the tooltip if you hover on the bottom of the bookmark
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2021-03-11 21:42:10+00:00
Resolved: 2021-06-07 14:46:43+00:00

STR:

1. Make sure that the following preferences are enabled:

browser.proton.tabs.enabled
browser.proton.places-tooltip.enabled

All other Proton options can bei either enabled or disabled. I don't know why the tabs setting affects the bookmarks toolbar but it only happens with the tabs setting enabled.

2. Enable the bookmarks toolbar and make sure that you have at least one bookmark in your bookmarks toolbar.
3. Move your mouse over a bookmark in the bookmarks toolbar, try it at the bottom of the bookmark and other positions.

Expected:

The tooltip appears, no matter where you move the mouse.

Actual:

The tooltip does not appear of you move the move on the bottom of the bookmark. Instead the bookmark flickers.
Bug: Intermittent TV browser/components/urlbar/tests/browser/browser_aboutHomeLoading.js | leaked 1 window(s) until shutdown [url = about:home]
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2021-03-11 23:04:05+00:00
Resolved: 2021-04-06 17:05:55+00:00

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

---
```
[task 2021-03-11T21:42:32.082Z] 21:42:32     INFO - GECKO(22754) | [Parent 22754, Main Thread] WARNING: NS_ENSURE_TRUE(Preferences::InitStaticMembers()) failed: file /builds/worker/checkouts/gecko/modules/libpref/Preferences.cpp:4377
[task 2021-03-11T21:42:32.114Z] 21:42:32     INFO - TEST-INFO | Main app process: exit 0
[task 2021-03-11T21:42:32.115Z] 21:42:32     INFO - TEST-INFO | Confirming we saw 39 DOCSHELL created and 39 destroyed log strings.
[task 2021-03-11T21:42:32.116Z] 21:42:32     INFO - TEST-INFO | Confirming we saw 102 DOMWINDOW created and 102 destroyed log strings.
[task 2021-03-11T21:42:32.117Z] 21:42:32    ERROR - TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/browser/browser_aboutHomeLoading.js | leaked 1 window(s) until shutdown [url = about:home]
[task 2021-03-11T21:42:32.118Z] 21:42:32     INFO - TEST-INFO | browser/components/urlbar/tests/browser/browser_aboutHomeLoading.js | windows(s) leaked: [pid = 22879] [serial = 33]
[task 2021-03-11T21:42:32.119Z] 21:42:32     INFO - TEST-INFO | browser/components/urlbar/tests/browser/browser_aboutHomeLoading.js | This test created 1 hidden window(s)
[task 2021-03-11T21:42:32.120Z] 21:42:32     INFO - TEST-INFO | browser/components/urlbar/tests/browser/browser_aboutHomeLoading.js | This test created 1 hidden docshell(s)
[task 2021-03-11T21:42:32.121Z] 21:42:32     INFO - runtests.py | Application ran for: 0:00:42.189867```
Bug: Intermittent TV browser/components/urlbar/tests/browser/browser_aboutHomeLoading.js | userTypedValue should be null - Got "about:home", expected null
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2021-03-11 23:04:53+00:00
Resolved: 2021-06-15 17:02:29+00:00

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

---
```
[task 2021-03-11T21:22:08.773Z] 21:22:08     INFO - TEST-PASS | browser/components/urlbar/tests/browser/browser_aboutHomeLoading.js | URL bar should be empty - 
[task 2021-03-11T21:22:08.773Z] 21:22:08     INFO - Buffered messages finished
[task 2021-03-11T21:22:08.774Z] 21:22:08     INFO - TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/browser/browser_aboutHomeLoading.js | userTypedValue should be null - Got "about:home", expected null
[task 2021-03-11T21:22:08.775Z] 21:22:08     INFO - Stack trace:
[task 2021-03-11T21:22:08.776Z] 21:22:08     INFO - chrome://mochikit/content/browser-test.js:test_is:1359
[task 2021-03-11T21:22:08.776Z] 21:22:08     INFO - chrome://mochitests/content/browser/browser/components/urlbar/tests/browser/browser_aboutHomeLoading.js:clearURLBarAfterManuallyLoadingAboutHome:110
[task 2021-03-11T21:22:08.777Z] 21:22:08     INFO - Leaving test bound clearURLBarAfterManuallyLoadingAboutHome
[task 2021-03-11T21:22:08.778Z] 21:22:08     INFO - Entering test bound dontTemporarilyShowAboutHome
[task 2021-03-11T21:22:08.778Z] 21:22:08     INFO - GECKO(13575) | JavaScript error: resource:///actors/ContentSearchParent.jsm, line 624: TypeError: can't access property "addEventListener", browser is null
[task 2021-03-11T21:22:08.779Z] 21:22:08     INFO - Console message: [JavaScript Error: "TypeError: can't access property "addEventListener", browser is null" {file: "resource:///actors/ContentSearchParent.jsm" line: 624}]
[task 2021-03-11T21:22:08.780Z] 21:22:08     INFO - receiveMessage@resource:///actors/ContentSearchParent.jsm:624:5
[task 2021-03-11T21:22:08.780Z] 21:22:08     INFO - 
[task 2021-03-11T21:22:11.194Z] 21:22:11     INFO - TEST-PASS | browser/components/urlbar/tests/browser/browser_aboutHomeLoading.js | 2 tabs opened - ```
Bug: Intermittent TV browser/base/content/test/general/browser_bug462289.js | tab key to selected tab1 activates tab - Got [object XULElement], expected [object XULElement]
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2021-03-11 23:06:10+00:00
Resolved: 2021-04-06 17:05:59+00:00

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

---
```
[task 2021-03-11T20:57:55.303Z] 20:57:55     INFO - TEST-PASS | browser/base/content/test/general/browser_bug462289.js | focusing URLBar then sending 2 Shift+Tab. - 
[task 2021-03-11T20:57:55.304Z] 20:57:55     INFO - Focus is now on Home button (#)
[task 2021-03-11T20:57:55.304Z] 20:57:55     INFO - TEST-PASS | browser/base/content/test/general/browser_bug462289.js | tab key to selected tab1 keeps tab selected - 
[task 2021-03-11T20:57:55.305Z] 20:57:55     INFO - Buffered messages finished
[task 2021-03-11T20:57:55.307Z] 20:57:55     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/general/browser_bug462289.js | tab key to selected tab1 activates tab - Got [object XULElement], expected [object XULElement]
[task 2021-03-11T20:57:55.308Z] 20:57:55     INFO - Stack trace:
[task 2021-03-11T20:57:55.309Z] 20:57:55     INFO - chrome://mochikit/content/browser-test.js:test_is:1359
[task 2021-03-11T20:57:55.310Z] 20:57:55     INFO - chrome://mochitests/content/browser/browser/base/content/test/general/browser_bug462289.js:step3:57
[task 2021-03-11T20:57:55.311Z] 20:57:55     INFO - Console message: [JavaScript Warning: "Key event not available on some keyboard layouts: key=“r” modifiers=“accel,alt” id=“key_toggleReaderMode”" {file: "chrome://mochikit/content/tests/SimpleTest/EventUtils.js" line: 1280}]
[task 2021-03-11T20:57:55.312Z] 20:57:55     INFO - Console message: [JavaScript Warning: "Key event not available on some keyboard layouts: key=“i” modifiers=“accel,alt,shift” id=“key_browserToolbox”" {file: "chrome://mochikit/content/tests/SimpleTest/EventUtils.js" line: 1280}]
[task 2021-03-11T20:57:55.313Z] 20:57:55     INFO - TEST-PASS | browser/base/content/test/general/browser_bug462289.js | 3rd click on activated tab1 keeps tab selected - ```
Bug: Intermittent browser/components/urlbar/tests/browser/browser_aboutHomeLoading.js | Uncaught exception - at chrome://browser_aboutHomeLoading.js:151 - TypeError: can't access property "linkedBrowser", otherTab is null
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2021-03-11 23:08:51+00:00
Resolved: 2021-04-06 17:06:01+00:00

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

---
```
[task 2021-03-11T21:56:09.487Z] 21:56:09     INFO - TEST-PASS | browser/components/urlbar/tests/browser/browser_aboutHomeLoading.js | Should have a closed window - 
[task 2021-03-11T21:56:09.487Z] 21:56:09     INFO - Buffered messages finished
[task 2021-03-11T21:56:09.488Z] 21:56:09     INFO - TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/browser/browser_aboutHomeLoading.js | Uncaught exception - at chrome://mochitests/content/browser/browser/components/urlbar/tests/browser/browser_aboutHomeLoading.js:151 - TypeError: can't access property "linkedBrowser", otherTab is null
[task 2021-03-11T21:56:09.489Z] 21:56:09     INFO - Stack trace:
[task 2021-03-11T21:56:09.489Z] 21:56:09     INFO - dontTemporarilyShowAboutHome@chrome://mochitests/content/browser/browser/components/urlbar/tests/browser/browser_aboutHomeLoading.js:151:1
[task 2021-03-11T21:56:09.490Z] 21:56:09     INFO - Leaving test bound dontTemporarilyShowAboutHome
[task 2021-03-11T21:56:09.490Z] 21:56:09     INFO - Entering test bound ```
Bug: Intermittent browser/components/newtab/test/xpcshell/test_AboutHomeStartupCacheWorker.js | xpcshell return code: 1
Status: RESOLVED
Priority: P5
Resolution: DUPLICATE
Created: 2021-03-12 03:05:08+00:00
Resolved: 2022-07-25 22:53:01+00:00

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

---
```
[task 2021-03-12T00:26:10.305Z] 00:26:10     INFO -  TEST-START | browser/components/newtab/test/xpcshell/test_AboutHomeStartupCacheWorker.js
[task 2021-03-12T00:26:12.125Z] 00:26:12  WARNING -  TEST-UNEXPECTED-FAIL | browser/components/newtab/test/xpcshell/test_AboutHomeStartupCacheWorker.js | xpcshell return code: 1
[task 2021-03-12T00:26:12.125Z] 00:26:12     INFO -  TEST-INFO took 1822ms
[task 2021-03-12T00:26:12.126Z] 00:26:12     INFO -  >>>>>>>
[task 2021-03-12T00:26:12.126Z] 00:26:12     INFO -  PID 2092 | [Parent 2092, Main Thread] WARNING: Failed to get directory to cache.: file /builds/worker/checkouts/gecko/security/sandbox/win/src/sandboxbroker/sandboxBroker.cpp:120
[task 2021-03-12T00:26:12.126Z] 00:26:12     INFO -  PID 2092 | [Parent 2092, Main Thread] WARNING: Failed to get directory to cache.: file /builds/worker/checkouts/gecko/security/sandbox/win/src/sandboxbroker/sandboxBroker.cpp:120
[task 2021-03-12T00:26:12.126Z] 00:26:12     INFO -  PID 2092 | [Parent 2092, Main Thread] WARNING: Failed to get directory to cache.: file /builds/worker/checkouts/gecko/security/sandbox/win/src/sandboxbroker/sandboxBroker.cpp:120
[task 2021-03-12T00:26:12.126Z] 00:26:12     INFO -  PID 2092 | [Parent 2092, Main Thread] WARNING: Failed to get directory to cache.: file /builds/worker/checkouts/gecko/security/sandbox/win/src/sandboxbroker/sandboxBroker.cpp:120
[task 2021-03-12T00:26:12.126Z] 00:26:12     INFO -  PID 2092 | [Parent 2092, Main Thread] WARNING: Failed to get directory to cache.: file /builds/worker/checkouts/gecko/security/sandbox/win/src/sandboxbroker/sandboxBroker.cpp:120
[task 2021-03-12T00:26:12.127Z] 00:26:12     INFO -  PID 2092 | [Parent 2092, Main Thread] WARNING: Couldn't get the user appdata directory. Crash events may not be produced.: file /builds/worker/checkouts/gecko/toolkit/crashreporter/nsExceptionHandler.cpp:2896
[task 2021-03-12T00:26:12.127Z] 00:26:12     INFO -  (xpcshell/head.js) | test MAIN run_test pending (1)
[task 2021-03-12T00:26:12.128Z] 00:26:12     INFO -  (xpcshell/head.js) | test run_next_test 0 pending (2)
[task 2021-03-12T00:26:12.128Z] 00:26:12     INFO -  (xpcshell/head.js) | test MAIN run_test finished (2)
[task 2021-03-12T00:26:12.128Z] 00:26:12     INFO -  running event loop
[task 2021-03-12T00:26:12.128Z] 00:26:12     INFO -  browser/components/newtab/test/xpcshell/test_AboutHomeStartupCacheWorker.js | Starting setup
[task 2021-03-12T00:26:12.128Z] 00:26:12     INFO -  (xpcshell/head.js) | test setup pending (2)
[task 2021-03-12T00:26:12.129Z] 00:26:12     INFO -  "CONSOLE_MESSAGE: (info) 1615508770594	addons.manager	DEBUG	Application has been upgraded"```
Bug: Grace periods should disappear on block, not when blocks are cleared.
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2021-03-12 06:00:03+00:00
Resolved: 2023-06-19 22:51:53+00:00

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

*(I'm filing this as a follow-up to bug 1693621 so the latter can land.)*

STRs:
 1. Open https://mozilla.github.io/webrtc-landing/enumerate.html in a new tab
 2. Click `Start Cam!` and **Allow** in prompt
 3. Click `Stop!`
 4. Click `Start Both!` and **Don't Allow** in prompt
 5. Refresh the page with ↻
 6. Click `Start Cam!`

Expected result: prompt
Actual result: camera turns on

Reasoning:
- The purpose of blocks is to block future getUserMedia calls, so having grace periods co-exist with them is confusing.
- The fact that blocks can be lifted by ↻ while grace periods can't doesn't change user intent when enacting (as opposed to lifting) them.

Known corner-case:
- Due to bug 1695757, there's a corner case with device switching, where a site may have an active camera, while at the same time be blocked from calling `getUserMedia` again. I don't think I care terribly about whether there's a grace period or not when that active camera stops capturing, as I'd rather we fix bug 1695757 to avoid that user trap.

Proposal:
- Don't store opposing intents. If we clear all grace periods at the point a block is enacted, I think that should do the right thing.

Found by written test, which I'll add to this bug.
Bug: .jpg photos are sometimes saved as .webp
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2021-03-12 07:19:02+00:00
Resolved: 2022-01-08 11:24:34+00:00

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

Steps to reproduce:

Tried to save a series of .jpg photos from a single website. I would right click the mouse and choose the option


Actual results:

Firefox saved the photos as .webp or incomplete .jpg photos which display as filenames only.


Expected results:

It should have saved all the photos as .jpg

I have attached a photos. Incorrectly saved in .WebP format by Firefox

I tried the same operation using Google Chrome, Apple Safari and Opera and had no problem. The bug appears to be intermittent and only in Firefox since sometime after version 84.0
Bug: [Proton] Missing `Send to All Devices` and `Manage Devices` from Send to device context menu
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2021-03-12 09:20:16+00:00
Resolved: 2021-03-17 15:55:28+00:00

**Affected versions**
* Latest Nightly 88.0a1

**Unaffected versions**
* Firefox 86.0.1
* Firefox 87.0b9

**Affected platforms**
* Windows 7 64bit
* Windows 10 64bit
* macOS 10.15
* Ubuntu 20.04

**Steps to reproduce**
1. Start Firefox
2. Login to a Firefox account that has more then 1 device connected to it (I used one with 3 and 30 devices)
3. Right click any tab (except about: pages)
4. Click `Send Tab to Device`

**Expected result**
* Devices connected are displayed along with `Send to All Devices... and Manage Devices...`.

**Actual result**
* `Send to All Devices... and Manage Devices...` options are missing from context menu.

**Regression range**
* First bad: 403ffdf9b6fb1d2be503cfb0feddae5faa3b85b7
* Last good: 73633f8e0e5860e4801288251decf1eaa6759b27
* Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=cffeff2a28032c57f5d43a8293814d4cedbbc804&tochange=b422dd886e036907f35269f381f43785873c5296
* Potential regressor: Bug 1690131: create proton-specific fxa menu

**Additional notes**
* Screenshot showing the issue attached.

**Suggested severity**
* I would mark this an S2 because items in menus are missing.
Bug: The zoom buttons from the Hamburger Menu have a background color that looks bad with dark themes
Status: RESOLVED
Priority: P1
Resolution: DUPLICATE
Created: 2021-03-12 10:14:56+00:00
Resolved: 2021-03-22 13:54:30+00:00

**Note**
* When the user activates the Proton Hamburger Menu changes, sets a dark theme and opens the Hamburger Menu, he will notice that the zoom icons have a background color that looks bad with dark themes.

**Affected versions**
* Nightly v88.0a1

**Affected platforms**
* all

**Steps to reproduce**
1. Lunch browser.
2. Activate Proton (Hamburger Menu, specifically)
3. Set a Dark Theme.
4. Open Hamburger Menu.

**Expected result**
* The zoom buttons have a pleasant color scheme in contrast with the Dark Theme background.

**Actual result**
* The zoom button icons have an unpleasant light gray background color and it looks bad in contrast with the Dark Theme background.

**Regression range**
* Not a regression, but an implementation issue.

**Additional notes**
* Beta is not really affected, but I wasn't sure how it would be best to flag it. The icons colors are inverted in Beta with Proton enabled.