Learn more about the features listed here through the provided links or from the list on. Unless otherwise noted, changes described below apply to the newest Chrome beta channel release for Android, Chrome OS, Linux, macOS, and Windows. We will note any significant delays or changes on this page as well. See the companion Reduced User Agent string updates page for more details and example User Agent strings at each of these phases.
#Via chrome9 driver android
Once rolled-out, the reduced UA string would apply to all page loads on Android that do not opt into the deprecation trial.ĭeprecation trial ends and all page loads receive the reduced UA string and related JS APIs. Once rolled-out, the reduced UA string would apply to all page loads on desktop operating systems for sites that do not opt into the deprecation trial.ĬTA: Ensure your site is compatible with the reduced Mobile UA string and related JS APIs, and migrate to UA Client Hints if not.īegin roll-out of reduced Android Mobile (and Tablet) UA string and related JS APIs. Once rolled-out, the reduced UA string would apply to all page loads on desktop and mobile operating systems for sites that do not opt into the deprecation trial.ĬTA: Ensure your site is compatible with the reduced Desktop UA string and related JS APIs, and migrate to UA Client Hints if not.īegin roll-out of reduced Desktop UA string and related JS APIs ( erAgent, navigator.appVersion, atform ). Ship reduced Chrome version numbers (“0.0.0”). Launch deprecation trial and Enterprise policy, for instances where a site may need more time for migration.ĬTA: Ensure your site is compatible with the reduced Chrome version number, and migrate to UA Client Hints if not. Otherwise, depending on feedback we will reconsider the best course of action.ĬTA: Enroll in the deprecation trial or Enterprise policy for your site, when needed. We will evaluate feedback from origin trial partners and the community, and based on this feedback proceed to Phases 3 through 7 of our plan, giving the ecosystem adequate time to adapt in between them. Launch an origin trial for sites to opt into the final reduced UA string for testing and feedback, for at least 6 months. Warn about accessing erAgent, navigator.appVersion, and atform in DevTools, beginning in M92.ĬTA: Enroll in the origin trial for your site, and provide feedback until Chrome 101 is released.
We plan to roll out these changes slowly and incrementally in 7 Phases-pending origin trial feedback.Ĭall to Action (CTA): Audit your site usage to understand where migration may be necessary. But in the case that we encounter delays, we do not intend to accelerate timelines between Phases. Note: The usual disclaimers about estimating engineering deadlines apply-unforeseen circumstances may dictate delays. The Chromium schedule dashboard will be useful for understanding dates associated with each Chrome version and its progression from Canary into Beta and Stable Release. What follows is repeated from the original blog post, but contains estimated Chrome versions where these Phases will begin to help you prepare. Now that we have an origin trial ready for testing the Reduced User-Agent header (and associated JS interfaces) we have estimated timelines to share.
#Via chrome9 driver update
Back in May, we published an update on our User-Agent string reduction plans with a promise to publish further details on timing.
0 kommentar(er)
