Navid Zolghadr

FYI @smaug---- Chrome had an unspecified behavior that blocked calculating click target over the interactive elements. This was never specified and nor implemented in other browsers like FF. Chrome 73...

``` @smaug---- Wrong user. ``` No. I meant to cc him. He is from Mozilla and worked on the same change on FF part.

@DanielRuf Let me look at this as part of https://bugs.chromium.org/p/chromium/issues/detail?id=941910

@DanielRuf do you by any chance know what has changed from https://materializecss.com/select.html to http://archives.materializecss.com/0.100.2/forms.html#select ? I don't know exactly which branch are those links from and the code is obfuscated...

I debugged the framework code a bit. I believe the better fix seems to be in the framework rather than restoring the old behavior of Chrome as we want to...

> This does not fix most cases, see https://codepen.io/DanielRuf/pen/rRENBm?editors=1010 and the two lines with // this will not work as this is still a regression bug in Chromium. I may...

> Okay, so my concern is calling fullscreen then pointerlock. And It works in Chrome. > Looks like Chrome does have special handling for pointerlock + fullscreen, https://source.chromium.org/chromium/chromium/src/+/master:chrome/browser/ui/exclusive_access/mouse_lock_controller.cc;l=63;drc=d5c9de46626708f710bed9634e1c598d4ac506fa Yeah. That...

I'm glad the fix works for you. But this library doesn't seem to be maintained by the owner anymore and hence why this change and others are just sitting with...

I'm not very familiar with this code. Can someone explain a little what that slider.pointerId is and what is so special about pointerId == 1? If something needs to be...

@Danila1985 I see. So you want to see whether a given pointer is active or not. Based on the spec setPointerCapture API is only supposed to work on [active button...