If I pursue your suggestion of what the browser might want to do, then taking: > and so the browser might want to make the default API hidden behind a power-user mode If the browser **might** want to do anything that involves hiding UI (and this is a very likely outcome and seems to express the semantic intent of `preventDefault()`) then it **must** wait for this signal, which means this event **will** block the user experience because the browser won't know whether that signal might come in until the event has been fully dispatched. That's the part I'm having trouble with. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/236#issuecomment-380609314
Received on Wednesday, 11 April 2018 22:00:01 UTC