No more javascript parsing errors in console
Since Safari 3 is out, the console is integrated within inspector. While I enjoy the command line interface it provides, I noticed that parsing errors are no more shown in this console. There is a numbered red flag number next to the faulty file in left pane but I can't see corresponding errors. Are they elsewhere or else I'll post a regression bug. Max Barel _____________________________ Développement web2, XHTML, CSS, PHP/MySQL, JavaScript, Ajax http://ac-mb.info
This works for me with Safari 3.1 on Mac OS X 10.5.2. (I used <http://www.dmregister.com/> to test.) I think the trick is that you must have the Web Inspector open before you load the page to see the parsing errors. If that still doesn't work, please file a bug. Thanks! Dave Max Barel <a_x@ac-mb.info> wrote:
Since Safari 3 is out, the console is integrated within inspector. While I enjoy the command line interface it provides, I noticed that parsing errors are no more shown in this console. There is a numbered red flag number next to the faulty file in left pane but I can't see corresponding errors. Are they elsewhere or else I'll post a regression bug.
Max Barel _____________________________ Développement web2, XHTML, CSS, PHP/MySQL, JavaScript, Ajax http://ac-mb.info
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
David Kilzer wrote:
This works for me with Safari 3.1 on Mac OS X 10.5.2. (I used <http://www.dmregister.com/> to test.)
I think the trick is that you must have the Web Inspector open before you load the page to see the parsing errors.
It sounds like a bug to me that you have to have the Inspector open in order for JS parse errors to be recorded. We should get this filed as a bug. -Adam
Max Barel <a_x@ac-mb.info> wrote:
Since Safari 3 is out, the console is integrated within inspector. While I enjoy the command line interface it provides, I noticed that parsing errors are no more shown in this console. There is a numbered red flag number next to the faulty file in left pane but I can't see corresponding errors. Are they elsewhere or else I'll post a regression bug.
Max Barel _____________________________ Développement web2, XHTML, CSS, PHP/MySQL, JavaScript, Ajax http://ac-mb.info
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Adam Roben <aroben@apple.com> wrote:
David Kilzer wrote:
This works for me with Safari 3.1 on Mac OS X 10.5.2. (I used <http://www.dmregister.com/> to test.)
I think the trick is that you must have the Web Inspector open before you load the page to see the parsing errors.
It sounds like a bug to me that you have to have the Inspector open in order for JS parse errors to be recorded. We should get this filed as a bug.
Sorry...I confused the issue. I was talking about HTML parsing errors, not JavaScript parsing errors. JavaScript parsing errors do not require the Inspector to be opened for for me with Safari 3.1 on Mac OS X 10.5.2. Dave
On Mar 28, 2008, at 9:36 AM, David Kilzer wrote:
Adam Roben <aroben@apple.com> wrote:
David Kilzer wrote:
This works for me with Safari 3.1 on Mac OS X 10.5.2. (I used <http://www.dmregister.com/
to test.)
I think the trick is that you must have the Web Inspector open before you load the page to see the parsing errors.
It sounds like a bug to me that you have to have the Inspector open in order for JS parse errors to be recorded. We should get this filed as a bug.
Sorry...I confused the issue. I was talking about HTML parsing errors, not JavaScript parsing errors.
JavaScript parsing errors do not require the Inspector to be opened for for me with Safari 3.1 on Mac OS X 10.5.2.
It's worth emphasizing that the comment still applies, though, to the JavaScript parsing error problem. If there's a bug, please file a bug report. Bug reports sent only to the mailing list aren't as good and usually don't result in a fix. -- Darin
In fact, it's the other 'round: Javascript console does not show parsing error if opened before page load. Filed a bug at http://bugs.webkit.org/show_bug.cgi?id=18182 Max Barel _____________________________ Développement web2, XHTML, CSS, PHP/MySQL, JavaScript, Ajax http://ac-mb.info Le 28 mars 08 à 17:36, David Kilzer a écrit :
Adam Roben <aroben@apple.com> wrote:
David Kilzer wrote:
This works for me with Safari 3.1 on Mac OS X 10.5.2. (I used <http://www.dmregister.com/> to test.)
I think the trick is that you must have the Web Inspector open before you load the page to see the parsing errors.
It sounds like a bug to me that you have to have the Inspector open in order for JS parse errors to be recorded. We should get this filed as a bug.
Sorry...I confused the issue. I was talking about HTML parsing errors, not JavaScript parsing errors.
JavaScript parsing errors do not require the Inspector to be opened for for me with Safari 3.1 on Mac OS X 10.5.2.
Dave
participants (4)
-
Adam Roben
-
Darin Adler
-
David Kilzer
-
Max Barel