Video Full Screen Mode: Mouse Event Not working
Reported by
robindra...@impressico.com,
Feb 8 2018
|
|||||||
Issue descriptionChrome Version : Version 64.0.3282.140 (Official Build) (64-bit) URLs (if applicable) : http://discovertheweb.co.in/auto-play-demo/ OS version : ALL Network (such as Cable/DSL/Dial up etc): Audio/Video format (if applicable): Special chrome flags (if applicable): Behavior in Safari (if known): Working As Expected Behavior in Firefox (if known): Working As Expected Video issue, Audio issue, both, neither? <b>Flash or HTML5? <right-clicking most players will either reveal some text</b> with “Flash”; otherwise likely HTML5> If the browser or renderer crashed (“Aw, Snap”), please add any crash IDs from chrome://crashes (possibly after enabling crash reporting per http://support.google.com/chrome/bin/answer.py?hl=en&answer=96817) What steps will reproduce the problem? (1) Open the shared URL (http://discovertheweb.co.in/auto-play-demo/) (2) Now Play the video and click on the Testing Button, in iniline, an alert will popup. Also scroll the content inside the div it works (3) Now, play the video in full screen and repeat the step 2, now none of the mouse event working neither click nor scroll. Everything was working till Chrome Version 63 but the issue has been started once we update to 64+ version. What is the expected result? Expect to work all the mouse event What is the actual result? All Mouse event has been disabled Any additional information (anything else which may help us debug the issue)? Please attach the HTML5/JavaScript code or audio/video files as well as screenshot and/or videos (if applicable)
,
Feb 9 2018
Hi, Please find the issue number Issue 810646 (https://bugs.chromium.org/p/chromium/issues/detail?id=810646)
,
Feb 9 2018
Issue 810646 has been merged into this issue.
,
Feb 9 2018
,
Feb 12 2018
Able to reproduce this issue on reported version 64.0.3282.140, latest beta 65.0.3325.51 and on latest canary 66.0.3344.0 using Mac 10.13.3,Windows 10 and Ubuntu 14.04. i.e; When in fullscreen mode unable to click on button and unable to scroll iframe. Good Build: 64.0.3282.3 Bad Build: 64.0.3282.31 Unable to do per-revison or chromium bisect for branched builds. Hence providing manual changelog. CR: https://chromium.googlesource.com/chromium/src/+log/64.0.3282.3..64.0.3282.31?pretty=fuller&n=10000 Reviewed-on: https://chromium-review.googlesource.com/824949 Suspecting above from changelog. @chrishtr: Please confirm the bug and help in re-assigning if it is not related to your change. Adding RB-Stable for M-64, Please change if not the case. Thanks!
,
Feb 12 2018
Issue 811072 has been merged into this issue.
,
Feb 12 2018
,
Feb 12 2018
Bisect: https://chromium.googlesource.com/chromium/src/+log/7631d3573c37329b0938be489a78a7689e552e31..17dd72fb55aaa071bf1077a02e45b9f2f44d1ed2 Culprit is https://chromium.googlesource.com/chromium/src/+/17dd72fb55aaa071bf1077a02e45b9f2f44d1ed2
,
Feb 13 2018
The problem here is that the <div class="layout-on-top"> is a sibling of the fullscreen element as opposed to a child. With the change linked in #8 all elements except the fullscreen element and its descendants become inert, which is why it becomes impossible to interact with them. The other fix to issue 736832 that was discussed was to wait for issue 240576 , which is about implementing https://fullscreen.spec.whatwg.org/#top-layer. That's still planned, an in addition to making the <div class="layout-on-top"> inert it will also no longer be shown above the fullscreen element, as no z-index will "win" over top layer. I recommend putting the <div class="layout-on-top"> *inside* of the fullscreen element, which should work now and continue to work after issue 240576 is fixed. I can't see a path for keeping the pattern in the demo working without also breaking issue 736832 and requiring fullscreen to be redefined spec-side in terms of z-index, so I'm going to WontFix this and hope it's not a common pattern, but please comment further if I've overlooked something.
,
Feb 26 2018
,
Apr 3 2018
Issue 821576 has been merged into this issue.
,
Apr 4 2018
I don't understand how this bug is in WontFix state Solving some bug in Android for accessibility doesn't need to effect desktop users of chrome. Not allowing this functionality harms a lot of companies that provide platforms for video annotation and quizzes etc, It hurts these companies and their clients. The workaround is not a wide solution for all the types of video players. This issue is simply a huge irresponsible from the chrome developers part ! |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by manoranj...@chromium.org
, Feb 8 2018