• Some reporters are aligned incorrectly, with lists to the right and boolean inputs to the right.

• The editor crashes when you switch the “Rays” backdrop to bitmap, then vector.

• There is a small gap in block dropdowns.

• Once you go to a sound in the Sounds tab, the sound becomes quieter (most likely due to problems with MP3).

• A user has reported that a bitmap circle does not go to bitmap from vector when deselecting.

• The color input disappears once you undo in a color reporter.

• After some time, a long sound gets completely muted.

• A blank stack My Block is partially cut.

• A user has reported that the sound editor does not load and clicking sprites after throws an error.

• The bug above has also been reported to continue the Choose a Sprite dropdown.

• The sprite deletion popup goes off-screen when attempting to delete a sprite.

• The Debug button causes the project name and the Share and See Project Page buttons to be condensed, including projects that you have not shared.

• The Debug icon does not load in some devices.

• The Scratch cloud monitor page does not load (this includes cloud variables). This is caused by an endpoint the clouddata website is pointing to. No latency is found, yet there is still DNS.

• The first profile comment is older than the account itself.

• Signatures go high enough to make you see its purple background.

• The navbar does not fit with the Sign In and Join Scratch in 2.0 pages.

• All projects are indexed slowly.

• The wrong OP is said when the Scratch Team merge a forum topic.

• Project thumbnails could potentially break.

• When on https://scratch.mit.edu/accounts/login, the next function (example: ?next=/mystuff/) does not work.

• The error breaks if you attempt to comment with an unsupported emoji.

• The alert for deleting a studio is empty.

• The Hosted by Me list remains empty.

• The Debug button in the editor's background color width is too small.

• The “report” button is not capitalized.

• The new topic tooltip should be updated to reflect the updated, new forums.

• In the BBCode toolbar, the dropdowns are bigger than the arrows. The Scratchblocks icon in the toolbar is a 2.0 stack block, rather than a 3.0 one.

• The unread messages counter on Scratch does not expand.

• The search bars on 2.0 pages have an inlet div.

• The “studios the project is in” counter always says 0.

• In 2.0 pages, the Scratch Wiki links to its original domain, wiki.scratch.mit.edu.

• The language set does not locale, which should change the types of projects you would see in the Explore tab.

• When adding a new post to a topic, the page does not reset to 1.

• You can go to any site when in the post preview.

• In 2.0 pages, “Adobe Flash Player is not supported” appears when Scratch loads the page.

• Most likely due to Internet issues, you can comment twice instead of once.

• Some parts of the Scratch homepage do not load, mainly because the Scratch Team have paused Front Page Curators.

• Scratch project running has worse performance in Firefox.

• In 2.0 pages, you can hover over the Scratch logo from just two pixels down.

• In 2.0 pages, there is no <hr> tag in the account dropdown.

• Some users have made topics or posts but the post counter says “0 posts”.

• Sort by Remixes option does not show all projects and is in the incorrect order.

• A user has reported that projects in the Explore page would not load.

• Scratchers, regardless of fame and how helpful they are, repeatedly get signed out. This is a different bug.

• Ghost messages occur, where a user gets a few messages until realizing they never existed at all.

• Parts of the home page fail to load.

Template (QnA) wrote:

Username: (fill)
Source: (fill if available)
Question: (fill)
Answer: (fill)

Template (Bug) wrote:

Username: (fill)
Source: (fill if available)
Bug: (fill)
Image: (fill)

Template (Useful links) wrote:

Username: (fill)
Topic: (fill)
Bug: (fill)
Image: (fill)

Scratch_Cat_Coder8 wrote:

The OP is inactive cause they absolutely have to be inactive, it’s stated on their profile. I don’t think that can render the old topic completely unusable.

acohen_bhusd wrote:

Scratch_Cat_Coder8 wrote:

The OP is inactive cause they absolutely have to be inactive, it’s stated on their profile. I don’t think that can render the old topic completely unusable.

they actually decided to use things other than scratch, no activity = stickied topic

Scratch_Cat_Coder8 wrote:

acohen_bhusd wrote:

Scratch_Cat_Coder8 wrote:

The OP is inactive cause they absolutely have to be inactive, it’s stated on their profile. I don’t think that can render the old topic completely unusable.

they actually decided to use things other than scratch, no activity = stickied topic

-snip-

acohen_bhusd wrote:

Scratch_Cat_Coder8 wrote:

acohen_bhusd wrote:

Scratch_Cat_Coder8 wrote:

The OP is inactive cause they absolutely have to be inactive, it’s stated on their profile. I don’t think that can render the old topic completely unusable.

they actually decided to use things other than scratch, no activity = stickied topic

the while should be one month, not two months

acohen_bhusd wrote:

okay, i still want my topic to be stickied

Scratch_Cat_Coder8 wrote:

acohen_bhusd wrote:

okay, i still want my topic to be stickied

You don’t have the ability to have that to be your choice to make. It’s the choice of the scratch team and the users who think wether or not the current topic is fine. Also, did you get permission? That’s one of the biggest parts. And tbh at this point yeah I can see why you would make this topic I’m not gonna argue anymore. (it is still kinda hard to take you seriously still )

You need to have explicit permission from the owner or the Scratch Team.

guides or attempts to create stickies are for the most part under a restrictive policy, and unless you have permission from other sticky owners or the Scratch Team (or if the Scratch Team deems the sticky extremely important), you may not get the sticky.

Remember that the reason for getting new ownership of topics like these most likely shouldn't be for bragging rights or to get famous.

SidewaysCoder wrote:

Here is what I said in your 2 previous topics:

You need to have explicit permission from the owner or the Scratch Team.

guides or attempts to create stickies are for the most part under a restrictive policy, and unless you have permission from other sticky owners or the Scratch Team (or if the Scratch Team deems the sticky extremely important), you may not get the sticky.

Remember that the reason for getting new ownership of topics like these most likely shouldn't be for bragging rights or to get famous.

acohen_bhusd wrote:

SidewaysCoder wrote:

Here is what I said in your 2 previous topics:

You need to have explicit permission from the owner or the Scratch Team.

guides or attempts to create stickies are for the most part under a restrictive policy, and unless you have permission from other sticky owners or the Scratch Team (or if the Scratch Team deems the sticky extremely important), you may not get the sticky.

Remember that the reason for getting new ownership of topics like these most likely shouldn't be for bragging rights or to get famous.

i know already