Chrome 100 affects certain websites

Previously, Firefox was the first to test the browser version of the millennium bug problem. When the browser version reaches 100, some websites may have problems such as abnormal loading. At that time, Mozilla engineers discovered that some websites were indeed affected, and some websites encountered errors when reading the browser version and converting them into strings, resulting in abnormal functions. Now Google Chrome is also testing this issue because the Google Chrome 100 version will be launched soon, which may affect the use of some websites.

Hidden Chrome Features

Under normal circumstances, the browser version number will not affect the use of the website, but some website developers will read the browser version to determine whether the function needs to be discarded. The UA string (user agent string) is used to read the browser version. For example, 96.0.4664.110 in the following UA string is the version number of Google Chrome.

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.110 Safari/537.36

The main version is 96 in the string. Usually, developers will only read the main version if they want to determine the browser version, and then translate the main version before processing. Some websites mistakenly regard 100 as 10, causing users to use Chrome version 100, but all versions will be recognized as Chrome version 10.

DUDA is a well-known web design toolkit website. The website reads the UA string to determine whether the user’s browser is supported. The test found that when Chrome 100 is used to access DUDA, it will be recognized as Chrome 10, which triggers the low version incompatibility restriction and is blocked from access. Considering that there may be more than one or two websites affected, Google and Mozilla are actively conducting tests to avoid the millennium bug problem in browsers.