NoOp wrote:
On 01/31/2013 06:39 AM, Matthias Kahlert wrote:
Am 31.01.2013 10:43, schrieb Rob:
...
When a problem can be worked around by using a new profile, it should
always be possible to determine what part of the profile is the cause.
Yes, but that is a very tedious task, so I hoped someone might know the
solution.
After some more testing (the new profile that worked yesterday has again
ceased to do so today) it seems that pluginreg.dat might be the culprit,
which doesn't even sound far-fetched with hindsight...
https://support.mozilla.org/en-US/kb/how-to-use-java-if-its-been-blocked
Just a comment, The "always allow java" section is really a map to "always allow
*every plugin*" and ignores the case where the java is trusted but some other
aspects of the site, such as flash, might not be. That might well not be the
action of chaice in all cases.
--
Bill Davidsen <[email protected]>
We are not out of the woods yet, but we know the direction and have
taken the first step. The steps are many, but finite in number, and if
we persevere we will reach our destination. -me, 2010
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
