9043 2010-02-17 10:41:11 +0000 Must the href attribute of <base> be a full URL, including http://...; if so, what is the correct terminology for that? I tried following the "valid URL" link and it goes down a rabbit hole to http://www.w3.org/html/wg/href/draft, which does not define "v 2011-05-10 01:02:18 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WORKSFORME http://www.whatwg.org/specs/web-apps/current-work/#the-base-element urls P3 normal LC 1 contributor ian ian julian.reschke mike public-html-admin public-html-wg-issue-tracking wycats public-html-bugzilla oldest_to_newest 32261 0 contributor 2010-02-17 10:41:11 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#the-base-element Comment: Must the href attribute of <base> be a full URL, including http://...; if so, what is the correct terminology for that? I tried following the "valid URL" link and it goes down a rabbit hole to http://www.w3.org/html/wg/href/draft, which does not define "valid URL" Posted from: 76.126.116.8 by wycats@gmail.com 32663 1 ian 2010-02-25 06:39:10 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Partially Accepted Change Description: no spec change Rationale: To answer your question, the answer is "no" (it can be a relative URL). However, you are right that the references don't yet define this in suitable detail. There's work ongoing on this front to fix this. I'll examine this again once it is done to see if this resolves this issue. 48394 2 ian 2011-05-10 01:02:18 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: no spec change Rationale: This seems to have been fixed now. Let me know if it's still too ambiguous.