My LGTM still stands. It's one site that did something weird, but as
Aristotle said, one swallow does not a summer make. I appreciate your
careful approach though.
/Daniel
(cutting away most of the history in an attempt to get Google's mail
servers to accept it)
On 2026-02-13 15:31, Barry Pollard wrote:
A further update on this Intent to Ship.
While testing Chrome Beta, Google testers discovered the new values
(16, and presumably 32 as well) caused blockages to x.com (formerly
Twitter) logins. We reached out to that team who made the change to
accept these new values too, and we've confirmed we no longer see the
issue. Unfortunately we've no way of measuring this since the blockage
was done server side and was only apparent when the new values were
sent. In addition it seems it was one of many signals used my X to
decide blockage (our testing team in India noticed this, but myself in
EMEA and others in USA could not repeat it). I've asked X for more
details if they can share, as a lot of this is presumption based on my
side and they've only confirmed the issue was resolved with a change
at their side.
This leaves us in a bit of a predicament as we cannot be sure that
other sites may not also have similar logic to block functionality on
seeing unexpected values. However, I don't want to accept that no new
values can be added, as that severely limits the usefulness of the
API. Especially as we 1) drop older values, and 2) introduce new
features that depend on higher memory usage (e.g. on-device AI).
This is gated behind a feature flag, we can disable these new number
with a kill switch if we do see issues. An alternative is for a
gradual rollout but, as per previous discussions, we try to avoid APIs
returning different values as this leads to more confusion than
helpfulness. And in this example, there was already enough confusion
since the behaviour was inconsistent.
Therefore, I'd like to proceed with the release with the kill switch
option if necessary.*Do API owners agree and/or have alternative
suggestions?*
In the meantime it has been disabled by default again and I've updated
the shipping milestone to 147 to allow more time for feedback.
Thanks,
Barry
--
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 [email protected].
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/d9b2f4a2-38f1-4713-9a86-eb8c24e7e3fc%40gmail.com.
