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 enabled and restarted the browser, Netflix worked fine for me (from login, all the way to playing a movie).
Thanks, Ali On Thu, Dec 30, 2021 at 12:37 PM Paul Schmied <psdae...@gmail.com> wrote: > I tested the Chrome 96 #reduce-user-agent Flags setting yesterday and > found that it causes Netflix to redirect to an " incompatible browser" > webpage. Netflix support had no idea what was going on. > > On Monday, December 20, 2021 at 8:13:33 AM UTC-6 mike...@chromium.org > wrote: > >> Hi Chris, >> >> Could you please file a bug at crbug.com/new, with the exact website you >> had an issue on? I'm happy to follow up once that's done. >> >> thanks, >> Mike >> >> On 12/20/21 9:11 AM, Chris Bloggs wrote: >> >> Can someone please contact sony, when I reduced these headers I was >> unable to auth on their website, it seems they specifically probably have >> whitelisted portions of the removed headers to allow authentication, it >> needs a google/chrome rep rather than a end user like myself. >> >> On Friday, 11 June 2021 at 18:34:14 UTC+1 James Rosewell wrote: >> >>> Please could you publish information concerning this proposals >>> compliance with the draft commitments Google >>> <https://assets.publishing.service.gov.uk/media/60c21e54d3bf7f4bcc0652cd/Notice_of_intention_to_accept_binding_commitments_offered_by_Google_publication.pdf> >>> made to the Competition and Markets Authority which were published today? >>> On Wednesday, 19 May 2021 at 21:49:10 UTC+1 Mike Taylor wrote: >>> >>>> Hi Par (and others), >>>> >>>> Today we published an update on our UA Reduction plans, in a new >>>> thread: >>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/e3pZJu96g6c >>>> >>>> Happy to answer any questions over there (rather than engage in >>>> multiple >>>> threads on the topic). >>>> >>>> Thanks, >>>> Mike >>>> >>>> On 5/6/21 10:33 AM, Mike Taylor wrote: >>>> > Hi Par, >>>> > >>>> > Yep, this is the right mailing list to follow for announcements >>>> > related to these proposed changes. >>>> > >>>> > We don't have anything to share right now, but hope to soon (not a >>>> > super satisfying answer, I know). >>>> > >>>> > thanks, >>>> > Mike >>>> > >>>> > On 5/6/21 9:22 AM, 'par.andersson%neten...@gtempaccount.com' via >>>> > blink-dev wrote: >>>> >> Any update on this? Where can I follow progress on this topic, is >>>> >> this the right place? (sorry if this has been asked/answered before, >>>> >> I have not seen such comment) >>>> >> Thanks, >>>> >> Par >>>> >> >>>> >> On Thursday, February 25, 2021 at 5:20:34 AM UTC+1 Aaron >>>> Tagliaboschi >>>> >> wrote: >>>> >> >>>> >> >>>> >> >>>> >> On Wed, Feb 24, 2021, 22:41 James Nghiem <james...@berkeley.edu> >>>> >>>> >> wrote: >>>> >> >>>> >> >>>> >> Ah I see it in the release now. A few more questions: >>>> >> As part of the Chrome 89 rollout, I'm assuming that the UA >>>> will >>>> >> also be frozen, correct? >>>> >> >>>> >> >>>> >> No, the UA string will *not* be frozen in Chrome 89. We've yet >>>> to >>>> >> release a firm timeline. >>>> >> >>>> >> If so, will the UA still be up-to-date for Chrome 89 or >>>> should >>>> >> we expect it to be frozen at Chrome 88's value? >>>> >> On Wednesday, February 24, 2021 at 11:16:43 AM UTC-8 Aaron >>>> >> Tagliaboschi wrote: >>>> >> >>>> >> The User Agent Client Hints feature will be fully rolled >>>> in >>>> >> Chrome 89 >>>> >> >>>> >> >>>> >> Aaron Tagliaboschi | Software Engineer, Chrome Trust & >>>> >> Safety >>>> >> >>>> >> >>>> >> On Wed, Feb 24, 2021 at 1:36 PM James Nghiem >>>> >> <james...@berkeley.edu> wrote: >>>> >> >>>> >> Just wanted to follow up on this since I haven't >>>> seen or >>>> >> been able to find any updates to the timeline! Do we >>>> >> have any specific dates on when we're expecting UACH >>>> to >>>> >> roll out? >>>> >> >>>> >> >>>> >> >>>> >> On Friday, January 29, 2021 at 9:16:39 AM UTC-8 >>>> Thomas >>>> >> Ziegelbecker wrote: >>>> >> >>>> >> +1 ? >>>> >> >>>> >> On Thursday, December 17, 2020 at 9:31:48 PM >>>> UTC+1 >>>> >> Saurav Kumar wrote: >>>> >> >>>> >> Hi James, >>>> >> >>>> >> Now that we are nearing 2021, do we have an >>>> >> approximate date when Chrome would start to >>>> roll >>>> >> out frozen UA strings? >>>> >> >>>> >> Thanks >>>> >> Saurav >>>> >> >>>> >> On Monday, 27 July 2020 at 14:32:01 UTC-7 >>>> James >>>> >> Nghiem wrote: >>>> >> >>>> >> Hi Yoav, >>>> >> >>>> >> Just wanted to clarify part of your >>>> message: >>>> >> >>>> >> > First, the phase of the project that >>>> >> reduces the amount of available >>>> information >>>> >> in the traditional User-Agent string to >>>> >> browser (e.g. “Chrome”), major browser >>>> >> version, and mobile/desktop, has been >>>> >> deferred until at least 2021 to provide >>>> >> additional time for the ecosystem to >>>> >> evaluate the new UA-CH capabilities. >>>> >> >>>> >> Will the delay also include freezing the >>>> UA >>>> >> string (i.e. will the current UA string >>>> be >>>> >> up-to-date until some change in 2021). >>>> >> >>>> >> Thanks and really appreciate your work! >>>> >> James >>>> >> On Thursday, June 18, 2020 at 2:01:37 PM >>>> >> UTC-7 Aaron Tagliaboschi wrote: >>>> >> >>>> >> Thank you. Are these the only >>>> two >>>> >> documents that are relevant to >>>> this >>>> >> work? How are changes to one >>>> >> reflected in the other? >>>> >> >>>> >> >>>> >> There are currently three related >>>> but >>>> >> technically independent proposed >>>> specs: >>>> >> >>>> >> * the HTTP Client Hints spec >>>> >> <https://httpwg.org/http-extensions/client-hints.html> deals >>>> >> with the actual client hint >>>> >> mechanics; that is to say the >>>> >> advertisement mechanism (the >>>> >> Accept-CH header and the >>>> preferences >>>> >> store). >>>> >> * the Client Hint Infrastructure >>>> spec >>>> >> <https://wicg.github.io/client-hints-infrastructure/> discusses >>>> >> how browsers decide when to >>>> store CH >>>> >> preferences and when to send >>>> >> headers. This document is >>>> actually >>>> >> the proposed changes to the >>>> HTML, >>>> >> Fetch, and Permission Policy >>>> (nee >>>> >> Feature Policy specs) >>>> >> * the User Agent Client Hints spec >>>> >> <https://wicg.github.io/ua-client-hints/> lays >>>> >> out the specifics if the user >>>> agent >>>> >> set of client hints >>>> >> >>>> >> They're generally laid out so >>>> there's no >>>> >> duplicate or redundant information, >>>> so >>>> >> they reference each other. >>>> >> >>>> >> -- >>>> >> 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 >>>> >> <mailto:blink-dev+...@chromium.org>. >>>> >> To view this discussion on the web visit >>>> >> >>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68030e42-3c2e-490e-b67a-1f1640c47766n%40chromium.org >>>> >> < >>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68030e42-3c2e-490e-b67a-1f1640c47766n%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 on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/a609b857-7b59-4d3b-b5a1-bd21d435e2e6n%40chromium.org > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/a609b857-7b59-4d3b-b5a1-bd21d435e2e6n%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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BWdJ_6X3yCk_BNQzmg%2BWqbR0WyRnWng7--vRzrKQSK8Af1EUg%40mail.gmail.com.
