|Warning:||This page is very probably out of date. Try the issue tracker on GitHub. (Although you might still like to discuss bugs here before reporting them.)|
This page is a list of bugs in the new 2.0 Block Plugin by blob8108.
The wiki usually lags behind the latest version of the plugin. Before reporting a bug, please test it on the plugin test page. If the bug doesn't happen there, then all you've found is that the wiki's out of date. Go bug scmb1 to update the wiki or something.
If you have a Github account, it'd be awesome if you could add the bug directly to the issue tracker.
Otherwise, click "Add Topic" at the top to add a bug. Be descriptive and give an example. Write the example here in a
<scratchblocks> tag, sign with four tildes (~~~~), and also provide a link to the test page showing the same example. Thanks!
You can comment on a bug like you can on a talk page. Just remember to indent your post(s) and sign them.
The archive can be found here. Move finished discussions there.
say <mouse down?>
Some blocks appear obsolete when there is a space between the argument and the last character.
set size to (100) % <color [#FF0000] is touching [#FF0000] ?>
- MediaWiki is sneakily converting those spaces into non-breaking spaces. I'll have a play with the wiki extension and see if I can stop that.
Blob8108 (talk | contribs) 13:06, 19 May 2013 (UTC)
Bottoms of C blocks
The lengths of the bottoms of C blocks do not match the lengths of their tops and are too short.
when gf clicked forever if <loud?> turn ccw (1) degrees ask [Hello, I'm Scratch Cat. What's your name?] and wait if < (answer) = [XYZ] > say [Wow. Wow! WOW!!!] for (2) secs end
- I spent a good while trying to do this one, but I think it's probably a CSS limitation. I'm not sure it's worth fixing, either.
Blob8108 (talk | contribs) 08:27, 11 June 2013 (UTC)
- There's a trivial JS fix for this, but it causes nasty flickering when the page refreshes.
Blob8108 (talk | contribs) 11:50, 11 June 2013 (UTC)
C Blocks that repeat need the arrows at the bottom.
repeat (10) move (5) steps end
- Added #23.
- How boring. I really can't be bothered to do this one. :P
- Sci knows CSS, he can fix it! :D
Blob8108 (talk | contribs) 19:26, 31 August 2013 (UTC)
Stop () block when "other scripts in sprite"
The Stop () block should render as a stack when set to "other scripts in sprite". I'll add it on GitHub when I get the chance, probably tomorrow.
stop [other scripts in sprite v]
Lego We-Do/SensorBoard blocks wrong color
- Yeah, fixed in the rewrite I'm working on. :)
blob8108 (talk | contribs) 20:36, 9 November 2013 (UTC)
10^On the forums
([10^ v] of ())appears as a Sensing block.
3sal2 (talk | contribs) 01:36, 4 August 2014 (UTC)
- This is only for bugs on the Wiki
derpmeup (talk | contribs) 22:31, 3 October 2014 (UTC)
- Fixed, eventually
blob8108 (talk | contribs) 19:54, 28 November 2014 (UTC)
Boolean insert in custom-arg block
Plugin Not Taking Place
Although my always on does not pass acid3, this is still a bug. all blocks appear just as text in code tags, for example:
when gf clicked
when gf clicked
No new extension blocks. Old ones work fine.
when [slider v] [> v] (50) when distance [< v] (20) when tilt [= v] (1) turn [motor v] on for (1) secs turn [motor v] on turn [motor v] off set [motor v] power to (100) set [motor v] direction [this way v] when distance < (20) when tilt = (1) turn motor on for (1) secs turn motor on turn motor off set motor power (100) set motor direction [this way v]
Scratch Wiki Extension block color
In the Scratch Forums and blob8108's block renderer, all extension blocks, such as Lego WeDo and PicoBoard appears to be grey as normal. But in the Scratch Wiki, all extension blocks are purple instead.
([slider v] sensor value)