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

@web-padawan I know about the spec. But why we can't config it in manfest or other way to tell browser we needs custom the buildin element? Why some thing jQuery can do, many developer can do, W3C can't?

I can enhance the `input` by jquery only one line code`$('input').enhance();

but with webcompoennts, I needs change `input` to `hrlink-input`, when i have more than 100 forms, this is not an easy job。

and if i use some element likes `paper-calendar`, and days after, customer likes `abc-calendar`, is this change so easy for a large **form based application**？

If we have no way to change it, I will bear it. If we can change it，why don‘t do it？

By this the reason, why W3C no way to define a custom element without javascript,
just for decoration & data binding？Is means `Custom Element` means `Javascript Compoent`?
About this kind of `Custom Element`, without performance, where better than the jQuery way?
So i think custom element may not yet be completed. 
And i believe that in the future， custom will make the web more better than now.

> condider the fact that user can disable JavaScript and DOM would still be rendered



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