23810 2013-11-12 21:27:24 +0000 When adopting, "If node is an element, it is affected by a base..." 2014-02-10 11:02:50 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified PC All RESOLVED FIXED P2 normal --- 20567 24312 1 ian annevk ian mike www-dom public-webapps-bugzilla oldest_to_newest 96200 0 ian 2013-11-12 21:27:24 +0000 http://dom.spec.whatwg.org/#interface-document When adopting, step 3 says "If node is an element, it is affected by a base URL change". But what if it's a DocumentFragment, and it contains Elements? What if it's an Element with children Elements? Are the descendants also so affected? 96508 1 annevk 2013-11-19 12:07:36 +0000 Yeah, this needs cleaning up. 100014 2 annevk 2014-02-07 13:16:24 +0000 How about: 1. Let /nodes/ be /node/'s inclusive descendants, in tree order. 2. For each /potentialElement/ in /nodes/, if /potentialElement/ is an element, run its base URL change steps. I guess I'll change that and fix bug 20976 later as that will revamp the entire way base URLs are done. 100015 3 annevk 2014-02-07 13:46:53 +0000 https://github.com/whatwg/dom/commit/8b87826a4a153f386152b44c691b9413eed93ed5 Assigning to you Hixie since there's no need anymore for "affected by a base URL change" in DOM. 100027 4 ian 2014-02-07 17:46:44 +0000 Per our discussion, we're going to have DOM forget about base URL change steps, and instead just notify HTML whenever a node is adopted. 100125 5 annevk 2014-02-10 11:02:50 +0000 https://github.com/whatwg/dom/commit/e50fd7138f1bf288c4fa0b92f1673359a3affadb Note that a) you have to cover children yourself and b) timing of when this extension hook runs might change to be a little later to allow for custom elements to work the same way.