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

> As I mentioned in my first post, **built-in components run into these issues as well, we've just accepted that this is how things are supposed to be**.

No question about it, they are limiting, and I don't know exactly why, but I'm not an implementer! I will assume, that if you are implementing a `<fancy-input type=number>`, I will expect 2 things: a) the ability to use `::part()` to style, in some degree, the arrow buttons, and b) Two slots to replace the arrow buttons all together. I will not assume that the default content of the two slots will be fully customizable from outside without replace them all together by providing content for the slots. In other words, a) from above is to get you to the "good-enough" customization that can cover majority of the cases, while b) is to get you to the "pixel-perfect" customization that is rare.

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

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