[Webkit-unassigned] [Bug 19932] console functions shouldn't print undefined in the console

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=19932





------- Comment #8 from timothy at hatcher.name  2008-07-08 11:38 PDT -------
(In reply to comment #7)
> (In reply to comment #6)
> > I think never printing undefined is fine. IMHO, seeing undefined does not tell
> > you anything.
> It tells you "ok, the code was executed". Maybe it's not the best feedback but
> it's better than nothing i think

What tells me code executes is I get a blinking caret on a new line and no
errors are logged. I don't think we need to log anything unless there is a
non-undefined result or there is an error.

> > Also I think this will be a bigger issues once bug 19931, not less. Since you
> > will see seemingly random undefined values showing up in the middle of the
> > output. But you would also see other return values separated from the original
> > call, which makes it seem like the proposed fix for bug 19931 should not land.
> I can't see how bug 19931 can change the output. It just prints input before
> everything. The order between output produced and return value shouldn't
> change. And I can't understand why it would be random.

It isn't random, but looking at the log it is not clear where the undefined
came from (same with any function result if bug 19931 is fixed as proposed.)

Look at the screenshot in bug 19931, and you see:

> console.log("hi")
"hi"
undefined

That undefined could be a console.log(undefined). The result is not clearly
marked.


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.