25021 2014-03-12 19:45:50 +0000 Reintroduction of Attribute ownerElement 2014-04-16 12:40:33 +0000 1 1 1 Unclassified HTML WG DOM4 unspecified Macintosh MacOS X RESOLVED FIXED P2 major --- 1 bedney robin oldest_to_newest 102257 0 bedney 2014-03-12 19:45:50 +0000 In changing Attributes from being Nodes to being just regular objects, this property got dropped. It seems to me that just because an Attribute is no longer a Node that that doesn't alter the fact that it still has an 'owning element'. I do have use cases whereby I am holding an Attribute (Node - for now, object - for the future) where I need to 'refer back' to the owning element. Browsers are starting to implement pieces of L4 and this is now a breaking change. I would propose it's reintroduction as a property of Attribute. 103163 1 robin 2014-03-31 12:49:47 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: Reintroduced ownerElement (from cherry-pick) Rationale: This is implemented, useful, and used. http://w3c.github.io/dom/index.html#dom-attr-ownerelement 103961 2 robin 2014-04-16 12:40:33 +0000 Actually, I am going to have to revert this decision (I just did in fact). I mistakenly thought that the upstream spec had reintroduced ownerElement (as discussed on www-dom) and that this bug was because I'd screwed up syncing with it. But it turns out that it was indeed added, but then removed. We're committed to tracking the upstream specification (http://dom.spec.whatwg.org/) and only differing from it by subsetting or small non-normative blah like the boilerplate. Please track the upstream bug (which is still open) for further discussion: https://www.w3.org/Bugs/Public/show_bug.cgi?id=25086. Note that while it is supported in Gecko and WebKit, it has recently been removed from Blink which ought to indicate that it is not needed. If you have data indicating the contrary, it would be a great idea to share it.