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

Not sure what you mean by "extremely compelling reason", in what other way can we design custom elements that responds to style changes? That by itself should be reason enough.
Like I said what if I want to design a slider with a custom css variable to let a user choose the orientation, how can I do it right now? I can see hundreds of reasons why being able to observe changes in styles would be useful, if observedStyles() is not the right way maybe something different but it seems like something that we should really be able to do. There is already the possibility to observe changes in the style attribute via mutation observer and that is also quite slow, doesn't feel like a good reason to remove it tho.

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