- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 13 Apr 2018 08:43:11 +0000
- To: public-houdini-archive@w3.org
tabatkins has just created a new issue for https://github.com/w3c/css-houdini-drafts: == [css-typed-om] Provide convenience methods to resolve lengths/etc == If you have a `<length>`-typed custom property, APIs that use TypedOM like the Layout API will give you the property as a computed value, so `vw`, `em`, etc all automatically resolve. However, if your property is too complex to give a type to, you have to deal with it as an untyped custom property. Then you don't have auto-resolved units; you parse it on your own, and then just have a "10vw" or whatever value, and no way to turn it into px. We should provide some convenience methods that allow this sort of thing to be resolved. (Separately, the other APIs that take in custom properties should have some way of taking a dependency on viewport size/font-size/etc automatically when a unit of the right type is used, and a way to manually register *within the callback* that you've ended up with a unit that needs that information, so you need to start invalidating based on it.) Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/754 using your GitHub account
Received on Friday, 13 April 2018 08:43:18 UTC