On 08/29/2013 11:27 AM, Roger Fink wrote:
-------- Original Message --------
I just upgraded from SM 2.15 to 2.20. Now, when I activate java (default
state being inactive) , the browser overrides my selection. What do I
need to do to gain control over my own computing decisions?
Fixed, but I'm not very happy with what SeaMonkey has done here, and if
there is a workaround (i.e. revert to the former behavior) I'd like to
hear about it..
About:plugins gives you two choices with the Java plugin, always enabled
or always disabled. This is different than in 2.15.
Enter about:config, look for "plugins.click_to_play", toggle it to "true".
That will add "Ask to Activate" to the other two options for all
plugins. Select "Ask to Activate" for your Java plugin.
The default upgrade setting is always disabled, so that's what was
preventing Java from launching. When you change it to always enabled
your launch problems go away but now every time you open the browser
java is enabled by default, an accident waiting to happen. I can disable
it from the GUI using prefbar (which most people are not set up to do),
but I need to do that every time I reopen. It's not an intuitive use of
the browser to go into about plugins on a per application basis. The
biggest problem with all Mozilla products lately is their headlong
plunge into counterintuitiveness. SeaMonkey is the best of the bunch at
avoiding that, but they've done it here.
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
