Page 1 of 1

javascript uri

Posted: Sat Jul 25, 2009 7:49 pm
by SD-DAken
Type

Code: Select all

javascript:function b(){}
into the location bar and press enter.

In the Compiled Scripts view this will show up as:
19:24:13.149


Script: javascript:function%20b(){}
Line: 1

function b() {
}



19:24:13.154


Script: javascript:function%20b(){}
Line: 1

function b() {
}


function b() {
}
In the Executed Scripts view as:
19:24:13.157


Script: javascript:function%20b(){}
Line: 1


Number of calls: 1

Average execution time (ms): 1


function b() {
}


function b() {
}
1) Why is there shown

Code: Select all

    function b() {
    }


    function b() {
    }
and not only

Code: Select all

    function b() {
    }
2) If you click on the "link" an empty View Source window will open and

Code: Select all

Error: uncaught exception: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebNavigation.loadURI]"  nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame :: chrome://global/content/viewSource.js :: viewSource :: line 221"  data: no]
will be printed to the error console.

Posted: Thu Aug 06, 2009 12:00 am
by Wladimir Palant
1) Good question, I wondered about this as well. This is a regression in Firefox 3.5, Firefox 3.0 didn't do that. Note that JavaScript Deobfuscator isn't creating the text representation of scripts itself - that information comes from the JavaScript engine.

2) Same happens if you click a javascript: URL in Error Console. It's an issue of the View Source window in Firefox, it cannot do anything meaningful with such URLs. The relevant bug is https://bugzilla.mozilla.org/show_bug.cgi?id=318245.

Posted: Thu Aug 06, 2009 1:07 am
by Wladimir Palant
1) Took some time to investigate this issue, filed https://bugzilla.mozilla.org/show_bug.cgi?id=508696 on it.

Re: javascript uri

Posted: Thu Dec 10, 2009 7:16 pm
by debs
This post was written in Jan of this year and still this is happening what is being done to resolve it?

Re: javascript uri

Posted: Thu Dec 10, 2009 7:38 pm
by Wladimir Palant
Which of the Mozilla bugs do you mean? Not that this is a good place to ask about progress. I rarely have time to pick up Mozilla bugs (particularly JS engine bugs, they are usually hard to resolve for me), if nobody else does there will be no progress.