Focus on wrong window after fullscreen
Reported by
johan.bl...@gmail.com,
Oct 3
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: 1. Open the attached main.html file 2. Open console log in a separate window 3. Click the button on the webpage to open a popout window 4. Observe the log, the popout has focus and the main window does not 5. Click the button in the popout to enter fullscreen 6. Observe the log, the popout still has focus and the main window does not 7. Click the button in the popout to exit fullscreen 8. Observe the log, the main window got an onFocus event 9. Observe the log, both the main window and the popout window seems to be focused What is the expected behavior? 8. Did not expect to get an onFocus event in the main window, since focus is on the popout all the time 9. Did not expect that both the main window and the popout window report being in focus What went wrong? Both the main window and the popout window are in focus Did this work before? Yes 68 Does this work in other browsers? Yes Chrome version: 69.0.3497.100 Channel: stable OS Version: OS X 10.12.6 Flash Version: This reproduces 100% on my mac. My colleague has the exact same hardware, but on his mac the problem manifests itself slightly different. He gets the unexpected onFocus event already when entering fullscreen. This also reproduces 100%.
,
Oct 3
This is the log I get when running the steps described above: main.html:50 main focus true main.html:6 popout 2main.html:33 popout onFocus() main.html:42 main onBlur() main.html:50 main focus false main.html:37 popout focus true main.html:19 fullscreen main.html:50 main focus false main.html:37 popout focus true main.html:19 fullscreen main.html:46 main onFocus() main.html:50 main focus true main.html:37 popout focus true
,
Oct 3
,
Oct 4
Thanks for filing the issue! Able to reproduce the issue on reported chrome version 69.0.3497.100 using Mac 10.13.1 Tried Checking the chrome version 68.0.3440.106 as it is mentioned in C#0 "Did this work before? Yes 68". The issue is also seen on 68.0.3440.106, Attaching the screencast of the same for reference. @Reporter: Could you please have a look at the screen cast and let us know if the issue is present in mentioned 68.0.3440.106. Your confirmation helps us to triage the issue further in a better way.
,
Oct 4
Yes, you are right. I can reproduce the issue also on chrome 68. The latest version where I cannot reproduce it is chrome 66.
,
Oct 9
Can we bisect this one somewhere between 66 and 68?
,
Oct 19
,
Oct 21
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by johan.bl...@gmail.com
, Oct 32.0 KB
2.0 KB View Download