Could go wrong? Get ready for version 100! ~ Canary version "Chrome" arrives at v100

Du du of Yajima

Chrome/Edge end of March, Firefox May v100 stable Edition

　“Du du of Yajima”では、ニュース・レビューにこだわらない幅広い話題をお伝えします。

　The Canary version of "Google Chrome" has finally become "100th version". It has been found that the release of the Stable (stable) version may be at the end of March. In a few days, "Microsoft Edge" will also be "version 100". The release of "Firefox100" will also be completed later in May.

　In other words, this year should commemorate the major browsers to usher in "version 100" (? (this is a year.

　However, as the mainstream version rises to three digits, a failure is also expected. This is because some Web browsers (UserAgent,UA) version determination process does not take into account that the major version is 3 digits. The following is an example of a banner that shows incorrect version judgment and is not supported. Through "Chrome100" access, it may be internally determined as "Chrome10".

　It's fine if it's just a warning banner, but it's troublesome if it doesn't move, or if it's an unintentional action.

An error occurs when the version of "Chrome" reaches three digits? The test function flag is installed on the "Chrome96" beta version

　Therefore, "Chrome" provides flags to detect or avoid this problem. Can be enabled on the chrome://flags screen.

Fix the major version as "99"# force-major-version-to-minor"

　"# force-major-version-to-minor" fixes the major version of UA to "99", forcing the major version number to be inserted into the location of the minor version. This flag is a backup plan to prevent unexpected incompatibility problems with the 3-bit major version. If you have a problem displaying the Web browser in Chrome 100th or later, you can try it. Developers can learn about the real major version by referring to minor versions (minor versions of "Chrome" are usually always "0").

Force the major version to be changed to "100"" # force-major-version-to-100 "

　"# force-major-version-to-100" forces the major version of UA to be changed to "100". If you want to test in advance what happens to your website when you visit through "Chrome 100th", you can use "Chrome 96" to "Chrome 99".

Fix the minor version to "100"" # force-minor-version-to-100 "

　"# force-minor-version-to-100" fixes the minor version of UA to "100".

　As mentioned above, if there is an unexpected incompatibility problem with the 3-bit major version, you can avoid the problem of replacing the major version with a minor version in "# force-major-version-to-minor", but there may be a problem with the site assuming the minor version is "0". Using this flag, you can check in advance to see if the solution is valid.

　In addition to "# force-major-version-to-minor", "Microsoft Edge" can also be used. I hope you can use it flexibly. By the way, there is no such logo specially prepared in "Firefox".