14168 2011-09-15 14:14:04 +0000 createElement and null 2011-09-16 08:27:34 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified PC All RESOLVED FIXED P2 normal --- 1 zcorpan annevk mike www-dom public-webapps-bugzilla oldest_to_newest 56851 0 zcorpan 2011-09-15 14:14:04 +0000 http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#document createElementNS second argument should have [TreatNullAs=EmptyString] 56858 1 annevk 2011-09-15 17:19:53 +0000 Why? 56860 2 zcorpan 2011-09-15 17:22:06 +0000 Because createElement has it, and because opera/webkit/gecko do it 56862 3 annevk 2011-09-15 17:25:36 +0000 I thought we wanted to move away from what Gecko/WebKit are doing? The whole point was that they had the wrong default. (The createElement thing might be a bug.) 56880 4 zcorpan 2011-09-16 06:41:10 +0000 Yeah, OK, remove [TreatNullAs=EmptyString] from createElement instead. 56886 5 annevk 2011-09-16 08:27:34 +0000 Thanks! Also changed it for hasFeature(). Have not changed it yet for CharacterData.data. We also treat textContent specially still (though not in IDL). https://bitbucket.org/ms2ger/dom-core/changeset/48c69619f6d5