For mobile users, most projects are too big for it's storage, leading to the page crashing.

But sometimes, mobile users don't click a project to see it, only to interact with the comments section of that project, Eg:- to stop an advertiser, but there is a very short time window for interaction before the project above is too big to handle.

So I think there should be an option to stop loading a project, this will help mobile users also to interact with the comments section in projects!

Support. I have a huge project that only loads on my tablet for some reason and it got curated but sometimes it crashes and all i want to do is respond to comments

WindowsMeRules2000 wrote:

Support. I have a huge project that only loads on my tablet for some reason and it got curated but sometimes it crashes and all i want to do is respond to comments

Thanks!

Bump!

Instead of a stop loading button a pause loading button so if a project that is loading starts to lag it can be paused so the user can close other tabs and windows.

scratchgodo wrote:

Instead of a stop loading button a pause loading button so if a project that is loading starts to lag it can be paused so the user can close other tabs and windows.

If you accidentally clicked the pause button, it could cancel all the messages you were going to post if you aren't fast enough, reloading the page could be an easy workaround and it's easy to notice when you're about to click it.

Assuming the user made it on the device, it shouldn’t crash. However, this would be a nice feature, however, using something more powerful, like a computer, is what Scratch was designed for(coming from a mobile user!)
There are a few other ways- using another browser, clearing your cache, restarting the device, etc.

GIitchInTheMatrix wrote:

Assuming the user made it on the device, it shouldn’t crash. However, this would be a nice feature, however, using something more powerful, like a computer, is what Scratch was designed for(coming from a mobile user!)
There are a few other ways- using another browser, clearing your cache, restarting the device, etc.

That doesn't help much though, ussually, it still crashes.

The_Blue_J wrote:

GIitchInTheMatrix wrote:

Assuming the user made it on the device, it shouldn’t crash. However, this would be a nice feature, however, using something more powerful, like a computer, is what Scratch was designed for(coming from a mobile user!)
There are a few other ways- using another browser, clearing your cache, restarting the device, etc.

That doesn't help much though, ussually, it still crashes.

With the assumption you made it on mobile, it shouldn’t. But, the cache may not have enough room for the project itself, so clearing it is a good first step.
If you didn’t, its assumed you have access to a computer you could use, which you could use. Ultimately, if it is to big for mobile, than that’s always the best way to go.
Using another browser, this issue I’ve only ever had on Safari. When i use DuckDuckGo, it doesn’t crash for me, just gives me the error screen in the player. Same with Google. This happened on a Samsung phone and Apple iPad. Its only Safari, from my knowledge, where that issue is caused.
Also, the ST doesn’t include a suggestion cuz of numbers of supporters, they includes them cuz of why people support.

GIitchInTheMatrix wrote:

Also, the ST doesn’t include a suggestion cuz of numbers of supporters, they includes them cuz of why people support.

I think my supporters have supported for pretty good reasons.

The_Blue_J wrote:

GIitchInTheMatrix wrote:

The_Blue_J wrote:

GIitchInTheMatrix wrote:

Assuming the user made it on the device, it shouldn’t crash. However, this would be a nice feature, however, using something more powerful, like a computer, is what Scratch was designed for(coming from a mobile user!)
There are a few other ways- using another browser, clearing your cache, restarting the device, etc.

That doesn't help much though, ussually, it still crashes.

Also, the ST doesn’t include a suggestion cuz of numbers of supporters, they includes them cuz of why people support.

I think my supporters have supported for pretty good reasons.

I mean the list you have. They’re generally discouraged

GIitchInTheMatrix wrote:

The_Blue_J wrote:

GIitchInTheMatrix wrote:

Assuming the user made it on the device, it shouldn’t crash. However, this would be a nice feature, however, using something more powerful, like a computer, is what Scratch was designed for(coming from a mobile user!)
There are a few other ways- using another browser, clearing your cache, restarting the device, etc.

That doesn't help much though, ussually, it still crashes.

With the assumption you made it on mobile, it shouldn’t. But, the cache may not have enough room for the project itself, so clearing it is a good first step.
If you didn’t, its assumed you have access to a computer you could use, which you could use. Ultimately, if it is to big for mobile, than that’s always the best way to go.
Using another browser, this issue I’ve only ever had on Safari. When i use DuckDuckGo, it doesn’t crash for me, just gives me the error screen in the player. Same with Google. This happened on a Samsung phone and Apple iPad. Its only Safari, from my knowledge, where that issue is caused.
Also, the ST doesn’t include a suggestion cuz of numbers of supporters, they includes them cuz of why people support.

Not many people want to meddle with the settings unless they know what they're doing, Scratch is mostly a website for younger audiences

The_Blue_J wrote:

GIitchInTheMatrix wrote:

The_Blue_J wrote:

GIitchInTheMatrix wrote:

Assuming the user made it on the device, it shouldn’t crash. However, this would be a nice feature, however, using something more powerful, like a computer, is what Scratch was designed for(coming from a mobile user!)
There are a few other ways- using another browser, clearing your cache, restarting the device, etc.

That doesn't help much though, ussually, it still crashes.

With the assumption you made it on mobile, it shouldn’t. But, the cache may not have enough room for the project itself, so clearing it is a good first step.
If you didn’t, its assumed you have access to a computer you could use, which you could use. Ultimately, if it is to big for mobile, than that’s always the best way to go.
Using another browser, this issue I’ve only ever had on Safari. When i use DuckDuckGo, it doesn’t crash for me, just gives me the error screen in the player. Same with Google. This happened on a Samsung phone and Apple iPad. Its only Safari, from my knowledge, where that issue is caused.
Also, the ST doesn’t include a suggestion cuz of numbers of supporters, they includes them cuz of why people support.

Not many people want to meddle with the settings unless they know what they're doing, Scratch is mostly a website for younger audiences

You should learn how to hold down the volume and power button for a few moments if you’re on mobile anyways.

GIitchInTheMatrix wrote:

I mean the list you have. They’re generally discouraged

OK, it's been removed!

Bump

Someone forgot to bump this
I have a feeling the next message is probably “Don't necropost” :P

Support. I’m a mobile user and sometimes I just want to check are people saying anything about Super Mario Maker 4 in the comments but the project is so large that it immediately lags the website so much that there is only 15-20 seconds before crashing, but because of the amount of lag I’m only able to scroll like 3 comments.

-OdysseyCentral- wrote:

Support. I’m a mobile user and sometimes I just want to check are people saying anything about Super Mario Maker 4 in the comments but the project is so large that it immediately lags the website so much that there is only 15-20 seconds before crashing, but because of the amount of lag I’m only able to scroll like 3 comments.

Exactly, it would help in stopping spam and advertising and such

Support, I’m a mobile user and I’d rather just go off the page than wait for it to crash and not be able to do anything.

Dogs-are-amazing1 wrote:

Support, I’m a mobile user and I’d rather just go off the page than wait for it to crash and not be able to do anything.

Exactly, we should at least be able to interact with the comments section.