Blockly HTTP section missing

[rlkoshak (Rich Koshak)]

@Mherwege

I don’t know what it is and it can well be a bug.

That’s the main focus here I think though. Neither add-on was installed and yet the user was able to choose Blockly when creating a new script.

When neither add-on is installed the user shouldn’t have to option to create a rule that has no chance of working.

@Mherwege

Both can still work. Certain blocks are only available with jsscripting (the HTTP blocks), no Nashorn can be generated.

Does MainUI hide these blocks in this case?

Maybe the issue is MainUI defaults to Nashorn instead of checking that Nashorn is installed when JS Scripting is also not installed.

[Mherwege (Mark Herwege)]

@rlkoshak

Does MainUI hide these blocks in this case?

Yes, it does.

[Mherwege (Mark Herwege)]

@rlkoshak

Maybe the issue is MainUI defaults to Nashorn instead of checking that Nashorn is installed when JS Scripting is also not installed.

And that could very well be the problem. But I didn’t look into the code yet.