16453 2012-03-20 17:31:40 +0000 Rename "node document" 2012-03-20 20:14:36 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified PC All RESOLVED WONTFIX P2 enhancement --- 1 zcorpan annevk bzbarsky mike Ms2ger www-dom public-webapps-bugzilla oldest_to_newest 65853 0 zcorpan 2012-03-20 17:31:40 +0000 I think the name "node document" is confusing. It would be easier to read various specs that use it if it was instead called "owner document". 65857 1 bzbarsky 2012-03-20 18:09:47 +0000 I think the problem is that node.ownerDocument is null when node is a Document, but the uses that call it "node document" want node itself when node is a Document, right? Maybe we should just add a realOwnerDocument property that does the sane thing for a Document of returning that same Document? ;) 65859 2 zcorpan 2012-03-20 18:25:01 +0000 (In reply to comment #1) > I think the problem is that node.ownerDocument is null when node is a Document, > but the uses that call it "node document" want node itself when node is a > Document, right? I don't see why that's a problem (and it's not the reason it's currently called "node document"). > Maybe we should just add a realOwnerDocument property that does the sane thing > for a Document of returning that same Document? ;) Not without a use case. :-) 65861 3 bzbarsky 2012-03-20 18:28:04 +0000 > I don't see why that's a problem Because having "owner document" mean something different from .ownerDocument seems really confusing to me... 65874 4 Ms2ger 2012-03-20 20:07:12 +0000 What bz said 65875 5 annevk 2012-03-20 20:14:36 +0000 Oh yeah, I forgot about that. Consider that reason #2 Simon. :-) The other was consistency with "XMLHttpRequest document".