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