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 <[EMAIL PROTECTED]> 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
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo/webkit-dev
