Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567)

@Zambonifofex I think it's like `<button onclick="globalScope()">` VS the ability to define a specific callback/listener within a private/local scope instead of exposing it globally so that no conflicts, like you said, could possibly happen.

It is also kinda off topic at this point so you've done the right thing closing it.

-- 
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/webcomponents/issues/567#issuecomment-247133102