This is an extremely bad call
-
-
-
I think
@slightlylate did a great job at explaining some concerns about this in the original issue --> https://groups.google.com/a/chromium.org/d/msg/blink-dev/-2JIRNMWJ7s/PT08NFFYCgAJ … Sorry for joining the conversation here, I work with Andrew on@polyfillio (which Alex mentioned in their comment).1 reply 0 retweets 1 like -
Replying to @JakeDChampion @triblondon and
Does http://polyfill.io need more than Sec-CH-UA gives it without an opt-in? (i.e. brand and major version)
1 reply 0 retweets 0 likes -
-
-
Replying to @yoavweiss @triblondon and
Yep exactly that. It's not frequent we use minor version nowadays but it does happen - here is a list of polyfills we have which target minor versions --https://gist.github.com/JakeChampion/fab796e59dfd3ff1a831186bf2b21c3d …
2 replies 0 retweets 1 like -
Replying to @JakeDChampion @yoavweiss and
The last polyfill to need minor version targeting was AbortController for iOS Safari as it was not present in 11.1 but was present in 11.2
2 replies 0 retweets 1 like -
Replying to @JakeDChampion @yoavweiss and
Last month we did 41.8 billion requests, hopefully we can figure out a way to get minor version without hurting the performance of those requests
1 reply 0 retweets 1 like -
Replying to @JakeDChampion @yoavweiss and
In the thread, I asked for some characterisation of the perf impact of losing this information. Any way we can partner to get (and publish) that data? Also, for
@yoavweiss, we need the model published re: how much each bit matters and threshold values.2 replies 0 retweets 1 like
API OWNERs can't possibly greenlight this without some firmer cost/value data.
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.