Open Bug 1552416 Opened 6 years ago Updated 3 years ago

Can't click on some button without first having to go in another tab.

Categories

(Firefox :: General, defect, P5)

defect

Tracking

()

Tracking Status
firefox68 --- affected

People

(Reporter: jya, Unassigned)

Details

There are two scenarios where this happens if not all the time, at least it's very regular.

A button is presented in the page, however clicking on it does nothing. If I click on another tab however and then go back to the previous tab where the button was, then I can click on it.

Scenario 1.
Using the Firefox multi-account container. Open a new tab in a specific container, and once the page is loaded, right click on the page and select "Firefox Multi-Account container" -> "Always Open in this Container".

Now close the tab. Open a new tab with no container.
You get a page stating something like:
"

Open this site in your assigned container?

You asked Firefox to always open Personal for this site:
http://www.domain.org/

Would you still like to open in this current container?

Remember my decision for this site
"

With two buttons: "Open in current container" and "Open In Personal Container".

Clicking on the "Open in Personal Container" will do nothing when you click on it, even though it gives visual feedback that it's been clicked on.
Now select another tab in the same window, then go back to the tab with the container prompt. Now clicking on "Open in Personal Container" will work and the page will open.

Scenario 2:
In IRCCloud, paste a multi-lines message.
A new popup shows to post the snippet with a button in the bottom left "Post Snippet".

Clicking on that button does nothing, but change tab and come back and now it works.

I can reproduce Scenario 2 all the time, running Nightly "68.0a1 (2019-05-16) (64-bit)" on Windows 10 1809.

Any errors in the browser console? Could you please find a regression range?

Flags: needinfo?(jyavenard)
Priority: -- → P5

I can't consistently reproduce with moz-regression.

It happens intermittently on the sessions started with moz-regression. But I can get it to fail reliably on my local machine even in a clear profile.

Flags: needinfo?(jyavenard)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.