Any content loaded as chrome has no security restrictions at all, and
you shouldn't have to call enablePrivilege. XUL files which are not
loaded as chrome (installed in the browser chrome directory and accessed
with a chrome:// URL) are treated exactly the same as HTML files. If you
load a XUL file via the Open File dialog, that's the equivalent of using
the file: protocol, which requires enablePrivilege calls.
If you're still having trouble, please send me a complete, minimal
testcase that demonstrates the problem, and I'll try to diagnose it.
-Mitch
rvj wrote:
> PS Ive tried using just the file references as you suggest
>
> Ive opened the test xul file via Mozilla's open file option but even
> though I get the Internet Security dialog box asking me to allow enhanced
> priviliges and accept, setting the event's screenX or screenY property
> still fails
>
> Can you confirm that Mozilla should be able to set these javascript
> attributes/properties as follows
>
> function mousedowns(event)
> {
>
> netscape.security.PrivilegeManager.enablePrivilege("UniversalBrowserWrite");
>
> alert("before"+event.screenX)
> event.screenX=event.screenX+1
> alert("after"+event.screenX)
> }
>
>
>
>
