- From: Yoav Weiss <notifications@github.com>
- Date: Tue, 03 May 2022 03:19:39 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 3 May 2022 10:19:51 UTC
I believe what @xiaochengh meant is that Chromium exposes this to traces, which are [used](https://blog.webpagetest.org/posts/new-render-blocking-indicator-in-chrome-and-webpagetest/) by developer tooling, and found to be [useful by developers](https://sia.codes/posts/render-blocking-resources/). It's a different use case, but e.g. makes me think we should [web expose](https://github.com/w3c/resource-timing/issues/262) this info in Resource Timing. I agree that an internal flag would be sufficient for that. I guess that for web-exposing the flag on the Request object itself we'd need a Service-Worker case that e.g. treats scripts and style requests differently when they are render blocking. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/1433#issuecomment-1115943357 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/issues/1433/1115943357@github.com>
Received on Tuesday, 3 May 2022 10:19:51 UTC