- From: <bugzilla@jessica.w3.org>
- Date: Sat, 18 Jun 2011 19:17:59 +0000
- To: public-script-coord@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12798 --- Comment #20 from Travis Leithead [MSFT] <travil@microsoft.com> 2011-06-18 19:17:59 UTC --- >> "I *think* and there is quite some content out there that relies on this too" >> "I *believe* WebKit has had similar experience." Anne, can you provide some examples that motivated the change in Opera? As I sighted before, the IE behavior defatul is null->"null", so I'm wondering what sites are broken in IE due to this behavior (and not some other side-effect)? In addition to the compatibility argument, there's also the argument around consistency _with ECMAScript_ default behavior. We should be very careful about changing to a default that is inconsistent with ECMAScript null converstions in [[ToString]]. Now, if ECMAScript is willing to change their defaults, then I think we may have something to discuss. >> Now if Gecko is changed and they can ship with that change null -> "null" might be the right thing to do, but otherwise the more sensible default is null -> "". Both for existing methods and attribute setters and for future ones, so we have at least some consistency. Indeed I am arguing for consistency, but consistency between the DOM and ECMAScript. This is one of my goals for the WebIDL binding. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Saturday, 18 June 2011 19:18:01 UTC