- From: Peter Linss <notifications@github.com>
- Date: Mon, 20 Feb 2023 10:09:03 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 20 February 2023 18:09:16 UTC
Thanks for the response, we're going to close this review as satisfied, but we still have some concerns. Mainly, new mechanisms to block rendering need to be used very carefully by developers or they can easily fall into traps that result in a worse user experience (e.g. not realizing how slow user's devices and connections may be in the wild), so developers need to tread very carefully when using this and the additional complexity needs to be carefully explained. Furthermore, some of the use cases seem to be replicating existing capabilities that would be better handled declaratively. For example, using script to inject links to stylesheets in certain situations should rather be handled by CSS mechanisms like feature and media queries so the UA can scan for preloading opportunities, handling is not gated by script execution, etc. We do like the possible future extensions of being able to relax blocking in situation that are currently blocking. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/727#issuecomment-1437391646 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/727/1437391646@github.com>
Received on Monday, 20 February 2023 18:09:16 UTC