Min/default/max would be awesome.
Yeah. BTW that was your idea. I'm now going to make a commit that hopefully adds it, but most likely will give me an error. You can test it here.
I know; I still bug Jens about it periodically. :~)
Yeah. BTW did you look at my new post on "Min/default/max for custom blocks"?
Edit: nevermind you did.
I guess that also explains why my test in the dev/7.0 didn't require checking 'Javascript extensions'
Yup.
A SIGSEGV is an error(signal) caused by an invalid memory reference or a segmentation fault . You are probably trying to access an array element out of bounds or trying to use too much memory.
I have 2 tabs open. Ugh.
It shouldn't be possible for a web page to segfault, so I'm gonna guess there's a Chrome bug involved here.
sigh, I don't know what's going on here:
Oh wait, it's not the set blocks that are the problem it's the Variable Show-ers
Oh, yes, that's a known limitation. Someday...