av9ash/GitBugs huggingface dataset:
Bug: The “Collection” section is wrongly dismissed when a collection card is dismissed, archived, or deleted from Pocket
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2020-02-28 14:18:36+00:00
Resolved: 2020-03-10 16:07:10+00:00

**[Affected versions]:**
- Firefox Nightly 75.0a1 Build ID: 20200228092428

**[Affected Platforms]:**
- Windows 10 x64
- macOS 10.15
- Arch Linux 5.3.6 x64

**[Prerequisites]:**
- Have the value of the pref `browser.newtabpage.activity-stream.discoverystream.endpoints` set to `http,https`.
- Have the value of the pref `browser.newtabpage.activity-stream.discoverystream.config` set to `{"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":true,"layout_endpoint":"https://e5e8374d-fffa-4a77-a604-31603852b6fd.mock.pstmn.io/1615081-layout"}`.
- Have the value of the pref` browser.search.region` set to `US`.

**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Open a new tab and hover a card from the “Collection” section.
3. Click the “Open menu” button and select the “Dismiss” option.
4. Observe the “Collection” section.

**[Expected result]:**
- The “Collection” section only has 2 cards left and the dismissed card disappears.

**[Actual result]:**
- The “Collection” section is completely dismissed.

**[Notes]:**
- This issue is also reproducible if the “Archive to pocket” or “Delete from Pocket” options are selected instead.
- If a “Sponsored Card” from the “Recommended by Pocket” section that has a URL shared with a card from the “Collection” section is dismissed, archived, or deleted from Pocket, the whole “Collection” section is dismissed.
- Attached a screen recording of the issue.
Bug: Synced tabs results disappear when the 2-lines layout is displayed
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2020-02-28 14:45:50+00:00
Resolved: 2020-03-05 21:55:41+00:00

[screencast attached]

STR:
1. Enter a query in the Urlbar that would cause synced tab results to appear. Just searching the open tabs restriction character, "%", is probably easiest.
2. Shrink the window horizontally until you pass the threshold where 2-line results would appear in the Urlbar.

Expected:
All the same results appear in the Urlbar.

Actual:
All the synced tab results disappear. They reappear when the window is expanded.
Bug: crash
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2020-02-28 14:51:09+00:00
Resolved: 2020-02-28 16:37:41+00:00

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

Steps to reproduce:

Just using


Actual results:

Sooner or later crashes
Bug: Pop-up window still showing up even after being blocked
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-02-28 15:11:31+00:00
Resolved: 2020-03-06 02:14:35+00:00

**Affected versions**
* 75.0a1 (2020-02-28)
* 74.0b9
* 73.0.1

**Affected platforms**
* Windows 10x64
* Windows 7x64
* macOS 10.14
* Ubuntu 18.04x64

**Steps to reproduce**
1. Launch Firefox.
2. Go to and about:preferences#privacy and check that “Block pop-up windows” is checked.
3. Go to www.pinterest.com
4. Click two times on Continue with Facebook or Google account button.

**Expected result**
* The pop-up window is blocked.

**Actual result**
* The pop-up window is displayed.

**Regression range**
* This issue is not a recent regression since I was able to reproduce it on Firefox 73.0.1. I’ll come with a regression range asap.
Bug: Interventions button stays pressed when mouse is moved to another area
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2020-02-28 15:17:54+00:00
Resolved: 2020-07-09 04:33:02+00:00

Checked on Windows10 64bit + Ubuntu 18.04 64bit + Macos 10.14
Firefox Beta 74.0b8     disabled
Firefox Nightly 75.0a1  affected
Firefox Release 73.0.1  not affected

Steps to reproduce:
- set user.js with these 2 lines
      user_pref("browser.urlbar.update1", true); 
      user_pref("browser.urlbar.update1.interventions", true);
- Create new profile with the user.js
- Launch firefox
- In URL bar type "refresh firefox"
- hover mouse on button "Refresh"
- left mouse click on button and keep it pressed
- move mouse arrow away from button

Results: Button stays selected and pressed.

Expected result: if you click, then move the mouse out of button then release, it shouldn't do button_pressed

Notes:
Same thing happens to the button next to it "get help" Question mark.

Also happens with other buttons interventions like:
"Cache firefox"
"refresh firefox"
"update firefox"
Bug: Interventions missing on Firefox Localized versions
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-02-28 16:07:48+00:00
Resolved: 2020-03-06 02:33:32+00:00

Checked on Windows10 64bit + Ubuntu 18.04 64bit  
Firefox Beta 74.0b8       disabled
Firefox Nightly 75.0a1    affected
Firefox Release 73.0.1    not affected

Steps to reproduce
- USE A LOCALIZED VERSION OF FIREFOX (example firefox-75.0a1.es-AR.win64.installer.exe)
- set user.js with these 2 lines
  user_pref("browser.urlbar.update1", true); 
  user_pref("browser.urlbar.update1.interventions", true);
- Create new profile with the user.js
- Launch firefox
- In URL bar type "refresh firefox"

Results: no interventions are shown

Expected result: Not sure if interventions need to show be on localized versions, i tried spanish words and also did not work.

Notes:
 
Also happens with other buttons interventions like:
"Cache firefox"
"refresh firefox"
"update firefox"
Bug: Default Zoom Level access keys changed between version 72.0.2 and 73.0.1
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2020-02-28 16:28:30+00:00
Resolved: 2020-03-03 12:13:33+00:00

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

Steps to reproduce:

Open Firefox
Type these keys:
ALT
V
R


Actual results:

Nothing.

The access keys for this function changed from ALT V (R)eset to ALT V (A)ctual size.



Expected results:

The menu Items should have been kept the same:
(R)eset
or changed to:
(R)eset to actual size
instead of being changed to:
(A)ctual size

Becuase the only reason to choose that option is to RESET the tab to the Default Zoom Level
Bug: An increase in the number of tabs not correctly connecting to content processes are being reported for recent Nightlies
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2020-02-28 18:09:15+00:00
Resolved: 2020-04-15 20:55:22+00:00

Both tbabos and shorlander have been seeing this behaviour over the past two days or so.

From what I can gather, tabs don't have nsIRemoteTab available off of their browser's frameloaders, so a bunch of stuff in the front-end breaks because it's not designed to handle the case where the frameloader didn't successfully connect to a content process.

Putting this in DOM :: Content Processes for now, but perhaps this could also belong in Firefox :: Tabbed Browser, in the event that we're not handling a failure case properly here.
Bug: [macOS] Menulists in the prefs are not tall enough
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2020-02-28 18:13:47+00:00
Resolved: 2020-03-24 07:22:31+00:00

Today in "no good deed goes unpunished" - I regressed this in bug 1616008 because I missed the macOS-only rule at https://searchfox.org/mozilla-central/rev/a3266997560904b484fd89d6a6bcdeace4a13652/toolkit/themes/osx/global/menulist.css#15 , which takes precedence over the `menulist` rule in the prefs, so it sets `min-height` to `20px` instead of `30px`.
Bug: PDF viewer never gets into a "ready to print" state inside an iframe with a "too small" size
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2020-02-28 19:26:50+00:00
Resolved: 2020-04-01 21:28:51+00:00

Testcase:
```
<iframe style="width: 10px; height: 10px" src="test.pdf"></iframe>
<button onclick="frames[0].print()">Click me</button>
```
Live version at http://web.mit.edu/bzbarsky/www/testcases/pdf-printing/print-with-small-size.html

Load the testcase, wait a bit, click the button.   Instead of the PDF getting printed properly, you will get the "The PDF is not fully loaded for printing" alert.

The same thing happens at 40px by 40px; going to 80px by 80px seems to make things work.
Bug: Potentially confusing text on Protections drop-down regarding blocked cookies when site cookies are whitelisted
Status: RESOLVED
Priority: P3
Resolution: WORKSFORME
Created: 2020-02-28 21:16:40+00:00
Resolved: 2024-12-10 11:28:06+00:00

So I have all cookies blocked globally in my Firefox Nightly settings. I then whitelist sites I use frequently.  For example, under the `Protections for bugzilla.mozilla.org` drop-down, it shows 

```
Blocked
All Cookies >
```

(see https://i.imgur.com/1046uuK.png) and when you select `All Cookies` it shows https://bugzilla.mozilla.org (see https://i.imgur.com/qh5PlQe.png ). Which it really shouldn't, because if I select `Site information for bugzilla.mozilla.org` it shows that I have allowed the Set Cookies permission (see https://i.imgur.com/iJjTJ9j.png).
Bug: In full screen mode, the toolbar context menu does not allow toolbar customization or changing bookmarks toolbar visibility
Status: NEW
Priority: P2
Created: 2020-02-29 01:53:58+00:00
Resolved: 2021-07-19 03:09:41+00:00

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

Steps to reproduce:

Open context menu on tool bar in full screen mode.


Actual results:

The context menu shows wrong items.


Expected results:

I expected items like non full screen mode.
Bug: new tab page shows sponsored content in wrong language
Status: RESOLVED
Priority: P1
Resolution: WONTFIX
Created: 2020-02-29 13:15:01+00:00
Resolved: 2020-03-30 17:39:47+00:00

There is sponsored content in the Pocket section of the new tab page. But the sponsored content does not follow the language of Firefox. I attached a screenshot that shows a German Firefox with German Pocket stories and an English sponsored story. This one is not the only one in English I saw today. Firefox should never show content in the wrong language because not everyone speaks English.

(I am using Firefox Nightly 75)
Bug: Continuously crashing on certain websites (http3 SIGSEGV)
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2020-02-29 16:14:12+00:00
Resolved: 2020-04-23 17:34:26+00:00

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

Steps to reproduce:

Firefox immediately crashes on opening some websites like cloudflare.com when http3 is enabled.
Disabling "network.http.http3.enabled". Fixes the problem.

Firefox 73.0.1 (64-bit) on Ubuntu 18.04 LTS

Here's the crash report.
https://crash-stats.mozilla.org/report/index/bp-0dfba583-59b9-4168-b00e-a702d0200229


Actual results:

Firefox immediately crashes on opening some websites like cloudflare.com when http3 is enabled.


Expected results:

Firefox shouldn't be crashing with http3 enabled.
Bug: The settings button for "Use custom settings for history" is greyed out.
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-02-29 17:12:04+00:00
Resolved: 2020-03-13 14:28:09+00:00

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

Steps to reproduce:

1. Try to set up setting for "Use custom settings for history"
(as shown over there https://www.groovypost.com/howto/automatically-delete-firefox-history-cookies-temp-exit/ , for instance)
so about:preferences#privacy / History
2. Select "Use custom settings for history" in the "Firefox will" option.


Actual results:

The "Settings..." button is greyed out.


Expected results:

The "Settings..." button is NOT greyed out.
Bug: click login button nothing to do
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2020-02-29 22:02:30+00:00
Resolved: 2020-03-20 08:47:19+00:00

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

Steps to reproduce:

I use firefox nightlu 75.0a1

1、visit this website : http://www.qidian.com

2、click login button ( top right corner ) and input my account info

3、click login button

chinese version :

1、访问该网站：http://www.qidian.com

2、点击右上角的登录按钮，输入账号面

3、点击登录


Actual results:

nothing to happend

chinese version :

什么都没发生，没有登录成功


Expected results:

only chinese version :

登录成功之后右上角应该显示的是昵称，而不是登录两个字。
Bug: The gray box with "Timed Out" on it on all websites.
Status: RESOLVED
Priority: P1
Resolution: INCOMPLETE
Created: 2020-02-29 23:02:19+00:00
Resolved: 2021-03-27 17:51:29+00:00

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

Steps to reproduce:

The little gray box saying "Timed Out" occurs as a bug this day.


Actual results:

A little gray box with "Timed Out" was seen at the lower-left hand corner of the browser, meaning that there's a bug in the loading / connecting / performing TLS handshake bar. If you move the cursor towards it, the bar will move the right hand corner of the screen, but will revert to the left hand. Anyone else has the same?


Expected results:

It happened today.
Bug: I found a bug (security vulnerability) in browser that can compromise devices, laptops, mobiles etc
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2020-03-01 00:00:13+00:00
Resolved: 2024-05-30 17:12:07+00:00

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

Steps to reproduce:

Visit this or any similar website used for hackers; website; https://www.y2mate.com/youtube/oQnqWAEReoY. Then click to download any video/item. 


Actual results:

The hacker (Website) after downloading any video/item opens a new tab automatically & redirects url to different sites & runs a malicious code that can compromise computers, mobiles etc.

In Laptop i tested the malware: The code gets inside in Temp folder & in RAM. When we delete temp folder, the program/malicious code is not deleted from RAM so it again gets into temp folder without getting installed in C-Drive like other applications. If we format & reinstall C-Drive from Windows OS, the code from RAM again infects temp folder.Thus it is difficult to be detected & it is also difficult to get removed. 

website; https://www.y2mate.com/youtube/oQnqWAEReoY 
Issues: Out-of-limit memory access in transmissions AND allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. Plus many other issues seen. 


Expected results:

Malware is installed without user permission in temp folder & RAM usually missed by anti virus, windows defender etc.
Bug: Firefox don't listed in context menu "open with..." with file type .jpg extension
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2020-03-01 08:01:18+00:00
Resolved: 2020-11-06 19:53:30+00:00

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

Steps to reproduce:

With version 73.0.1 Firefox. Right click on file with .jpg extension


Actual results:

Since installation of version 73.01, Firefox is no longer offered in the list of the context menu "Open with ..." when you right-click on a .jpg file


Expected results:

Firefox should have been offered in the list of applications in the context menu "Open with ..."
Bug: Intermittent browser/components/newtab/test/browser/browser_discovery_card.js | Uncaught exception - undefined - timed out after 50 tries.
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2020-03-01 11:41:49+00:00
Resolved: 2025-01-20 12:10:05+00:00

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

---

[task 2020-03-01T10:58:47.028Z] 10:58:47     INFO - TEST-START | browser/components/newtab/test/browser/browser_discovery_card.js
[task 2020-03-01T10:59:00.019Z] 10:59:00     INFO - Buffered messages finished
[task 2020-03-01T10:59:00.019Z] 10:59:00     INFO - TEST-UNEXPECTED-FAIL | browser/components/newtab/test/browser/browser_discovery_card.js | Uncaught exception - undefined - timed out after 50 tries.
[task 2020-03-01T10:59:00.019Z] 10:59:00     INFO - Leaving test bound test_card_render
[task 2020-03-01T10:59:00.019Z] 10:59:00     INFO - GECKO(3217) | MEMORY STAT | vsize 7756MB | residentFast 430MB | heapAllocated 129MB
[task 2020-03-01T10:59:00.020Z] 10:59:00     INFO - TEST-OK | browser/components/newtab/test/browser/browser_discovery_card.js | took 12875ms
[task 2020-03-01T10:59:00.020Z] 10:59:00     INFO - GECKO(3217) | [Child 3219: Main Thread]: I/DocShellAndDOMWindowLeak ++DOCSHELL 0x124d3a000 == 2 [pid = 3219] [id = {4ebaa327-f39e-094a-b50b-c947f08dbfc5}]
[task 2020-03-01T10:59:00.020Z] 10:59:00     INFO - GECKO(3217) | [Child 3219: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 3 (0x124df4480) [pid = 3219] [serial = 23] [outer = 0x0]
[task 2020-03-01T10:59:00.020Z] 10:59:00     INFO - GECKO(3217) | [Child 3219: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 4 (0x110718c00) [pid = 3219] [serial = 24] [outer = 0x124df4480]
[task 2020-03-01T10:59:00.020Z] 10:59:00     INFO - GECKO(3217) | [Child 3219: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 5 (0x125d13c00) [pid = 3219] [serial = 25] [outer = 0x124df4480]
[task 2020-03-01T10:59:00.020Z] 10:59:00     INFO - checking window state
Bug: The ARES-6 benchmark fails when restored from previous session
Status: REOPENED
Priority: P3
Created: 2020-03-01 18:12:59+00:00
Resolved: 2023-11-12 01:22:58+00:00

The ARES-6 benchmark crashes on start.

Steps to reproduce:
1. Open https://browserbench.org/ARES-6/index.html
2. Click START.

The "START" button text changes to "Test failure — error in console", and the console displays:
```
Error encountered:  ReferenceError: AirBenchmark is not defined https://browserbench.org/ARES-6/index.html line 170 > scriptElement 32 17 ReferenceError: "AirBenchmark is not defined"
    <anonymous> https://browserbench.org/ARES-6/index.html line 170 > scriptElement:32
    _iterate https://browserbench.org/ARES-6/driver.js:170
    setTimeout handler*_iterate https://browserbench.org/ARES-6/driver.js:161
    start https://browserbench.org/ARES-6/driver.js:73
    driver https://browserbench.org/ARES-6/glue.js:31
    readyTrigger https://browserbench.org/ARES-6/driver.js:49
    <anonymous> https://browserbench.org/ARES-6/glue.js:54
```
followed by a bunch of warnings like:
```
‘src’ attribute of <script> element is not a valid URI: “Air/symbols.js”
```

The benchmark fails in Nightly 75.0a1 (2020-02-29) & 75.0a1 (2020-03-01). It worked in recent Nightly versions, I think even in the immediately preceding one to the one from 2020-02-29.
Bug: Intermittent browser/components/urlbar/tests/browser-tips/browser_updateAsk.js | 2 == 7 - JS frame :: chrome://mochitests/content/browser/browser/components/urlbar/tests/browser/tips/head.js :: awaitTip :: line 292
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2020-03-01 22:10:14+00:00
Resolved: 2020-05-26 17:04:50+00:00

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

---

>[task 2020-03-01T21:31:57.468Z] 21:31:57     INFO - TEST-PASS | browser/components/urlbar/tests/browser/tips/browser_updateAsk.js | There should not be an active update - true == true - 
[task 2020-03-01T21:31:57.468Z] 21:31:57     INFO - TEST-PASS | browser/components/urlbar/tests/browser/tips/browser_updateAsk.js | true == true - 
[task 2020-03-01T21:31:57.468Z] 21:31:57     INFO - Buffered messages finished
[task 2020-03-01T21:31:57.468Z] 21:31:57     INFO - TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/browser/tips/browser_updateAsk.js | 2 == 7 - JS frame :: chrome://mochitests/content/browser/browser/components/urlbar/tests/browser/tips/head.js :: awaitTip :: line 292
[task 2020-03-01T21:31:57.468Z] 21:31:57     INFO - Stack trace:
[task 2020-03-01T21:31:57.469Z] 21:31:57     INFO - chrome://mochitests/content/browser/browser/components/urlbar/tests/browser/tips/head.js:awaitTip:292
[task 2020-03-01T21:31:57.469Z] 21:31:57     INFO - chrome://mochitests/content/browser/browser/components/urlbar/tests/browser/tips/head.js:doUpdateTest:227
[task 2020-03-01T21:31:57.469Z] 21:31:57     INFO - chrome://mochitests/content/browser/browser/components/urlbar/tests/browser/tips/browser_updateAsk.js:test:58
[task 2020-03-01T21:31:57.469Z] 21:31:57     INFO - chrome://mochikit/content/browser-test.js:Tester_execTest/<:1062
[task 2020-03-01T21:31:57.469Z] 21:31:57     INFO - chrome://mochikit/content/browser-test.js:Tester_execTest:1097
[task 2020-03-01T21:31:57.469Z] 21:31:57     INFO - chrome://mochikit/content/browser-test.js:nextTest/<:925
[task 2020-03-01T21:31:57.469Z] 21:31:57     INFO - chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<:914
[task 2020-03-01T21:31:57.469Z] 21:31:57     INFO - Not taking screenshot here: see the one that was previously logged
Bug: LinkHandlerChild has a useless "dispatcher" constructor argument
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2020-03-01 23:46:21+00:00
Resolved: 2020-03-05 22:11:42+00:00

All it does with it is pass it to `super()`, but `JSWindowActorChild` does not take any constructor arguments.

Possible regression from bug 1592157?  Before that it looks like the superclass was `ActorChild`, which actually does expect a dispatcher.
Bug: RUN xss PAYLOAD javascript:alert(1);
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-03-02 05:56:06+00:00
Resolved: 2020-03-02 10:06:39+00:00

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

Steps to reproduce:

Open the browser
click mune
go to bookmarks
add bookmark url javascript:alert(1);
click bookmark 



Actual results:

alert box


Expected results:

Javascript application in the browser
Bug: The user is able to add a separator to the Address Bar
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2020-03-02 10:08:18+00:00
Resolved: 2020-03-05 17:59:07+00:00

**Affected versions**
- Firefox 68.5.0esr
- Firefox 73.0.1
- Firefox 74.0b9
- Firefox 75.0a1

**Affected platforms**
- Windows 10 & 7
- Ubuntu 18.04
- macOS 10.15 & 10.13

**Steps to reproduce**
1. Launch Firefox
2. Open a page, for example [Wikipedia](https://www.wikipedia.org) to trigger the extra controls from the Address Bar
3. Access the dropdown from the three dots and spam right click on the separator until the popup with Add to address bar is shown

**Expected result**
- The separator can't be added to Address Bar

**Actual result**
- The separator can be added to the Address Bar

**Regression range**
- I will see for a regression range.

**Additional notes**
- The issue can be seen in the attachment.
- There are only some points on the separator which will trigger the Add to address bar option.
Bug: [Protection Report] The icon of the Mobile Call Out Card not visible enough in High Contrast Mode
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2020-03-02 15:34:40+00:00
Resolved: 2020-04-29 09:05:00+00:00

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Build ID: 20200302094818

**Affected versions**
Nightly 75.0a1

**Affected platforms**
* Windows 10 x64
* Windows 7

**Prerequisites:**
* Start menu -> Settings - Turn high contrast on or off - Enable the high contrast and choose one of the dark themes
* In about:config change the pref "browser.contentblocking.report.show_mobile_app" to "true"

**Steps to reproduce**
1. Open Firefox.
2. Go to about: protections
3. Observe the "Mobile Call Card" icon

**Expected result**
* The "Mobile Call Card" icon is correctly displayed. 

**Actual result**
* By comparison to other icons on the page, the icon of the "Mobile Call Card" is not properly displayed - the mobile shape is not visible enough.

**Additional notes**
* For more details, please see the screenshot.