> These properties are unique in that they’re specific to this custom element. The element in question is responsible for a layout effect, so yes — ideally though I could ditch the element, which isn’t used directly but only as an implementation detail for the widgets which are meant for direct consumption. In other words, custom elements are currently providing the only hook I know of for managing custom layout effects. The elements that ‘really’ use these CSS properties are diverse, including select, typeahead, tooltip, and dropdown menu widgets. I think I did make it very clear why we’re using CSS: the values are CSS values. They need to be able to handle CSS variables and resolve to CSS value types. -- 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-558406157
Received on Tuesday, 26 November 2019 00:40:09 UTC