- From: Stephen Williams via GitHub <sysbot+gh@w3.org>
- Date: Fri, 26 Apr 2019 22:13:52 +0000
- To: public-css-archive@w3.org
Either I don't understand something or I am not communicating well: Your first paragraph seems to indicate that leaving these CSS variables non-registered would prevent the very problem that you are pointing out. Or at least non-registered in that complete, compute-now sense. The browser should not care that they contain a length when they are declared. They can simply be a string. The value only needs to be computed when a CSS property needs an actual value in layout, such as font-size: 2em. In the most straightforward implementation, the 2em wouldn't be replaced. If --em-map was set, the internal browser function that returns the pixel (or whatever is used) value for em would use the given mapping expression to return what em means at that point. Nothing else changes, no other accommodation is needed. I'll be publishing my PanResp method and library soon. And I'm going to look into creating a polyfill for this; should be an interesting challenge. -- GitHub Notification of comment by sdwlig Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3874#issuecomment-487217396 using your GitHub account
Received on Friday, 26 April 2019 22:13:54 UTC