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

Re: Standardizing console APIs: Where?

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Thu, 28 Feb 2013 13:37:24 -0500
Message-ID: <512FA3E4.5060602@mit.edu>
To: Jorge Chamorro <jorge@jorgechamorro.com>
CC: Marcos Caceres <w3c@marcosc.com>, Thaddee Tyl <thaddee.tyl@gmail.com>, François REMY <francois.remy.dev@outlook.com>, Brian Kardell <bkardell@gmail.com>, public-script-coord@w3.org
On 2/28/13 1:31 PM, Jorge Chamorro wrote:
> @Zbarsky: I think that those clickable interactive trees and whatnots are über awesome when in interactive mode, when one's typing at the console, but to get them programatically perhaps one should have to call .dir() [1] not .log(), don't you think so?

<shrug>.  I'm just telling you what current console implementations do 
and what presumably authors expect.

Note that console.dir() always produces the "object tree" output in 
Firefox and Chrome at least, while console.log() seems to be a "dwim" 
feature: what it does depends on what got passed.

> If .log() -as it seems- is the printf() [2]

I believe this perception is incorrect.

> When you do a console.log(obj) in a loop as in that example, to observe obj changing, delaying the serialization obviously won't work


Received on Thursday, 28 February 2013 18:37:56 UTC

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