This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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?
Yeah, this needs cleaning up.
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.
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.
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.
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.