1) Enter the above string into the location bar, or go to https://junruh.mcom.com/mix.html and click on the navigator.usreAgent button. What is expected: A popup showing the userAgent string. What happens" A blank page opens up. Commercial builds - Win32 and Linux.

isn't brendan back?

I'm not quite back, but this surely isn't my bug (cuz I was away; and anyway it sounds like a XPToolkit sort of bug). Peter, can you find an owner? Sorry if I should have given it to gramps for further reassignment. /be

reproduced in today's bits, reassigning to danm for triage.

In Javascript Console you´ll find folling Message: JavaScript Error: line 0, column 0: access disallowed from scripts at javascript:alert(navigator.userAgent) to documents at another domain Source line:

cc mstoltz. is this a js security problem? need more info on why this should be a beta2 stopper.

Please see bugs 31818 and 28387, there's some discussion about this issue there. Previously, javascript: URLs ran in the trust domain of the currently displayed page. This may be insecure. As a temporary solution, Norris changed this behavior so that javascript: URLs run in their own trust domain, and so do not have access to the DOM of any page. This is probably not the best permanent solution. An alternative is for javacript: urls to run with the privileges of the page from which the url is loaded. This has turned out to be difficult to implement; I have a partial solution but it doesn't yet handle every case. With some help from someone who's familiar with webshell, I may be able to implement this solution. I don't know whether this is a Beta2 stopper, as I don't know who is depending on this use of javascript: URLs. If this is an important feature, then we should talk about how to allow it without compromising security.

Putting on [nsbeta2-] radar. Not critical to beta2.

Marking 4xp. Changing Summary from "javascript:alert(navigator.userAgent) creates blank page" to "javascript: URLs blocked from accessing DOM of own page by security model". Assessment: Providing backward compatibility with DOM0 JS 1.1 code on the web is a critical goal for the browser to be a viable product. javascript: URLs are fairly widely used even by beginning JS programmers and are common in the JS 1.1 code that's predominant on the web. Until we are executing the JavaScript code in javascript: URLs on legacy web pages, we won't even be detecting the other backward compatibility bugs we must have. We must fix this for nsbeta2 if we are to have any hope of finding the other b.c. bugs that will be exposed by executing the code in <A HREF="javascript: ..."> URLs in time to fix them for FCS. Clearing [nsbeta2-] to trigger re-evaluation. Recommend [nsbeta2+] stopper.

Agreed. I will fix this ASAP. Reassigning to me.

Putting on [nsbeta2+] radar for beta2 fix.

*** This bug has been marked as a duplicate of 31818 ***

Verified.

Mass changing Security:Crypto to PSM

Mass changing Security:Crypto to PSM

*** This bug has been marked as a duplicate of 31818 ***

V/dupe. Accidental reopen.