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

It's a bit more accurate to say that there's no real division between "v1" and "v2"; see https://wiki.whatwg.org/wiki/FAQ#What_does_.22Living_Standard.22_mean.3F to learn about the actual working mode. "Versions" are fiction in spec-land.

The things that are widely implemented and shipping are what will not change, and so far that's every part of the spec except customized built-in elements---although even those are under development in multiple browsers and so we'd need a very good reason to tell those browser vendors to throw away all the work they've done so far.

In general we don't make breaking changes to the web, unless required for security, and even then it's a long hard process with lots of teeth-gnashing ([example](https://bugs.chromium.org/p/chromium/issues/detail?id=669800)).

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