- From: <bugzilla@jessica.w3.org>
- Date: Wed, 29 Sep 2010 17:39:28 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10694
Edward O'Connor <hober0@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hober0@gmail.com
--- Comment #7 from Edward O'Connor <hober0@gmail.com> 2010-09-29 17:39:28 UTC ---
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
--
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 17:39:30 UTC