I know, but Abrowser doesn't block JavaScript by default, so in a question
about whether or not it would work, I saw no sense in bringing that up.
To be perfectly frank, I think we should be designing our browsers to block
all JavaScript by default. And until some functionality to finely control
JavaScript execution (up to and including choosing a different script instead
of the one requested) as outlined in my essay[1] is developed, enabling of
JavaScript should be indicated as a highly dangerous last resort attempt to
get the Web page to work.
Furthermore, while this is the state of affairs. the browser should have a
button to enable the user to do this just once to see the JavaScript-ridden
version of a single page (such that pressing a button reloads the page with
all JavaScript enabled, but leaves it disabled everywhere else and doesn't
cause the JavaScript to load again when the same page is loaded again). That
way, it could be shipped to people who aren't experts with JavaScript
disabled by default and not be useless to them. I proposed this a little more
than a month ago on the bug-gnuzilla mailing list and offered a $50 bounty
for a Firefox extension that does it, which still stands. Even better would
be for this to be integrated into IceCat and Abrowser.
