Test-Scratch-Wiki:Block Plugin Bugs/Archive

Any discussions that were closed should be moved from the original page to here as soon as possible under a header showing the current month. Please do not edit any discussions here. Revive bugs on the current page.

List reporters
There is no way to differentiate variable and list reporters. (variable) (list)
 * Just make a list block inside the same scratchblocks tag:

add [x] to [list v] say (list) Blob8108 13:06, 19 May 2013 (UTC)
 * but what if i simply want to use the list without doing anything with it? shouldn't there be some text at the beginning (something like list:) that turns it red without needing an entire block before it? MF231 13:24, 19 May 2013 (UTC)
 * "list:" would look messy -- remember the code renders as plain text if Javascript's disabled. It's used so rarely that I'm not convinced it's worth it. And remember, you could always have a variable with a name starting "list:"... :P Blob8108 12:22, 20 May 2013 (UTC)

Free-floating inputs
You can have freely floating number inserts, string inserts, and dropdowns. (...) (2) [hello world] [dropdown v]
 * This is a bug, insofar as you could create a custom block with no text and a single argument. Blob8108 13:06, 19 May 2013 (UTC)
 * Should be fixed now. Blob8108 12:22, 20 May 2013 (UTC)
 * Not fixed. Mathfreak231 Talk to me! I did that! 20:33, 20 May 2013 (UTC)
 * Well, it was fixed on GitHub... Lightnin just hadn't updated the wiki extension yet. :P Works now. Blob8108 19:47, 21 May 2013 (UTC)

Empty Booleans
Empty Boolean inserts, when not in a block, render as a blank Operators block. <>
 * Again, not really a bug. (What should it do in that situation?) Blob8108 13:06, 19 May 2013 (UTC)
 * should it render as an obsolete block? Mathfreak231 Talk to me! I did that! 20:33, 20 May 2013 (UTC)
 * No, I don't think so. Blob8108 07:17, 21 May 2013 (UTC)

Obsolete blocks
An block shows in a slightly darker color than the real thing. obsolete! Curiouscrab (talk | contribs) 02:15, 11 June 2013 (UTC)
 * They are actually the darker colour in 2.0, the last time I checked. Blob8108 13:06, 19 May 2013 (UTC)
 * do the blocks that say "obsolete!" appear dark? MF231 13:24, 19 May 2013 (UTC)
 * Drop a "loud?" block into a Scratch 1.4 project, load it into Scratch 2.0, and have a look! Blob8108 12:22, 20 May 2013 (UTC)
 * I mean the blocks that literally say "obsolete!". If there are any in 2.0. MF231 20:16, 20 May 2013 (UTC)
 * Not as far as I'm aware. Blob8108 07:17, 21 May 2013 (UTC)
 * It should be the same. It shouldn't matter. If it's obsolete, it's one shade of red.
 * Okay, closing. Mathfreak231 Talk to me! I did that! 20:13, 11 June 2013 (UTC)

Puzzle slots in "else"
When using the "stop []" block before "else", a notch appears in the "else". if  then stop [this script v] else say [Put the mouse down!] Mathfreak231 Talk to me! I did that! 00:30, 11 June 2013 (UTC)
 * Dangit, I thought I'd got all of these. Blob8108 08:32, 11 June 2013 (UTC)
 * Added #16.
 * Fixed on Github. Blob8108 07:53, 25 June 2013 (UTC)
 * Fixed on wiki. Mathfreak231 12:19, 28 June 2013 (UTC)

Obsolete Booleans Show as Operator Reporters/Booleans

 * This is also on the forums. Curiouscrab 19:43, 2 September 2013 (UTC)
 * Not a bug. Replied on the forums. Blob8108 19:58, 2 September 2013 (UTC)
 * Saw and replied. Curiouscrab 20:14, 2 September 2013 (UTC)

Distance Custom Variable = Purple
Let me show you:

set [Distance v] to (90) set [Distance+2 v] to ((Distance) + (2))

If anything, I'd think Distance would become blue. ErnieParke 14:10, 15 September 2013 (UTC)
 * Huh, weird. You're right, distance shouldn't be purple. It should be red. Blob8108 14:38, 15 September 2013 (UTC)
 * Wait! It is a block in Scratch. It's in the list of blocks. It's one of the Lego WeDo blocks. Not a bug! :) Blob8108 14:40, 15 September 2013 (UTC)
 * Exactly. If you want, you can name the variable something like "dist" instead. (it corrected "dist" to "diet" :P ) Mathfreak231 14:58, 15 September 2013 (UTC)

Boolean inserts
The boolean inserts aren't wide enough. They seem so thin, and it bothers me whenever I see it on Default Value... <<> and <>> Mathfreak231 00:05, 7 July 2013 (UTC)
 * Play around with setting the width via CSS in Chrome's inspector, and let me know what width they should be! Blob8108 17:18, 10 July 2013 (UTC)
 * .boolean.empty {padding: 2px 10px} PS: Go Firefox. Scimonster 17:22, 10 July 2013 (UTC)
 * That looks a bit too wide to me.
 * PS. "(Chrome|Safari's)'s inspector|Firefox's Firebug|Opera's Dragonfly|IE's Developer Tools" seemed a little wordy. :P Blob8108 17:47, 10 July 2013 (UTC)
 * It doesn't look too wide. It's around the same width as in the image above.
 * You know Firefox has it's own awesome devtools, without Firebug? Now i only use Firebug for the advanced console and DOM editing. But the native devtools have stuff (box model, fonts, scratchpad, style editor, 3D view) that Firebug doesn't. And... "devtools" is even shorter. :P Scimonster 18:25, 10 July 2013 (UTC)
 * The 3D view seemed cool, but when I tried to use it to debug z-indexes I found it basically useless. I'll go with "devtools" in future, thanks. :P Blob8108 07:56, 11 July 2013 (UTC)
 * 3D view is more of a visual DOM rendering. Scimonster 09:14, 11 July 2013 (UTC)
 * Is there any way to make the height shorter? I think that's why Sci's idea looked so big. Sorry if I'm being too needy... :P Mathfreak231 12:34, 11 July 2013 (UTC)
 * {padding: 1.5px 10px} makes it 1px shorter. Scimonster 13:29, 11 July 2013 (UTC)

I think I fixed this ages ago... <<> and <>> Blob8108 15:22, 15 September 2013 (UTC)

Blocks Ruin Header
Click here and then look at top blue header. The blue header on the Scratch Wiki Skin is sent back layers and the blocks are brought to front.

Scroll down until a block is right below the blue header at the top of the browser viewing area. Now go up some more until it should be behind the blue header. Only occurs with blocks that have stubs on bottom and comments. //This is a comment that has that bug. Block //This block will have that bug. Curiouscrab 18:33, 24 June 2013 (UTC)
 * Yeah, it's a bug in the skin, not the plugin — it's on the skin bug list. It's a trivial fix, actually. Maybe I'll just go do that... Blob8108 20:22, 24 June 2013 (UTC)
 * I don't see anything unusual... It seems that only the image stuff (puzzle piece stubs and edges of C-blocks) get screwed. Mathfreak231 Updated 13:46, 10 July 2013 (UTC)
 * I thought this was fixed -- Scmb1 said on GitHub that they'll update it soon. Blob8108 17:17, 10 July 2013