- From: <bugzilla@jessica.w3.org>
- Date: Mon, 13 Jun 2011 19:44:20 +0000
- To: public-script-coord@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12798
Travis Leithead [MSFT] <travil@microsoft.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |adrianba@microsoft.com,
| |travil@microsoft.com
Resolution|FIXED |
--- Comment #2 from Travis Leithead [MSFT] <travil@microsoft.com> 2011-06-13 19:44:18 UTC ---
I'm a little concerned about this change; what was the justification for this
change?
In IE9, we now use WebIDL syntax to drive the code-generation for our legacy
DOM APIs. I just checked, and 443+ of our legacy APIs are using null->"null"
conversions, while only 2 needed the [TreatNullAs=EmptyString] annotations.
There are some additional APIs I'd have to test to validate (as the signatures
don't 100% align with those speced in the latest W3C WebIDL-converted
specs)--however it's doubtful that those would change the tide. Given IE's wide
deployment and large compatibility history, I'd guess that null->"null"
conversions are more typically expected by the web.
Additionally, by flipping the default, you are moving away from ECMAScript
default conversions (ToString(x)) which seems backwards and not a direction we
should be going.
--
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 Monday, 13 June 2011 19:44:25 UTC