No, "readonly" has nothing to do with anything. That's just a feature of
BBEdit. Readonly is a red herring. You can't call enablePrivilege unless
your script is signed, or it's loaded from file://, or you've enabled
codebase principals. That has always been the case and didn't change
with 0.9.5. You probably just forgot to enable codebase principals.
Note that codebase principals are meant for use during development and
debugging only. By setting codebase_principal_support to true, you are
weakening the security of the browser by allowing unsigned scripts to
enable privileges. But that's up to you.
-Mitch
Thad Hoffman wrote:
> it appears that for some reason or another this build was released with
> all the pref.js files in readonly mode and therefore appear to not allow
> scripts to change the settings, as once I went into all.js and edited it
> in teh "readonly mode" offered by BBEdit and changed this line from
> false to true (which I have never had to do before):
>
> pref("signed.applets.codebase_principal_support", true);
>
> the code now works and lets me access cross domains again.
>
> Does this theory appear sound to the Moz team? The files readonly status
> is the only difference I can see that isn't hidden by compiled code.
>
> I could be way off my rocker, but we did that netscape.security line to
> prevent all the users from having to hand edit their preferences...
> could be why it works in Netscape 6.2 (I know it is 094 based not 5 0r
> 6, but the pref files aren't in a readonly state).
>
> Thoughts?
>
>
>
>
