Briefly looking through, I do not see anything that says differently. Nothing says the fragment identifier should be removed. So, these specifications are silent on this.
Certainly, having the base URI contain a fragment identifier has no effect on the resolved URI as the fragment identifier comes from the reference and not the base URI. On Thu, Mar 14, 2013 at 9:23 AM, Anne van Kesteren <[email protected]> wrote: > On Thu, Mar 14, 2013 at 3:50 PM, Alex Milowski <[email protected]> wrote: > > Meanwhile, the base URI resolution of HTML5 defers to RFC 3986 (section > 5) > > and does not mention removing it. In section 5.2, you'll see that the > > fragment identifier is preserved (as would be expected). Thus, it seems > > that Firefox is right. > > Yes. I recommend reading the latest material on the matter going forward > though: > > http://dom.spec.whatwg.org/ > http://www.whatwg.org/specs/web-apps/current-work/multipage/ > > Cheers, > > > -- > http://annevankesteren.nl/ > -- --Alex Milowski "The excellence of grammar as a guide is proportional to the paucity of the inflexions, i.e. to the degree of analysis effected by the language considered." Bertrand Russell in a footnote of Principles of Mathematics
