Re: [w3c/webcomponents] Remove `Callback` suffix from custom elements callbacks (#414)

I have to admit that I was thinking in the past:
```
Don't care of name conflict, if you use my library, you should know the names I provide! 
Even if it's overrided ones! And take care of your naming to don't conflict with the library.
```
But I changed my mind since I read about new `Symbol` type. The point is not about naming conflict, but more about namespacing. Kinda "hide" some API for user to don't worry about it.
A library author may want to configure the custom element with this symboled method or property, and expose only high level API for the component that internaly use the symbols. The component inspection would not show the symbols property ( I know that it's still accessible with `Object.getOwnPropertySymbols` ) because it need's the user to use some component API and not the native directly (let's say for custom behavior).

PS: I continue to answer here because the discussion about symbols it's interesting, but I don't really mind of symbolised CEReactions ...

-- 
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/414#issuecomment-274333276