On Wed, May 4, 2022 at 9:53 AM Ronan Cremin wrote:
> > In the long term, we expect this change to improve compatibility, as UA
> detection based on UA-CH is bound to be more reliable than the current
> status quo.
>
> Data so far suggests that this is not in fact the case due to model name
>
On Tue, Apr 26, 2022 at 4:58 PM Jerilyn D. wrote:
> We are testing this reduction change in Chrome 100 using experimental
> flag settings as:
>
> #full-user-agent : Disabled
>
> #reduce-user-agent: Enabled
>
> This is the correct way to test right now ? However this experimental
> feature will
On Tue, Apr 26, 2022 at 4:14 AM Kirill Kandalov
wrote:
> Hi,
> Thanks for the quick reply!
>
> On Monday, April 25, 2022 at 6:34:56 PM UTC+3 abe...@google.com wrote:
>
>> Hi Kirill,
>>
>> Thanks for your feedback.
>>
>> On Thu, Apr 21, 2022 at 2:16 PM Kirill Kandalov
>> wrote:
>>
>>> Hey all!
On Mon, Apr 25, 2022 at 9:14 PM Jerilyn D. wrote:
> Hello,
>
> I just want to get confirmation for the following:
> 1) Going forward, the User-Agent http header will continue to return
> information but just reduced information. This http header will not be
> dropped or suddenly return empty
Hi Kirill,
Thanks for your feedback.
On Thu, Apr 21, 2022 at 2:16 PM Kirill Kandalov
wrote:
> Hey all!
>
> Looks like I'm jumping on this train a little bit late, but still probably
> I’m not the last person on earth that is in the field of the web and only
> recently stumbled this change.
Note: please see the “Experiment Timeline” section for our extension
request - the rest of the details are the same as before.
Contact emails
abe...@chromium.org, miketa...@chromium.org
Original I2E
https://groups.google.com/a/chromium.org/g/blink-dev/c/R0xKm1B7qoQ/
Explainer
Hello:
On Wed, Feb 2, 2022 at 1:21 PM Ян Стахеев wrote:
> Hi!
> I'm looking for a way to test Client Hints and to understand how CH will
> work on my site before UA will be reduced. For now I use
> #reduce-user-agent flag disabling UA. Is blocking UA by the flag is
> enought to see the impact
ed timelines for the deprecation trial?
>
> On Tuesday, January 25, 2022 at 3:40:15 PM UTC+1 Ali Beyad wrote:
>
>> Contact emails
>>
>> abe...@chromium.org, victor...@chromium.org, jadekess...@chromium.org,
>> miketa...@chromium.org
>>
>> Explainer
>>
>> None
Contact emails
abe...@chromium.org, victor...@chromium.org, jadekess...@chromium.org,
miketa...@chromium.org
Explainer
None
Specification
None
Summary
Before we proceed with User-Agent (UA) reduction, we want to allow sites
that are not yet ready for the reduced UA string to get the full UA
Hi Paul,
Thanks for letting us know about Netflix. Could you kindly file a bug at
crbug.com/new with the UA string that you're seeing in devtools? I'm on
Chrome 96 Desktop (Google Chrome96.0.4664.110 (Official Build) (x86_64)),
and when I set the chrome://flags/#reduce-user-agent flag to
, 2021 at 9:39 AM Ali Beyad wrote:
> A blog post just went out for this OT:
> https://developer.chrome.com/blog/user-agent-reduction-origin-trial/
>
> On Thu, Aug 12, 2021 at 9:47 AM Ali Beyad wrote:
>
>> An update on this: it will be too rushed to get the User-Agent Reducti
A blog post just went out for this OT:
https://developer.chrome.com/blog/user-agent-reduction-origin-trial/
On Thu, Aug 12, 2021 at 9:47 AM Ali Beyad wrote:
> An update on this: it will be too rushed to get the User-Agent Reduction
> OT into the M94 branch cutoff (this Thursday), so we
12 matches
Mail list logo
