- From: Alex Milowski <alex@milowski.com>
- Date: Thu, 14 Mar 2013 08:50:59 -0700
- To: public-webapps@w3.org
- Message-ID: <CABp3FN++aChHcD1ji5xDbEJHVo5MkNW6_PWTuYzQ_KM9zmMQgg@mail.gmail.com>
In looking at [1], I don't see whether the baseURI property should contain the fragment identifier. I have noticed that WebKit based browsers remove the fragment identifier and Firefox does not. Specifically, when a document uses the 'base' element with a URI that contains a fragment identifier, Firefox and WebKit will differ. Who is correct? This (DOM Core) specification defers to other specifications which are not referenced by [1]. 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. [1] http://www.w3.org/TR/domcore/#concept-node-base-url [2] http://tools.ietf.org/html/rfc3986#section-5.2 -- --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
Received on Thursday, 14 March 2013 15:51:31 UTC