Re: [w3c/webcomponents] observedStyles (#856)

> Again it is not clear to me that this should be part of the element API. I’d rather be realizing this example through the Houdini Layout API, using a registered worklet. But I think it’s a good illustration of a use case in this space.
>
> Note that even if one does not consider it valuable to keep attributes concerned with semantics and css properties concerned with style, attributes would not help for items that require interpretation as CSS values (referencing vars, resolving lengths, etc).

These properties are unique in that they’re specific to this custom element. As far as I know, there is no built in CSS property which only applies to a specific element and affects it’s behavior.

But again, this is too close to a particular solution. To keep my analogy to a mode transportation, this is like saying NYC runs subway 24 hours with specific trains & stations. That’s not really defining the underlying use cases. We need to step back and ask *why* anyone is using CSS properties to define these things.

-- 
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/856#issuecomment-558397121