This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 14168 - createElement and null
Summary: createElement and null
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: DOM (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-15 14:14 UTC by Simon Pieters
Modified: 2011-09-16 08:27 UTC (History)
2 users (show)

See Also:

Attachments

Description Simon Pieters 2011-09-15 14:14:04 UTC 
http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#document

createElementNS second argument should have [TreatNullAs=EmptyString]
Comment 1 Anne 2011-09-15 17:19:53 UTC 
Why?
Comment 2 Simon Pieters 2011-09-15 17:22:06 UTC 
Because createElement has it, and because opera/webkit/gecko do it
Comment 3 Anne 2011-09-15 17:25:36 UTC 
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.)
Comment 4 Simon Pieters 2011-09-16 06:41:10 UTC 
Yeah, OK, remove [TreatNullAs=EmptyString] from createElement instead.
Comment 5 Anne 2011-09-16 08:27:34 UTC 
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