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

As far as I know, Chrome has already shipped v1 custom elements API to public in their stable release, so it's a bit too late to change this semantics. Although we've replaced v0 with v1 but that was because other browser vendors had a significant problem with it, and new API had some benefits (e.g. integration with ES6 class syntax). Also note that we've implemented the v1 API and turned it on by default on Safari Technology Preview.

In contrast, using `Callback` suffix was discussed multiple times in the past, and we had reached a consensus on this matter a while ago so unless there is a strong support from multiple browser vendors for making this change, I don't think it will happen.

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