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

Anything else? Maybe that's huge for someone but we (where I work) avoid
ShadowDOM at all costs due polyfills shenanigans and also due the ease to
style Custom Elements through regular CSS. We need to be careful with rules
for when we put components inside other components, and we'd love to
explicitly assign CSS per component on definition level so that such
component would works even inside other ShadowDOM elements.

As summary: why isn't this proposal working exactly like a <style> inside a
shadow root so that anything can be styled within the component and not
just the component itself which is super limited as it is?

This way nobody can reuse a style dedicated to a component to define its
view in a single place, including its optional children.

Any component with just an `input` in it will never be able with ease to
define a non browser-centric layout, unless custom builtins extend are
allowed.

Is there any chance this can be more useful?

On Tue, Oct 16, 2018 at 2:53 PM Rakina Zata Amni <notifications@github.com>
wrote:

> I don't see any benefit then, over a generic my-element {} set on the
> global style definition.
>
> That wouldn't work if the custom element is inside a shadow tree, for
> example.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/webcomponents/issues/468#issuecomment-430225339>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAFO9WJTbxY4juZAFctqoXdek6eHrLJIks5uldasgaJpZM4H7C23>
> .
>


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