Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)

FWIW, I like every proposal as long as it works but I am having hard time to understand the plural as object property ... `styles` ... why is that?

  * the element to which you would define content is `<style>`, not `<styles>`
  * indeed you [create style elemenr](https://github.com/w3c/webcomponents/issues/468#issuecomment-203321502) as specified in this comment, so that `{style: sheet}` is more semantic than `{styleSheet: sheet}` (which is even worse than styles, IMO)
  * non mother-tongue English developers will stick with what they know, which is either `style` or `css` to style their components.
  * every framework I know uses the word `style`, never `styles`, here just [an example](https://vuejs.org/v2/guide/class-and-style.html#Object-Syntax-1)

As silly as this matter could look like, I think having `style` as property name doesn't need explanations, while having a plural form would mislead at least once most developers (those I know).

You don't "_styles_" a component, you "_style_" a component.

As non native, non mother-tongue, English developer, I think the correct naming would be a plus.

Thanks in advance for eventually considering this point of view.

-- 
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/468#issuecomment-324138340