-ElectronicArts- wrote:

VedanshS933 wrote:

erencemaltay wrote:

Version 99 Release Dates:

iOS: 28 Febuary 2022
PC - 2 March 2022
Android - 2 March 2022

We are not talking about version 99 here and there is no sense talking about it eventhrough thanks for sharing

thankyou for not using scratch on

SuperSonicmario wrote:

Scratch137 wrote:

because Chrome 10, being from March 2011, is extremely outdated and unsupported by most websites.

So when a browser has a sensible design and doesn't eat 4 GiB of RAM, it's outdated?

when green flag clicked
set [ RAM] to [4 GiB]

erencemaltay wrote:

SuperSonicmario wrote:

Scratch137 wrote:

because Chrome 10, being from March 2011, is extremely outdated and unsupported by most websites.

So when a browser has a sensible design and doesn't eat 4 GiB of RAM, it's outdated?

like:

when green flag clicked
set [ RAM] to [4 GiB]

god286 wrote:

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

mumu245 wrote:

god286 wrote:

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

Does Scratch work with the flag?

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

My browser / operating system: Windows NT 10.0, Chrome 100.0.4758.102, No Flash version detected

Scratch137 wrote:

(#46)

mumu245 wrote:

god286 wrote:

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

Does Scratch work with the flag?

I'm using Edge Stable 98, so I don't have that flag, but Scratch seems to work just fine with the UA string edited to say 100 instead of 98:

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

My browser / operating system: Windows NT 10.0, Chrome 100.0.4758.102, No Flash version detected

My browser / operating system: MacOS Macintosh X 10.15, Firefox 107.4, No Flash version detected

mbrick2 wrote:

Scratch137 wrote:

(#46)

mumu245 wrote:

god286 wrote:

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

Does Scratch work with the flag?

I'm using Edge Stable 98, so I don't have that flag, but Scratch seems to work just fine with the UA string edited to say 100 instead of 98:

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

My browser / operating system: Windows NT 10.0, Chrome 100.0.4758.102, No Flash version detected

Mine is

My browser / operating system: MacOS Macintosh X 10.15, Firefox 107.4, No Flash version detected

(Custom UA goes brr )

VedanshS933 wrote:

ideapad-320 wrote:

My browser / operating system: ChromeOS 14324.80.0, Chrome 97.0.4692.102, No Flash version detected
My actual user agent: Mozilla/5.0 (X11; CrOS x86_64 14388.52.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4758.91 Safari/537.36 (Chrome 100 on Chrome OS 14388)
Fun fact: scratch works. It also does not use your user agent.
For this to effect affect a website it has to be big enough to have a version detector but small enough to not fix it in time.

Right, can you update to Chrome 98? It would be safer I think as I don't use Chrome

mbrick2 wrote:

Scratch137 wrote:

(#46)

mumu245 wrote:

god286 wrote:

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

Does Scratch work with the flag?

I'm using Edge Stable 98, so I don't have that flag, but Scratch seems to work just fine with the UA string edited to say 100 instead of 98:

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

My browser / operating system: Windows NT 10.0, Chrome 100.0.4758.102, No Flash version detected

Mine is

My browser / operating system: MacOS Macintosh X 10.15, Firefox 107.4, No Flash version detected

(Custom UA goes brr )

erencemaltay wrote:

mbrick2 wrote:

Scratch137 wrote:

(#46)

mumu245 wrote:

god286 wrote:

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

Does Scratch work with the flag?

I'm using Edge Stable 98, so I don't have that flag, but Scratch seems to work just fine with the UA string edited to say 100 instead of 98:

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

My browser / operating system: Windows NT 10.0, Chrome 100.0.4758.102, No Flash version detected

Mine is

My browser / operating system: MacOS Macintosh X 10.15, Firefox 107.4, No Flash version detected

(Custom UA goes brr )

what? FIREFOX 107???

erencemaltay wrote:

what? FIREFOX 107???

mbrick2 wrote:

erencemaltay wrote:

what? FIREFOX 107???

Custom User Agent

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.

completeness wrote:

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.

Couldn't browsers list their version as the newest chrome version before Chrome 100 in the user agent string for old websites to not detect the wrong version, and include the real version at the end for newer websites that updated their user-agent parsing software? I'm pretty sure most information in user agent strings is false for this exact reason.

Chiroyce wrote:

I went the through the posts in this topic and didn't see any mentioning how v100 could break some websites, so I'll mention it here.

Some websites which use modern technologies found in modern browsers often like to check what version of s browser their clients are using, they simply check the first two digits of the version number. If they see v30 or v40 they're gonna tell you that you're using an unsupported version of the browser. Now imagine this, what are the first two digits of 100? 10 right? And v10 is very well below v90 or v30 or v40, so the server will think that we're using an extremely old version of the browser and will refuse the send us the content of the site.

Chiroyce wrote:

I went the through the posts in this topic and didn't see any mentioning how v100 could break some websites, so I'll mention it here.

Scratch137 wrote:

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 wrote:

and by s you mean User Agent String right?

god286 wrote:

Chiroyce wrote:

I went the through the posts in this topic and didn't see any mentioning how v100 could break some websites, so I'll mention it here.

Scratch137 wrote:

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 wrote:

and by s you mean User Agent String right?

I think it's meant to be a. On the QWERTY keyboard A is next to S.