W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2011

[Bug 13034] Consider [TreatNullAs=EmptyString] for some reflected attributes

From: <bugzilla@jessica.w3.org>
Date: Thu, 29 Sep 2011 20:56:08 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1R9NeK-0002uh-5o@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13034

Travis Leithead [MSFT] <travil@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |travil@microsoft.com

--- Comment #6 from Travis Leithead [MSFT] <travil@microsoft.com> 2011-09-29 20:56:07 UTC ---
I've been meaning to do an exhaustive test of our DOM in order to document any
exceptions we may have to the default null->"null" and undefined->"undefined"
conversions... so thanks Aryeh!

These conversions (and APIs!) are carryovers from our classic behavior--I don't
have any data on what the web compatibility story might be like for these.
Considering that old versions of IE are probably the biggest consumer of these
APIs from a compatibility standpoint, I think the safest approach for web
compat is to simply call out each of these in HTML5 with the
[TreatNullAs=EmptyString] annotation. As was said before, its a pretty short
list.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 29 September 2011 20:56:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:04 UTC