Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New principle: Avoid exposing API that result in synchronous flushing of CSS or layout #388

Open
atanassov opened this issue Aug 8, 2022 · 1 comment

Comments

@atanassov
Copy link
Contributor

This was brought up in our discussion of exposing a new Range API..

During review of the issue, prior art of similar API, and guidance we have written our conclusions is that we need a new design principle. This is also closely related to the issue or better defining the HTML loop and what causes bucketing and flushing. At the very least we need to specify what forces layout or CSS to flush and provide some guidance on how to avoid it.

@plinss
Copy link
Member

plinss commented May 24, 2023

See also: w3ctag/design-reviews#734

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants