[webkit-dev] No more javascript parsing errors in console
Darin Adler
darin at apple.com
Fri Mar 28 09:42:51 PDT 2008
On Mar 28, 2008, at 9:36 AM, David Kilzer wrote:
> Adam Roben <aroben at 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
More information about the webkit-dev
mailing list