Boris Zbarsky wrote:
> Bryan White wrote:
>>  netscape.security.PrivilegeManager
>>         .enablePrivilege("UniversalXPConnect");   
> 
> Hmm.  It's really odd that you're getting 
> NS_ERROR_XPC_SECURITY_MANAGER_VETO after that.
> 
> I assume you can't really make a testcase available that would 
> demonstrate the problem, right?  Would you be able to hunt down a 
> one-day regression range using the 1.8.0 builds from 
> <http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/>?  For example, 
> http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2008-03-28-04-mozilla1.8.0/
>  
> has builds from March 28, 2008.  There are also 2008/ and 2007/ 
> directories for older builds....
> 
> Given a one-day range, it should be possible to figure out which exact 
> code change caused the behavior change and see what's going on...

The test case is here:

http://www.arcamax.com/testcase/

this works:
http://ftp.mozilla.org/pub/mozilla.org
    /firefox/nightly/2008/03/2008-03-06-12-mozilla1.8
    /firefox-2.0.0.13pre.en-US.win32.installer.exe

this fails:
http://ftp.mozilla.org/pub/mozilla.org
    /firefox/nightly/2008/03/2008-03-07-03-mozilla1.8
    /firefox-2.0.0.13pre.en-US.win32.installer.exe

Bryan
_______________________________________________
dev-security mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security

Reply via email to