W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2013

Re: Standardizing console APIs: Where?

From: Garrett Smith <dhtmlkitchen@gmail.com>
Date: Fri, 22 Feb 2013 20:49:17 -0800
Message-ID: <CABZUbM0TJMng2LP_iBaLt-67JvumBn3KDJon9ep1G_3Xfg-UWw@mail.gmail.com>
To: Brian Kardell <bkardell@gmail.com>
Cc: es-discuss <es-discuss@mozilla.org>, public-script-coord@w3.org
On 2/22/13, Brian Kardell <bkardell@gmail.com> wrote:
> Recently I read a post about Chrome adding a console.table API which
> mentioned some things in other browsers.  My immediate reaction was "is
> this a new proposal for addition to console standard API, because that
> could be pretty handy actually" but then after a moments pause and about an
> hour search, I realized:  There is no codified standard for console API.
>  Turns out that public-browser-tools-testing@w3.org has sort of agreed to
> take it up, but it doesn't seem like anything much has happened yet and I'm
> wondering why that should be bound to anything with the browser since
> console is a pretty universal thing in implementations.  Not saying it
> should or shouldn't be ECMA, just that it seems to be in the wrong place
> now if, indeed, anything is happening there.
> So what does everybody think?

Start by testing and documenting the various console APIs.

> It seems that there is already a subset of what's implemented out there as
> a de-facto standard and could be some low-hanging fruit to create a base
> standard on which others could propose against, provide prollyfills for,
> etc - and that would be a pretty good thing IMO.  Over the years, just a
> couple of anomalies in browsers have caused some pain - let's write it down
> somewhere :)

Yes, tables of functionality by implementations, replete with
comprehensive tests.
Twitter: @xkit
Received on Saturday, 23 February 2013 04:49:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:08 UTC