Im using the Snap! anti crash so that it doesn’t crash
If you’re typing in javascript, then it’s not a bug snap has to fix.
Ah, there you go, thank you.
I’m afraid that Jens will consider this a very low priority problem, since (a) it’s about coding in JS, and (b) in particular, the specific reason for allowing JS in the Options field of an input dialog has been obsoleted by the WHEN SLOT SIGNALS hat block.
So I’m afraid the response to this bug report may be that Jens will make me rewrite the Colors and Crayons library. :~(
how is this connected to the menu thing?
and, with a rewrite, would it use the new colors?
cus
do you notice a difference? There’s some javascript going on internally, checking that read-only dropdown
right, thanks.
and, with a rewrite, would it use the new colors?
Yes of course, if I get around to the rewrite, of course it’ll use first class colors.
If you don’t want to watch the GIF, here are the steps transcribed:
- Create a new custom block
- Create an input
- In that input, open the menu located in the gear button at the bottom-right, and choose “options…”
- Enter:
function(){
return {'a':Object.create(null)}
}
- Open the dropdown of the custom block
@askofep1, I recommend that next time, don’t only include a GIF for a bug that can be easily described by a step-by-step tutorial, especially with a video screen recording poorly transmuted to a GIF, in a way that caused the GIF to be three times slower than it should be.
sorry, I was in a rush