In theory, deleting the library or disabling it in the settings should have
the effect of disabling JS. The preferred approach is to leave the library
installed and disable in the settings if you do not wish to use it.
Certainly, deleting the library shouldn't cause crashes - IBrowse will only
show a requester about not being able to open it the first time in a session.
I've now fixed an issue where JS could be executed when the library was not
open, which is probably the MuForce hits that you saw - this largely involved
the onFocus, onBlur, onChangeText and onChangeTextarea handlers.
With the library available and JS disabled in the settings, on the most part,
everywhere JS is executed, it first checks if it is enabled or not. However,
to support JS being switched off/on on the fly, IBrowse will do
initialisation of JS stuff when the page is parsed (this involves opening
the library), but that doesn't mean it actually executes any JavaScript. If
you are seeing any JS errors pop up (with the library installed and JS
disabled), please forward example URLs.
--
Oliver Roberts / @Futaura /
www.futaura.co.uk