Post

Alex Russell
@infrequently.org

Lots of folks fell for the "DOM is slow" marketing of certain frameworks, but DOM isn't slow. *Uncontrolled style read-back* is. But what if that wasn't a thing? Looking for feedback on a new proposal to control layout thrashing here: github.com/MicrosoftEdge/MS…

github.comMSEdgeExplainers/EventPhases/explainer.md at main · MicrosoftEdge/MSEdgeExplainersHome for explainer documents originated by the Microsoft Edge team - MicrosoftEdge/MSEdgeExplainers
Mauro
@mb21.bsky.social

The meta property proposed is nice. But I wonder whether adoption will hit the same problem like CSP meta tags: marketing will insist on their tracking script and we just cannot add the meta tag. Could we instead opt in an entiry third-party script and all its event handlers into this kind of mode?

Alex Russell
@infrequently.org

We went through the same problems with MOAR TLS, and it's fair to say that browsers need to make sure the juice is worth the squeeze. Restricting new APIs to only work under this mode is an obvious first step, and one CSP hasn't benefited from.

0 reposts1 like

Mauro
@mb21.bsky.social

Yeah, the stick is always an option. But I meant an attribute like async that web devs can put on the script tag of their third-party scripts they have no control over. It would put the whole script in a dom-read-only mode, or increase the batch size so that the main thread would yield less often.