So browsers read stream sof bytes coming in and try to locate things that will correspond to network resources and request them early. This is happening in the critical path of page load without full information about the resulting DOM, CSS OM, or even what's in the viewport.
It was meant as a joke; done poorly. Apologies for that and to @mnot.
That said, the critique stands. The protocol is over-complex beyond one level of dependency. Also, I frequently disagree with my colleagues (and many other people) on a great many things.
-
-
An instance of this is my deep, near-decade-long frustration that the Powers That Be in HTML (largely Googlers) have failed to prioritize creating a functional priority level scheme for HTML and to make `async` and `defer` attributes universally respected across types
-
That was the primary ding in the thread; that HTML is even more broken than H/2 in this regard. I'll try to be more clear in the future. And, again, apologies to
@mnot.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.