How prevalent are new "Browser out of date" warning since roll out of M100 ?

[Jonathan Dixon]

I've just come across a website (a commercial Health imaging tool) that no longer loads on Chrome M100 claiming the browser is out of date. Sure enough, hacking the UA to Chrome/99.1.2.3 allows the page to work.

Obv the issue here is the poor webserver implementation and fix lies on them, but I'm interested if this is known to be a prevalent issue? and there's any publicly documented help for this, both for users to work around, and for web devs to fix their code?

Cheers,

Joth

- Having flashbacks of Y2K bug.

(Aplos if this is an inappropriate list for this question. I searched and can't find any FAQ on it which maybe my answer)

[K. Moon]

You might find this article has useful background information: https://hacks.mozilla.org/2022/02/version-100-in-chrome-and-firefox/

If you'd like to file an issue, you can do so here: https://webcompat.com/issues/new?label=version100.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/60f85028-56d5-4f67-9dd9-d2007711b6d5n%40chromium.org.

[Jonathan Dixon]

On Wednesday, April 13, 2022 at 5:14:19 PM UTC+1 K. Moon wrote:

You might find this article has useful background information: https://hacks.mozilla.org/2022/02/version-100-in-chrome-and-firefox/

Perfect, exactly what I was hoping for, thank you.

 

If you'd like to file an issue, you can do so here: https://webcompat.com/issues/new?label=version100.

 

On Wed, Apr 13, 2022 at 5:18 AM Jonathan Dixon <jo...@chromium.org> wrote:

I've just come across a website (a commercial Health imaging tool) that no longer loads on Chrome M100 claiming the browser is out of date. Sure enough, hacking the UA to Chrome/99.1.2.3 allows the page to work.

Obv the issue here is the poor webserver implementation and fix lies on them, but I'm interested if this is known to be a prevalent issue? and there's any publicly documented help for this, both for users to work around, and for web devs to fix their code?

Cheers,

Joth

- Having flashbacks of Y2K bug.

(Aplos if this is an inappropriate list for this question. I searched and can't find any FAQ on it which maybe my answer)

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+unsubscribe@chromium.org.

[Mike Taylor]

Hey Jonathan,

https://bugs.chromium.org/p/chromium/issues/detail?id=1310778 is also a place to hang bugs off of. I wrote a bit about how to test for these 3 digit parsing bugs in https://miketaylr.com/posts/2022/03/chrome-100-breakage-playbook.html, and documented how to fix a not-very-widely-used jQuery plugin at https://miketaylr.com/posts/2021/10/jquery-reject-js-seo-hack.html (tl;dr - delete it).

We know of a handful of bugs, and I've been working on outreach - but please report more as you find them. The Mozilla WebCompat team tags me on the webcompat.com issues that relate to Chrome, if you prefer using webcompat.com to crbug.

later,
Mike