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

@WebReflection

> 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.

I see. However, behaviors would be a very shareable thing. I think it would have been rare to actually need a non‐global behavior.

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

I’m just kinda sad since I spent a lot of time designing this feature for it to be closed in less than five hours. I was really expecting to get more positive feedback.

I think that I closing the thread was more of a result of my disapointment than an actual thoughtful action. I’m really unsure whether I sould leave this closed or if I should reopen it. All I really want is to hear feedback from more than two people.

If anyone who might have been lurking/following this thread may not mind sharing their opinions, it’d be extremely appreciated.

-- 
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-247143890