Re: [w3ctag/design-reviews] Document Render-Blocking (Issue #886)

> Personally I have concerns about adding mechanisms that allow the author to block rendering. 

Those exists already, and most of them are far more powerful than render-blocking on an element.

> Authors will tend to test on faster devices and connections than most users have and are prone to unintentionally making the user's experience worse. (Let's all remember the blank pages people were staring at while fonts downloaded.)
> 
> Browsers already make a lot of tradeoffs trying to give the user the best experience, and authors can't predict the user's network conditions or device capabilities. I accept that the browser can't read the author's mind to know which content is more important to the user, so a mechanism that allows the author to set relative priorities rather than forced blocking seems like it would satisfy most of the needs here without the harms.

This wouldn't work for view-transitions, and a lot of this was discussed at length [here](https://github.com/whatwg/html/issues/9332).

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/886#issuecomment-1953197350
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/886/1953197350@github.com>