Re: [w3c/webcomponents] Why do we really need hyphens? (#658)

What @milieuChris said, this is really a namespace problem at the core and the technology that would allow us to "name things locally in any way we chose" was called XSLT (or XQuery or XProc to suit your needs). Developers didn't "want" this for various suspect reasons and without any such "response filter" mechanisms we are left to hardcoding our HTML directly in the output, reminding ourselves all this time that the "X" in these acronyms would stand for "extensible". It may not be the custom elements you want, but it is the custom elements we deserve and it is the custom elements we need: At least the resulting syntax is very explicit about the use magic it involves.

There's no reason why a high level framework cannot be rigged to output '<form>` as `<my-form>` when it can already render `<MyForm>` as a `<form>` (@baocang), so I'm still lacking some motivation for introducing this potentially confusing behavior into the one specification we have left :/

-- 
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/658#issuecomment-327409966