- From: Ryosuke Niwa <notifications@github.com>
- Date: Mon, 25 Nov 2019 14:38:30 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 25 November 2019 22:38:32 UTC
> Let's try to make it easier than, you don't need the old value of the style, a custom element should already know its own state (vertical, horizontal), can this be applied only to custom css properties, can a callback be fired whenever any style changes without telling me what has changed, we just need to know that something happened then we can check the computedStyle on whatever property we care about, something like that. It may surprise you but none of that makes this feature substantially easier to implement (at least in WebKit). But again, the difficulty of implementation is secondary. The primary thing we need is a list of concrete use cases. Nothing is gonna happen until we have that. -- 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-558372505
Received on Monday, 25 November 2019 22:38:32 UTC