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
On Mar 28, 2008, at 9:36 AM, David Kilzer wrote:
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
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
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
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 [EMAIL
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
6 matches
Mail list logo
