Re: [WICG/webcomponents] Web components should be able to easily adapt to the host page while maintaining enapsulation (Issue #986)

Okay here's an attempt at breaking this down in a reasonable way:

All web components have two types of elements:
1. Light-DOM elements, which constitute the "actual" content which is interesting to the user and
2. Decorative elements that constitute the actual functionality of the component additionally to that of the elements in 1.

In the case of a light-dom input box, the "interesting" content is the text-input, which already gets styled from the outside. We can ignore this as it already works.

In the case of an image carousel, the interesting content are the images, provided by the HTML author, but the forward/backward control buttons are part of the additional functionality that the component provides. **This is what we care about**.

As has been shown above, putting these in the light-DOM is not optimal, because they're functionality that the component is supposed to provide.

This distinction into "user-provided" and "component-provided" functionality and elements seems (to me at least) universal to all the possible applications of web components, even if at a different split.

And I really hope that we can now continue to discuss the actual use-case, because if the discussion continues this way there won't ever be an actual resolution.

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

Message ID: <WICG/webcomponents/issues/986/1472178602@github.com>