Issue metadata
Sign in to add a comment
|
user interactions (pointer events) not working on DOM element that is outside of DOM element that is in full screen.
Reported by
hen.a...@gmail.com,
Feb 25 2018
|
||||||||||||||||||||||||
Issue description
Chrome Version : Version 64.0.3282.186 (Official Build) (64-bit)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari: OK
Firefox: OK
Edge: FAIL
What steps will reproduce the problem?
(1) enter to this website for example : https://b2b-setup.annoto.net/demos/playground-flow.html
(2) Get to fullscreen mode
(3) try to move the Annoto widget
What is the expected result?
The Annoto widget can be moved
What happens instead?
Please provide any additional information below. Attach a screenshot if
possible.
The issue is related to user interactions (pointer events) not working on DOM element that is outside of DOM element that is in full screen.
```
<div id="DIV_A"></div>
<div id="DIV_B" style="z-index: 2147483647; position: absolute;"></div>
```
`DIV_B` is absolutely positioned element as an overlay on top of `DIV_A`.
The issue starts if `DIV_A` is entered into a fullscreen by for example means of `requestFullscreen()`.
`DIV_B` is still visible but it cannot be interacted with. clicking elements of `DIV_B` for example does not work the click event just goes throw `DIV_B` and is propagated to `DIV_A`.
Before versions 64 of Chrome everything worked fine.
The wanted behaviour is that `DIV_B` is visible and can be interacted with
`DIV_A` can be any element for example iframe or video
,
Feb 25 2018
,
Feb 26 2018
hen.aton@ Thanks for the issue. Tested this issue on Ubuntu 14.04, Mac OS 10.12.6 and Windows 10 on the Stable 64.0.3282.186 and Canary 66.0.3355.0 and able to reproduce the issue by following the steps mentioned above. Bisect Information: =================== Good Build: 64.0.3282.30 Bad Build : 64.0.3282.31 Providing the Changelog URL from Omahaproxy as this issue is regressed in Dot builds. Manual Changelog URL: ===================== https://chromium.googlesource.com/chromium/src/+log/64.0.3282.30..64.0.3282.31?pretty=fuller&n=10000 From the above Changelog, suspecting the below change: Reviewed-on: https://chromium-review.googlesource.com/810584 foolip@ Please check and confirm if this issue is related to your change, else help us in assigning to the right owner. Adding ReleaseBlock-Stable as this is a recent Regression. Please feel free to remove if it is not applicable. Thanks.
,
Feb 26 2018
This is a duplicate of issue 810308 , see https://bugs.chromium.org/p/chromium/issues/detail?id=810308#c9 for why I believe this should not be fixed. (In short, such elements shouldn't be visible at all, and relying on them being visible will soon break too.)
,
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 susan.boorgula@chromium.org
, Feb 25 2018