Closed Bug 1753106 Opened 3 years ago Closed 3 years ago

Session restored uBO logger window is transparent to mouse events

Categories

(Firefox :: Session Restore, defect)

Firefox 98
defect

Tracking

()

RESOLVED FIXED
98 Branch
Tracking Status
firefox-esr91 --- unaffected
firefox96 --- unaffected
firefox97 --- unaffected
firefox98 --- fixed

People

(Reporter: gwarser, Assigned: emk)

References

(Regression)

Details

(Keywords: regression)

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

Steps to reproduce:

  • Manjaro KDE
  • fresh Nightly 20220201175554
  • enable session restore
  • disable title bar
  • install uBlock Origin
  • enable uBO logger (uBO button on toolbar -> list button) and switch it to windowed mode if maximized
  • switch to main window
  • open wikipedia (tile)
  • wait 15s (side note: logger will not be restored if you don't wait here - was it always like this?)
  • close main window
  • close logger window
  • open Firefox again
  • move mouse cursor over logger window, try clicking something

Actual results:

Main window under the logger window receives mouse events

Maybe regression from bug 1564738

Hmmm, I cannot reproduce in mozregression.

Also, I did maximized the main window after first start.

I was able to reproduce in mozregression after all and it really seem to be regression from bug 1564738

12:18.25 INFO: Running autoland build built on 2022-02-01 02:29:49.178000, revision e00a268f
12:25.53 INFO: Launching /tmp/tmp0meq_qs3/firefox/firefox
12:25.53 INFO: Application command: /tmp/tmp0meq_qs3/firefox/firefox --allow-downgrade -profile /tmp/tmpv5x47_gq.mozrunner
12:25.54 INFO: application_buildid: 20220201021450
12:25.54 INFO: application_changeset: e00a268f35f37e6fd48749bf3c3f5de42219112d
12:25.54 INFO: application_name: Firefox
12:25.54 INFO: application_repository: https://hg.mozilla.org/integration/autoland
12:25.54 INFO: application_version: 98.0a1
Was this integration build good, bad, or broken? (type 'good', 'bad', 'skip', 'retry', 'back' or 'exit' and press Enter): bad
12:35.10 INFO: Narrowed integration regression window from [c2642c27, edbc8f7e] (3 builds) to [c2642c27, e00a268f] (2 builds) (~1 steps left)
12:35.10 INFO: No more integration revisions, bisection finished.
12:35.10 INFO: Last good revision: c2642c279e9320d564247bd44d3b93930b0af870
12:35.10 INFO: First bad revision: e00a268f35f37e6fd48749bf3c3f5de42219112d
12:35.10 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=c2642c279e9320d564247bd44d3b93930b0af870&tochange=e00a268f35f37e6fd48749bf3c3f5de42219112d

I will try one more time to be sure.

Regressed by: 1564738

The Bugbug bot thinks this bug should belong to the 'Firefox::Session Restore' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Session Restore

Yeah, confirmed, mozregression -g 2022-01-31 --profile-persistence clone-first, retry first run and then simply click empty space in the logger just bellow first few logged lines - main window will be bring to front.

Has Regression Range: --- → yes
Has STR: --- → yes
  1. Is this not reproducible when the uBO logger window is restored by Ctrl+Shift+N?
  2. You cannot recover the problem once the bug happened?
  1. yes
  2. yes

Argh,

  1. it IS reproducible by Ctrl+Shift+N
  2. yes, I cannot recover when this happens

Thank you, but I could not reproduce the problem on Windows. Depends on the platform?

Depends on the platform?

Very likely KDE only. I cannot reproduce in VM in win10.

Set release status flags based on info from the regressing bug 1564738

gwarser, Could you test whether this try build works?
https://treeherder.mozilla.org/jobs?repo=try&revision=2f531d475ebfaeb9bfc2222a5b8bbb720aee8e82

  1. Click the B link to the right of "Linux x64 opt".
  2. Click "Artifacts and Debugging Tools".
  3. Click "target.tar.bz2" to download the try build.
    Or try the direct link to the build: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/St39ZDrRQYm61ti1zwAx-A/runs/0/artifacts/public/build/target.tar.bz2
Flags: needinfo?(gwarser)

Try build looks good. In both cases (original STR and Ctrl+Shift+N) window is working fine.

Flags: needinfo?(gwarser)

Hey gwarser,
Is this fixed for you? Should we close the ticket?

Flags: needinfo?(gwarser)

Yes, I think everything is fixed, can be closed.

Flags: needinfo?(gwarser)
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Assignee: nobody → VYV03354
Target Milestone: --- → 98 Branch
You need to log in before you can comment on or make changes to this bug.