18459 2012-08-01 09:41:17 +0000 So, this makes it sound like the document base URL is computed every time that it's needed. But that doesn't seem to be true in Gecko/WebKit - in particular after pushState they don't recompute the document base URL. So the value probably needs to be stor 2013-06-12 19:05:21 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#resolving-urls P3 normal Unsorted 1 contributor ian bzbarsky hackwrench ian james justin.lebar mike contributor oldest_to_newest 71732 0 contributor 2012-08-01 09:41:17 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#resolving-urls Complete: http://www.whatwg.org/c#resolving-urls Comment: So, this makes it sound like the document base URL is computed every time that it's needed. But that doesn't seem to be true in Gecko/WebKit - in particular after pushState they don't recompute the document base URL. So the value probably needs to be stored somewhere and computed only at specified times. Posted from: 2001:4c28:a030:30:2d33:76:f557:82e4 User agent: Opera/9.80 (X11; Linux x86_64; U; Edition Next; en) Presto/2.11.310 Version/12.50 71733 1 james 2012-08-01 10:33:06 +0000 TC, sort of: http://hoppipolla.co.uk/tests/pushState/001.html 72712 2 ian 2012-08-24 18:51:36 +0000 Wow, this makes my head hurt. So, _without_ the base element, the pushState() call _does_ cause the base URL to update. But somehow the <base> element is resolved relative to something different than the document's address. So the question is, what on earth is <base href=""> actually resolved against? 77461 3 ian 2012-10-30 22:19:12 +0000 bz, do you have any input on this one? (Or know who might know more?) 78802 4 bzbarsky 2012-11-26 04:46:46 +0000 Maybe Justin Lebar? 82681 5 ian 2013-02-07 03:49:00 +0000 Justin: any ideas? 83284 6 justin.lebar 2013-02-18 18:25:27 +0000 > So, _without_ the base element, the pushState() call _does_ cause the base URL > to update. Correct: http://jsfiddle.net/c7GVu/ > But somehow the <base> element is resolved relative to something different than > the document's address. It's resolved relative to the document's address at the time the base element is created. http://jsfiddle.net/zZ6Ft/ > So the question is, what on earth is <base href=""> actually resolved against? The document's current URI at the time the node is created. If that node's href is later modified, the href is again resolved against the document's current URI. http://jsfiddle.net/LkvaR/2/ 85798 7 ian 2013-04-09 17:40:45 +0000 So the base URL for <base> elements is a stored value, which is saved: * when the element is created * when the href="" attribute is set or changed And this is used to determine the absolute URL that is then used as the document's base URL. And fixing just that would resolve this bug. Everyone agree? 85803 8 bzbarsky 2013-04-09 17:50:40 +0000 Sounds about right to me. 85805 9 justin.lebar 2013-04-09 17:55:03 +0000 This doesn't quite match what Firefox does. Suppose I add <base href="foo"> and then add <base href="bar">. Comment 7 suggests that the second base's href will be resolved immediately, relative to the first base's href. But in fact the second base's href is not resolved until it becomes the first base! var base = document.createElement('base'); base.href = 'foo'; document.body.appendChild(base); var base2 = document.createElement('base'); base2.href = 'bar'; document.body.appendChild(base2); document.body.removeChild(base); console.log(document.baseURI); // prints 'bar', not 'foo/bar'. http://jsfiddle.net/rZfnY/ 85807 10 justin.lebar 2013-04-09 17:57:04 +0000 The testcase works the same if I replace "foo" and "bar" with "foo/" and "bar/". 88471 11 ian 2013-05-30 21:51:30 +0000 I made a bigger testcase: http://www.hixie.ch/tests/adhoc/dom/level0/history/pushState/003.html Looks like when a <base> becomes the relevant <base> (either by being inserted first, or by the only earlier <base> being removed), and when a <base> that is the relevant <base> gets its href="" changed, its href="" is to be resolved against the document URL, and that becomes the new document base URL. That sound better? 88475 12 justin.lebar 2013-05-30 22:06:45 +0000 > That sound better? Yes! 88493 13 bzbarsky 2013-05-31 02:03:37 +0000 Comment 11 matches what Gecko does, I believe. See SetBaseURIUsingFirstBaseWithHref in http://mxr.mozilla.org/mozilla-central/source/content/html/content/src/HTMLSharedElement.cpp 89192 14 contributor 2013-06-12 19:05:21 +0000 Checked in as WHATWG revision r7962. Check-in comment: Make <base> elements not be affected by changes by to the document's address http://html5.org/tools/web-apps-tracker?from=7961&to=7962