Do we know how much complexity would be involved in exposing it on Request for the current implementation?
-
-
Trivial :) Only reason I didn’t expose it is because Yutaka I believe initially wanted it that way to make it less of a barrier for other implementations (less normative things involved). Happy to expose and see if we get any feedback
2 replies 0 retweets 3 likes -
Replying to @domfarolino @addyosmani and
I seem to recall the Firefox networking folks did not think it could be easily boiled down into an exposed enum like low/medium/high when I asked about this before. I'll try to dig up where they told me that.
2 replies 0 retweets 5 likes -
Replying to @wanderview @domfarolino and
Thanks! :) Getting feedback from the Mozilla side of things would be awesome. Just note that we're not talking about exposing the priority, but the (developer provided) hint that was used to created the Request
2 replies 0 retweets 3 likes -
-
Replying to @wanderview @yoavweiss and
Actually, looking at the design doc this is what I was thinking of and I feel like we discussed it before. I think the necko folks were concerned about such fine grained enum values and trying to map them to actual browser behavior.
1 reply 0 retweets 0 likes -
Replying to @wanderview @domfarolino and
What design doc you're referring to? https://wicg.github.io/priority-hints/#solution … outlines the approach (in a not-yet-normative way). Basically, the importance values enable the UA to "upgrade" or "downgrade", but don't dictate an exact value
1 reply 0 retweets 1 like -
Replying to @yoavweiss @domfarolino and
Oh, the explainer still has the more granular values. Sorry for my confusion. Missing details trying to read on my mobile. I'll try to look more later when I have a real computer.
1 reply 0 retweets 2 likes -
Replying to @wanderview @domfarolino and
Meh, need to fix it then... Sorry for not keeping the docs in sync
1 reply 0 retweets 0 likes -
Replying to @yoavweiss @wanderview and
So wait, does the new proposal actually map the full set of priorities? I.e. 1-10...or 100. Whatever. Just want to stop the dual charades of "browsers are magic" and "browsers are fully under my control as a developer". It's always a negotiated peace.
2 replies 0 retweets 3 likes
The idea that the browser will figure out the right thing to do is nuts. It's similarly nuts to pretend that the browser won't intervene to improve things when it can. So give us an expressive hint language already!
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.