Real-world browsers (like Chrome) have to deal with HTTP 1.1 and 2.0 at the same time. This means that priority doesn't map cleanly onto the H/2 notion of priorities...which is also bonkers. How bonkers? Lets take a look!
My feedback to them at the time was the same as now: cool, but beyond one level of dependency, how will this ever be sane or useful by a webdevs?
-
-
it may be the case that webdevs use something simpler and protocol stacks map those into roots reflecting webdev scope. Or maybe webdevs standardize classifications instead of pri - which can also be mapped along the lines of firefox. no reason web view has to be the same.
-
mostly I'm annoyed you took a pot shot at mark rather than assuming we're all in this together to build a better internet. That's how I remember it. Especially galling when your proximate complaint is about a technology your own google teammates promoted hard.
- 3 more replies
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.