W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2010

[Bug 10694] Specify window.console

From: <bugzilla@jessica.w3.org>
Date: Wed, 29 Sep 2010 18:05:30 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1P1122-0007uh-S1@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10694

--- Comment #8 from Maciej Stachowiak <mjs@apple.com> 2010-09-29 18:05:29 UTC ---
(In reply to comment #7)
> I think I'll take a stab at speccing window.console.
> 
> Maciej, you wrote:
> > We added console.log and a few related calls in Safari in part because
> > sites broke occasionally due to a stray console.log. Realistically, a
> > new browser would have to include the console object to achieve a
> > competitive level of compatibility.
> 
> I went looking for what the few related calls might be: when
> window.console was originally added to WebKit[1], its error, info, log,
> and warn methods were added. Since then, WebKit has added a bunch more
> to its Console object[2]; do you have a sense for how much of that is
> needed for interop with web content?
> 
> 
> Ted
> 
> 1. http://trac.webkit.org/changeset/27161
> 2.
> http://trac.webkit.org/browser/trunk/LayoutTests/fast/dom/Window/window-properties-expected.txt#L2171

The first round was driven in part by the desire to keep sites working. Most of
the subsequent additions were to enable debugging compatibility between the Web
Inspector and Firebug, not for stray calls left on sites.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 29 September 2010 18:05:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:25 UTC