Closed
Bug 267276
Opened 20 years ago
Closed 20 years ago
Firefox doesn't resolve relative URIRefs according to xml:base in XHTML 2.0
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: pierre.thierry, Assigned: bugzilla)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041026 Firefox/0.10.1 (Debian package 0.10.1+1.0PR-4) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041026 Firefox/0.10.1 (Debian package 0.10.1+1.0PR-4) In an XHTML document, a relative URI should be appended the in-scope xml:base to resolve an absolute URIRef, but Firefox doesn't. Reproducible: Always Steps to Reproduce: 1. Go to the given URI 2. Follow an hyperlink Actual Results: Firefox tries a bogus URI based on the document URI. Expected Results: Firefox should resolve URI by appending the href attributes to the given xml:base.
| Reporter | ||
Comment 1•20 years ago
|
||
Changing title, as xml:base only applies to XHTML 2.0 (see <http://www.w3.org/TR/xhtml2/mod-hyperAttributes.html#adef_hyperAttributes_xml:base>)
Summary: Firefox doesn't resolve relative URIRefs according to xml:base → Firefox doesn't resolve relative URIRefs according to xml:base in XHTML 2.0
Comment 2•20 years ago
|
||
Actually, I think you'll find that Firefox (and Seamonkey, since Firefox doesn't have its own XML parser) does support xml:base in XHTML 1.0, assuming it's XML: your URL is being served as text/html, so it's being interpreted as a strange and somewhat invalid form of HTML, not XHTML. Change to application/xhtml+xml, and you'll find that XHTML 2.0 (which is, after all, still a Working Draft) isn't exactly supported beyond XML pretty-printing just yet, change to XHTML 1.0 and you'll find that you've forgotten to add an xml:base attribute anywhere, add that, and you should see that it works.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
| Reporter | ||
Updated•20 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•