Bill Davidsen wrote:
Rufus wrote:
jim wrote:
On Tue, 22 Dec 2009 14:15:20 -0800, Rufus <[email protected]> in
mozilla.support.seamonkey wrote:
Jens Hatlak wrote:
Leonidas Jones wrote:
[JS in MailNews]
As I am sure you know, but for those who do not, in about:config:
javascript.allow.mailnews
Set to true.
That won't have any effect. JS in MailNews is gone for good:
<http://kb.mozillazine.org/Javascript.allow.mailnews>
The reason that the pref is still appearing in about:config is that
the
relevant patch applies against core code which follows different time
schedules. The pref will be removed from about:config in SeaMonkey
2.1.
<https://bugzilla.mozilla.org/show_bug.cgi?id=248280>
HTH
Jens
I guess this doesn't surprise me. Just one more example of the
interface not being in step with the code...now I can't trust what I
see in about:config or what it actually does either?
Thanks.
But hasn't that always been the case, stretching back into netscape?
I believe that there are some vestigial files as well...........
jim
And that's why I'm not a fan of fiddling with about:config...user
input/control should be provided in user Preference panels - it's one
thing if I come here and get info on a workaround from a knowledgeable
individual, in advance of a forthcoming fix, but as a general, generic
user I should never even have to think about about:config.
And someone will tell you you can use voodoo to add config things to
your custom preferences, which I personally think is even less obvious.
But the root issue is that stuff should work and the tricks should be
documented elsewhere than the source or some developer's notes.
Agreed.
I don't mind learning to work around by visiting a forum, doing a Google
search, or consulting a knowledge base - but I do mind that workaround
not being of a temporary nature...a VERY temporary nature.
--
- Rufus
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
