Post

I like this. Wonder which pattern is most usable for devs!

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?

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.

Have you seen my tree-aware task scheduler idea? I think it could handle the read-after-write cases as well as help ensure coherence and prevent double rendering triggered from shared observable data sources: github.com/WICG/webcomp...

is that mentality still holds true among devs who came to frontend in the past ~5 years? I'm under impression that folks just don't think about it anymore and use frameworks to get their jobs done

Oh, my sweet summer child.

maybe that's my bubble, where do you get the data from?

What is 'uncontrolled style read-back'? Anywhere I can read about it?