**
*Hi there,*
*
We would like to extend the User-Agent Reduction OT again, from M107 to
M111 (inclusive). As announced in our I2S for “Phase 5”
<https://groups.google.com/a/chromium.org/g/blink-dev/c/kC-AeZ1fSdY/m/HhYYNDeACAAJ>,
we intend to roll out the next phase of UA reduction gradually until
M111. We’ve received a request from the ecosystem that it would benefit
testers and developers to continue testing with the user-agent reduction
until the rollout to general availability reaches 100%, which seems very
reasonable.
(We might come back and ask for another extension for “Phase 6” testing,
but let’s wait until there’s demand for that.)
Original I2E
https://groups.google.com/a/chromium.org/g/blink-dev/c/R0xKm1B7qoQ/
<https://groups.google.com/a/chromium.org/g/blink-dev/c/R0xKm1B7qoQ/>
First
I2EEhttps://groups.google.com/a/chromium.org/g/blink-dev/c/6x6WH2Odzfo/m/FkDjee5cHQAJ
<https://groups.google.com/a/chromium.org/g/blink-dev/c/6x6WH2Odzfo/m/FkDjee5cHQAJ>
Second I2EE
https://groups.google.com/a/chromium.org/g/blink-dev/c/jjGeFtHhak4/m/jgldkEkHBgAJ
<https://groups.google.com/a/chromium.org/g/blink-dev/c/jjGeFtHhak4/m/jgldkEkHBgAJ>
Experiment Timeline
M107-M111 inclusive
Reason this experiment is being extended
Like the previous extension, we believe the risks for burn-in don't
apply, because this OT just enables what we are planning to ship as
default behavior in the future (and the OT stopped working last week).
We still have not received negative feedback or reports of breaking from
OT participants, and are encouraged by that fact.
Here’s the relevant info required for OT extensions beyond 6 milestones:
Draft spec:
*
https://compat.spec.whatwg.org/#ua-string-chrome
<https://compat.spec.whatwg.org/#ua-string-chrome>
*
We’ve made solid progress against the open UA string issues, and
have documented the recent landing of “Phase 4” in Chromium. We plan
to continue improving things here.
TAG review:
*
https://github.com/w3ctag/design-reviews/issues/640
<https://github.com/w3ctag/design-reviews/issues/640>- closed as
“Satisfied with concerns”
bit.ly/blink-signals <http://bit.ly/blink-signals>requests
*
Gecko: Shipped/Shipping. Firefox has frozen (or capped) much of
their UA string already.
*
WebKit: Shipped/Shipping. Safari has already frozen everything in
their UA string except for version number info.
*
Web developers: Mixed signals. Reactions have ranged from positive
to indifferent to negative, from various channels.
WPT tests
*
None yet, since UAs have flexibility to diverge here. With more
alignment, this may make sense in the future.
Thanks,
Mike
*
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/45f668db-e8bc-5c32-291f-1b269013dd14%40chromium.org.
