Re: [w3c/pointerlock] pointerlockchange is cancelable, breaking the processing model (#9)

Right @annevk and @scheib , the default cancelable attribute in EventInit dictionaries is false but nothing in the spec says the event is never cancelable so it's still  possible to create programmatically such an event with the cancelable flag to true in the eventInitDict and dispatch it. The fact the spec says nothing about the handling of the canceled flag is an ambiguity in the spec and I see it as an underspecification that could lead to issues on the users' side and even possibly on the browsers' side. If all brower vendors agree these events should never be cancelable/canceled, its should be in the spec. So, yes, I still think a spec change is needed. It's a cheap change and IMO a very useful clarification.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/pointerlock/issues/9#issuecomment-250088546