apparently, making a custom block, adding a number slot and setting the default value to ANYTHING other than zero will make snap freak out. am i crazy or is this a serious bug?
i clicked the slot
i changed the type to 'number'
i set the value to '1'
i clicked OK
i clicked the clot again
i broke it
(im using windows 10, chrome browser)
I suggest opening a new tab and load Snap into it and try it again and see what happens then
same issue, it still broke
edit: i just realised, if you change the input type, then change the value again, it suddenly fixes itself
Can only suggest the usual tech support - clear cache/switch computer off and on again
... this only works for non-text inputs, huh
I’ve just noticed that I’m still on 11.0 so I’ll update to 11.0.1 and try again
ill restart my pc and see if that fixes it
I’m running 11.0.1 now and still OK for me
Hold up - mine won’t let me re-edit the parameter now 
Going to try a few other things and will report back
i restarted it, still not working.
I switched to Edge browser and got the same effect as you so it looks like it’s definitely a problem
oh this is a serious bug.
Jens is looking at the issue 
thanks for the report, I’ve apparently introduced this bug yesterday when adding support for translatable named numerical inputs (such as “random”, “last” or “auto”) for custom blocks. I’ve found and fixed the issue and will patch it within the hour along with a bunch of other small fixes.
the one thing that makes it worse is, im not using a chromebook
So it's definitely a source-code error, not a system error.