15520 2007-10-15 11:21:04 -0700 alert(undefined) should say "undefined" in the alert 2007-10-17 10:14:59 -0700 1 1 1 Unclassified WebKit WebCore JavaScript 523.x (Safari 3) Mac OS X 10.4 RESOLVED FIXED P3 Trivial --- 1 darin darin mitz sam oldest_to_newest 58590 0 darin 2007-10-15 11:21:04 -0700 I tested other browsers, and alert(undefined) should not say "", it should say "undefined". 58703 1 mitz 2007-10-16 23:50:12 -0700 This was fixed in <http://trac.webkit.org/projects/webkit/changeset/26616>. That patch also changed the behavior of "alert()" and "prompt('string')", as evident by the changes to test results. I think that change was wrong; in Firefox, prompt('foo') doesn't use "undefined" as the default value (and alert() throws a not enough arguments exception). 58728 2 darin 2007-10-17 07:51:12 -0700 (In reply to comment #1) > This was fixed in <http://trac.webkit.org/projects/webkit/changeset/26616>. > > That patch also changed the behavior of "alert()" and "prompt('string')", as > evident by the changes to test results. I think that change was wrong; in > Firefox, prompt('foo') doesn't use "undefined" as the default value (and > alert() throws a not enough arguments exception). In the case of alert(), I think we're OK. IE shows an alert with the empty string and Firefox throws an exception. I think it's fine that we display the string "undefined". But prompt("string") I think is something else altogether! We don't want "undefined" as the default value in that case! 58731 3 mitz 2007-10-17 10:14:59 -0700 Bug 15541 filed on the prompt() issue.