1347375 - Sometimes items in context menu aren't visible in insecure fields (covered by "Logins entered here could be compromised" notification)

Status: RESOLVED DUPLICATE of bug 1337772

(Firefox :: Security, defect)

Description

[684sigma]

Attachment: screenshot, by reporter.png

I have a problem with Firefox Beta 53. It doesn't happen in Firefox 51.
Sometimes notification "Logins entered here could be compromised" appears above context menu when I right-click in password field, depending on how fast right-click happens.
Sorry, I don't want to tell you exact sites I visit, but it this scenario should work

1. Open http://example.com in a new tab and execute the following line in web console:
document.body.innerHTML=`<form method="post" action="/"><input name="L"><input name="P" type="password" size="12">`; document.querySelector("[name='P']").focus();
2. Quickly right-click the second input field on the page.
("Quickly" means that 'mousedown' should be immediately followed by 'mouseup')

Result: The notification appears above context menu, covering some of the menu items. I don't remember their order.
Expected: All menu items should be visible. Or the notification shouldn't appear at all.

As I've said in bug 1344390, I would appreciate any advice on removing the notification forever, because it seems annoying. In case I get the advice, I won't see the notification at all, so I won't ever encounter this bug, and it can be closed then.

Comment 1

[YF (Yang)]

I could not reproduce the cover problem, but see the notification flashes almost every time when right clicked on insecure fields.


(In reply to 684sigma from comment #0)
> As I've said in bug 1344390, I would appreciate any advice on removing the
> notification forever, because it seems annoying. In case I get the advice, I
> won't see the notification at all, so I won't ever encounter this bug, and
> it can be closed then.

security.insecure_field_warning.contextual.enabled to false.

Because I said problem on the above, keep this bug open.

Comment 2

[Matthew N. [:MattN]]

This is a known issue being fixed in bug 1337772