aroben at apple.com
Thu Mar 27 19:09:41 PDT 2008
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.
> Max Barel <a_x at 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
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
More information about the webkit-dev