Major Milestone - v100 of Edge/Chrome/Firefox!

VedanshS933

100 version will cause problem and also is a Major Milestone! It will cause the problem that big sites will stop working because many sites only report the first two digit numbers. So they'll report 100 as 10 and then block you thinking you are using an old version.

Will Scratch get affected? discuss about version 100 here.

Release dates for v100
March 29 - Microsoft Edge and Google Chrome
May 3 - Mozilla Firefox

What can happen in Scratch blocks?

when green flag clicked
set [User Agent v] to (join (letter (1) of (correct user agent)) (letter (2) of (correct user agent))
if <(User Agent) < [40]> then 
say [You are Blocked. Please upgrade to a new version]
else
broadcast [Connect... v]
end

(I know they are Scratch Blocks)

Here if it reports 100 as 10 then is will surely block them. They need to update it to

when green flag clicked
set [User Agent v] to (join (letter (1) of (correct user agent))(join (letter (2) of (correct user agent)) (letter (3) of (correct user agent))))
if <(User Agent) < [40]> then 
say [You are Blocked. Please upgrade to a new version]
else
broadcast [Connect... v]
end

In this script it detects all three numbers and then it will able to allow

Scratch On!

Last edited by VedanshS933 (Feb. 22, 2022 04:39:53)

-ElectronicArts-

they have their own topic why you have to make a separate topic for this

-EmeraldThunder-

I expect most sites will quickly allow ‘version 10’ through their filters in a matter of days. Maybe the browsers have some sort of elaborate fix they've got planned and are waitng to reveal.

VedanshS933

-EmeraldThunder- wrote:
I expect most sites will quickly allow ‘version 10’ through their filters in a matter of days. Maybe the browsers have some sort of elaborate fix they've got planned and are waitng to reveal.

What would happen if someone is using 10 so they'll also be allowed and then might get hacked?

-EmeraldThunder-

VedanshS933 wrote:
(#4)
-EmeraldThunder- wrote:
I expect most sites will quickly allow ‘version 10’ through their filters in a matter of days. Maybe the browsers have some sort of elaborate fix they've got planned and are waitng to reveal.

What would happen if someone is using 10 so they'll also be allowed and then might get hacked?

Maybe they'd be forced to update, not ideal but it's better than facing patched venrebilities.

VedanshS933

-EmeraldThunder- wrote:
VedanshS933 wrote:
(#4)
-EmeraldThunder- wrote:
I expect most sites will quickly allow ‘version 10’ through their filters in a matter of days. Maybe the browsers have some sort of elaborate fix they've got planned and are waitng to reveal.

What would happen if someone is using 10 so they'll also be allowed and then might get hacked?
Maybe they'd be forced to update, not ideal but it's better than facing patched venrebilities.

If they allow 10 then they'll also need to allow 11 and above.

god286

Check the news (very interesting) - right now in Firefox Nightly and Chrome you can set a flag to volunteer to test sites with your User Agent as Version 100, UA parsing libraries have made fixes (just get sites to update), things should go well. But if it doesn't go well, Mozilla (and I think Google) have a backup plan to freeze version numbers at 99 if there is widespread damage. I heard they also might make the version like Chrome/99.101.1.2 (101 being the actual version number) instead of the usual Chrome/99.1.2 maybe? I don't think the 99.101 solution will be good though - it will make user agents even more complicated. But it's a last resort, I hope the transition goes well!

Some people called it a Y2K all over again. It's very similar.

Last edited by god286 (Feb. 21, 2022 08:28:05)

-inspect-

I never got the problem with this. The number changes UA is increased to 100 and then what? It can't process it? Well that makes no sense! Why on earth would you make a website without thinking about parsing ONE extra character!

VedanshS933

-inspect- wrote:
I never got the problem with this. The number changes UA is increased to 100 and then what? It can't process it? Well that makes no sense! Why on earth would you make a website without thinking about parsing ONE extra character!

Check the Realese Dates. Also search

Scratch137

-inspect- wrote:
I never got the problem with this. The number changes UA is increased to 100 and then what? It can't process it? Well that makes no sense! Why on earth would you make a website without thinking about parsing ONE extra character!

Browsers report version info using what's called a user agent string, which looks something like this:

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

Let's just look at the Chrome version for simplicity.

98.0.4758.80 is quite a long and complicated version number. Features are never added or removed in minor updates, which means that for the sake of compatibility, most websites just check the first two digits, which represent the major version number.

This method, of course, isn't compatible with three-digit version numbers, so Chrome 100 will end up being detected as Chrome 10. This is an issue, because Chrome 10, being from March 2011, is extremely outdated and unsupported by most websites.

In order to prevent major issues when Chrome 100 releases in March, a lot of websites will have to change the way they check version strings.

VedanshS933

Scratch137 wrote:
-inspect- wrote:
I never got the problem with this. The number changes UA is increased to 100 and then what? It can't process it? Well that makes no sense! Why on earth would you make a website without thinking about parsing ONE extra character!
Browsers report version info using what's called a user agent string, which looks something like this:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4758.80 Safari/537.36 Edg/98.0.1108.50
Let's just look at the Chrome version for simplicity.

98.0.4758.80 is quite a long and complicated version number. Features are never added or removed in minor updates, which means that for the sake of compatibility, most websites just check the first two digits, which represent the major version number.

This method, of course, isn't compatible with three-digit version numbers, so Chrome 100 will end up being detected as Chrome 10. This is an issue, because Chrome 10, being from March 2011, is extremely outdated and unsupported by most websites.

In order to prevent major issues when Chrome 100 releases in March, a lot of websites will have to change the way they check version strings.

That's what I mean!

MagicCrayon9342

Does the UA parser in
https://github.com/JaydenDev/redirX
have any issues with 100.x versions?

VedanshS933

MagicCrayon9342 wrote:
Does the UA parser in
https://github.com/JaydenDev/redirX
have any issues with 100.x versions?

You can check by activating a flag I think. Can't remember it's name

kccuber

I find it quite hilarious that this is literally what user-agent detectors are:

(join (letter (1) of (user agent)) (letter (2) of (user agent))

ok not exactly but you get the point

scratchusername40

If apple keeps releasing safari versions at the current pace, Safari 100 will likely come out in the year 2123 (yes I did the math)

SuperMarioHome

First we had the Y2K bug, then we started *ing (was going to have a different f) out about 2038 and now we have this.

VedanshS933

SuperMarioHome wrote:
First we had the Y2K bug, then we started *ing (was going to have a different f) out about 2038 and now we have this.

Yup! We are entering 3 numbers!

god286

MagicCrayon9342 wrote:
Does the UA parser in
https://github.com/JaydenDev/redirX
have any issues with 100.x versions?

It doesn't check version numbers..

VedanshS933

god286 wrote:
MagicCrayon9342 wrote:
Does the UA parser in
https://github.com/JaydenDev/redirX
have any issues with 100.x versions?
It doesn't check version numbers..

Github does not?

VedanshS933

scratchusername40 wrote:
If apple keeps releasing safari versions at the current pace, Safari 100 will likely come out in the year 2123 (yes I did the math)

They're still on 15 ha ha ha

kccuber wrote:
I find it quite hilarious that this is literally what user-agent detectors are:
(join (letter (1) of (user agent)) (letter (2) of (user agent))
ok not exactly but you get the point

Yup I think they do this

when green flag clicked
set [User Agent v] to (join (letter (1) of (correct user agent)) (letter (2) of (correct user agent))
if <(User Agent) < [40]> then 
say [You are Blocked. Please upgrade to a new version]
else
broadcast [Connect... v]
end

(I know they are Scratch Blocks)

Here if it reports 100 as 10 then is will surely block them. They need to update it to

when green flag clicked
set [User Agent v] to (join (letter (1) of (correct user agent))(join (letter (2) of (correct user agent)) (letter (3) of (correct user agent))))
if <(User Agent) < [40]> then 
say [You are Blocked. Please upgrade to a new version]
else
broadcast [Connect... v]
end

In this script it detects all three numbers and then it will able to allow

Scratch On!

Discuss Scratch