Re: [WICG/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624)

oelmekki left a comment (WICG/webcomponents#624)

> But the ultimate downside of self closing elements are that they are not backwards compatible so is it worth the migration effort? 🤷

Can you elaborate on why it would not be backward compatible? I haven't seen that mentioned yet, and that would indeed be a serious issue in a standard. Is it just a case of "older parser will not know what to do with it", as adding any new feature would be (and then, I guess we can count of the fact that parsers always expect broken HTML), or is there something more fundamental that would break also pages not using custom elements?

> This is the exact use-case that has kept me subscribed to this issue for years. I hope we get it someday.

I'm quite convinced it will happen at some point, just because of the amount of people asking for it, no matter how vocal the minority of opposants are (just like types annotation in ECMA, which people keep asking for over and over). My guess would be that the reason there isn't much more activity here yet is because most developers don't yet use custom elements, or not directly. I can see it becoming only more noisy as they becomes more mainstream.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/624#issuecomment-2885791684
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/624/2885791684@github.com>