Re: [css-houdini-drafts] [css-layout-api] issues with (optional) caching of intrinsic size computation and generated fragments (#841)

> Also, I wonder if it's a problem to optionally cache these things. If an author writes a layout that uses some external data, like Math.rand(), two UAs could easily behave differently if one does caching and the other doesn't, and they have different strategies for optimizing out reflows.

This is somewhat mitigated with the global scope switching (randomization). There are lots of things we don't have compat on here (which previously hasn't been exposed), e.g. number of passes to determine scrollbars, etc.

Our experience with paint so far is that switching the global scope randomly works pretty well to encourage developers to write idempotent code.

-- 
GitHub Notification of comment by bfgeek
Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/841#issuecomment-441736196 using your GitHub account

Received on Monday, 26 November 2018 17:59:45 UTC