This content originally appeared on Mike Taylr Dot Com Web Log and was authored by Mike Taylor
If you somehow found this blog post because you googled or binged “site not working Chrome 100”, well, congrats my SEO trap worked successfully.
Also, don’t panic.
The quickest way to test if your site is broken due to a 3-digit version parsing bug is to temporarily enable the chrome://flags/#force-major-version-to-minor flag and restart the browser. This will change the version that Chrome reports in the User-Agent string and header from 100.0.4896.45 (or whatever the real version number will be) to 99.100.4896.45. If the site works again, you know you have a UA string parsing bug. Congrats again!
(Also, test your site in Firefox Nightly - not all three digit parsing bugs will affect both Chromium browsers and Firefox, but it’s good to verify in case you need to fix your bugs in multiple places.)
At this point, please file a bug at crbug.com/new. That will automatically cc me. Or just feel free to tweet at me or email me. Swing by the house if you want, but we have dinner around 6pm. After dinner is better.
Or, best yet, just fix your site bugs without me being in the loop and I will be so proud of you.
This content originally appeared on Mike Taylr Dot Com Web Log and was authored by Mike Taylor
Mike Taylor | Sciencx (2022-03-21T04:00:00+00:00) Chrome 100 Breakage Playbook. Retrieved from https://www.scien.cx/2022/03/21/chrome-100-breakage-playbook/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.