On 4/9/25 3:51 PM, Frank Yung-Fong Tang wrote:
> Safari already reduced the Accept-Language to a single language in
most cases.
If my understanding of the English is correct:
This mean, right now, in *some cases, * Safari does *NOT* reduced the
Accept-Language to a single language, right?
Please read
https://github.com/explainers-by-googlers/reduce-accept-language/issues/10#issuecomment-2093927039,
the claim that "safari only contains one language" is incorrect when I
check last May. Please correct me if Apple change that after May 2024.
Then., we should understand why Apple does NOT reduce to only one
language for those cases?
Yes, we would love to have more info on this, and would be happy to
align with it - maybe that's a better outcome. I have asked for more
information at
https://github.com/WebKit/standards-positions/issues/338#issuecomment-2791172271.
In
https://github.com/explainers-by-googlers/reduce-accept-language/issues/10#issuecomment-2098949098
I listed the following regions which should have higher impact by this
change:
Tier 1: High Importance India, South Africa, Singapore, Switzerland
Tier 2: Moderate Importance Canada, Belgium, Malaysia, Nigeria
I think we need to be careful about undercoverage bias and sampling
bias while analysis the impact of this change
https://www.scribbr.com/research-bias/undercoverage-bias/
https://www.scribbr.com/research-bias/sampling-bias
> HTTP-only
Does this mean you are not proposing to ship this to HTTPS?
No, this is just shorthand for not touching the JS APIs, but only the
Accept-Language header sent over HTTP (or HTTPS).
Regards,
Frank
On Wednesday, April 9, 2025 at 9:01:44 AM UTC-7 Mike Taylor wrote:
Also, thanks for the offer to help with the appcompat assessment -
let's connect off-list to discuss that.
On 4/9/25 7:25 AM, Victor Tan wrote:
Hi Peter,
I don't think we currently support the feature on WebView even if
we turn on the finch flag.
WebView might work a little differently, there is some work to
support this feature on WebView. We can start the work in the
near future.
Victor
On Wed, Apr 9, 2025 at 6:18 AM Peter Beverloo
<beve...@google.com> wrote:
Agreed, and thank you for iterating on this. If this is
launching behind a Finch flag then we'd be happy to help with
an initial assessment too :)
Thanks,
Peter
On Tue, Apr 8, 2025 at 4:21 PM Mike Taylor
<mike...@chromium.org> wrote:
We do intend to follow suit there once we learn we can
ship this and its compatible with the web. It seems nice
to separate web compat problems from app compat problems,
if we can.
On 4/8/25 6:48 AM, Peter Beverloo wrote:
Hi Victor - you write that the feature is supported on
all of Blink's platforms but WebView: is there a plan to
follow up and avoid a more permanent divergence in
behaviour?
Thanks,
Peter
On Thu, Apr 3, 2025 at 8:47 PM Victor Tan
<vict...@chromium.org> wrote:
TAG review issue open:
https://github.com/w3ctag/design-reviews/issues/1078
Victor
On Tuesday, April 1, 2025 at 10:42:44 PM UTC-4
Vladimir Levin wrote:
Can you file the various review gates as well?
Screenshot 2025-04-01 at 10.42.12 PM.png
TAG reviewTo be filed
Is this accurate?
--
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+...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/35bf986c-e830-4265-8621-c1a24a70ce43n%40chromium.org
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/35bf986c-e830-4265-8621-c1a24a70ce43n%40chromium.org?utm_medium=email&utm_source=footer>.
--
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 visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/7fb6cf8b-2a75-4315-baf9-6966982e0c46%40chromium.org.
