Closed Bug 1656518 Opened 5 years ago Closed 5 years ago

The first click on specific CFR-feature buttons does not work if the browser is unfocused

Categories

(Firefox :: Messaging System, defect)

Desktop
All
defect

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox79 --- wontfix
firefox80 --- wontfix
firefox81 --- wontfix

People

(Reporter: romartin, Unassigned)

Details

Attachments

(1 file)

Attached image 2020-07-31_20h14_36.gif

[Affected Versions]:

  • Firefox Release 79.0 (Build ID: 20200720193547)
  • Firefox Beta 80.0b2 (Build ID: 20200730152159)
  • Firefox Nightly 81.0a1 (Build ID: 20200731094606)

[Affected Platforms]:

  • Windows 10 (x64)
  • Ubuntu Linux 18.04
  • macOS 10.15

[Prerequisites]:

  • Have the browser.newtabpage.activity-stream.asrouter.devtoolsEnabled pref set to true.
  • Have the browser.ping-centre.log pref set to true.
  • Have the Browser Console opened.

[Steps to reproduce]:

  1. Start the Firefox Browser with the set-up from prerequisites.
  2. Open an “about:newtab” page and click the “Expand devtools” button.
  3. From the “Messages” section, select “cfr”.
  4. Scroll down to “CRYPTOMINERS_PROTECTION” and click the “Show” button.
  5. Focus a different window and click any button from the doorhanger.
  6. Observe the behavior and the Browser Console.

[Expected results]:

  • The action meant for the button is performed.

[Actual results]:

  • The button does nothing and an error can be observed in the browser console.

[Notes]:

  • On macOS 10.15, and Ubuntu Linux 18.04 the issue can be reproduced for the “Close” button and for the “See Protections” button.
  • Attached a screen recording with the issue.
  • The browser console errors that appear are the following:
    • “ TelemetryStopwatch: finishing nonexisting stopwatch. Histogram: "FOG_EVAL_WINDOW_RAISED_S", key: "" “
    • “ TelemetryStopwatch: key "FOG_EVAL_WINDOW_RAISED_S" was already initialized “
OS: Windows → All

Andrei, is there any chance this behavior on Windows is intentional?

Flags: needinfo?(andrei.br92)

We don't own the PopupNotification code, I can't say what the desired behavior is. It doesn't seem to me that this behavior is affecting interaction with the dropdown (there is no accidental dismiss), I don't think it's worth taking any action on this.

Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(andrei.br92)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: