Re: [w3ctag/design-reviews] Review request on Render Blocking Status in Resource Timing (Issue #753)

The main reasoning was to keep it open to being extended later on, if we wanted to provide more supporting information regarding render blocking.

Say we have a scenario where a plain script element is present in the `head` and another plain script element is dynamically added to head. The former is `blocking` and the latter is `non-blocking`, so say we had a string value saying `dynamically-injected-non-blocking`, we could maybe convey more information regarding why it was `non-blocking` as well.  The proposal started out with a couple more such values before deciding to rely on the boolean.

The final value that is exposed was defined as string to keep it open to such possible extensions if they were to be deemed useful later on.

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

Message ID: <w3ctag/design-reviews/issues/753/1196938824@github.com>