Skip to content

Section 2.1 should mention the effect of lock on PointerEvents #97

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mustaqahmed opened this issue May 28, 2024 · 1 comment
Open

Comments

@mustaqahmed
Copy link
Member

mustaqahmed commented May 28, 2024

This came up in this thread on #49:

Would it be possible to list these events normatively, instead of only giving some examples?

I think the current text is OK, because the lack of precision here is just a symptom of the larger lack of precision in how mouse events are specified in general. Some progress is being made there, in w3c/uievents#200, and if that lands then eventually this paragraph can move into the UI events spec as an actual change to the processing model.

But in the meantime, it would help achieve interoperability if you were precise about the list of events.

For example, it's not clear to me whether pointer events are impacted by this change.

@masayuki-nakano
Copy link

masayuki-nakano commented Aug 1, 2024

FYI: This test (for Pointer Events) expects that lostpointercapture, pointerout and pointerleave are fired on the capturing element before the pointer lock and pointerover and pointerenter are fired on the pointer locking element.

Sorry for the spam. The test is not related to the pointerlock. I was confused with other tests which I'm currntly debugging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants