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

Re: Standardizing console APIs: Where?

From: Robin Berjon <robin@w3.org>
Date: Mon, 25 Feb 2013 12:06:59 +0100
Message-ID: <512B45D3.8000106@w3.org>
To: Thaddee Tyl <thaddee.tyl@gmail.com>
CC: Brian Kardell <bkardell@gmail.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, es-discuss <es-discuss@mozilla.org>
On 25/02/2013 11:50 , Thaddee Tyl wrote:
> I beg to differ.
>
> The standard for console APIs is at
> <https://getfirebug.com/wiki/index.php/Command_Line_API>, along with
> other devtools-related standards.
> It is very functional (changes happen regularly by cross-browser
> consensus, and suggestions are welcome from anyone).
> Sure, not all devtools support it all, and they may have bugs, but
> they each strive to fix their implementation.
> Duplicating standards will only duplicate efforts.

I presume you actually meant: 
https://getfirebug.com/wiki/index.php/Console_API ?

I suspect that that page is actually Good Enough for the needs at hand, 
due to the fact that the interoperability requirements on the console 
API are nowhere near as stringent as those that apply to other parts of 
the stack.

If someone has a use case for stronger interop here, then it would be 
worthwhile looking into tightening that prose up. I don't personally see 
the use case, but I may well have missed it.

-- 
Robin Berjon - http://berjon.com/ - @robinberjon
Received on Monday, 25 February 2013 11:07:13 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:09 UTC