On 8/29/13 8:34 AM, Roger Fink wrote: > > > -------- Original Message -------- >> >> -------- 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. >> >> 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. > > Actually prefbar let's me uncheck it but I don't think it's really doing > anything, which makes the situation much worse. >
If you do not have it, you should update to PrefBar 6.2.2. See <http://prefbar.tuxfamily.org/help/use.html#preferences.plugintoggle.mode>. All this is because the internal guts of Firefox (used by SeaMonkey) changed to "protect" users. -- David E. Ross <http://www.rossde.com/> Concerned about someone (e.g., the government) snooping into your E-mail? Use PGP. See my <http://www.rossde.com/PGP/> _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
