5859 2008-07-12 02:37:20 +0000 Spec doesn't handle unknown schemes 2010-10-04 14:45:45 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All VERIFIED FIXED NoReply P2 normal --- 1 ian ian aaz mike preston public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 21158 0 ian 2008-07-12 02:37:20 +0000 Many parts of the spec (e.g. anywhere that talks about "default port") assume that all schemes are known. We should make sure that anywhere that handles URLs knows how to handle unknown schemes. 21163 1 preston 2008-07-12 23:02:30 +0000 Should the HTML spec define what is a valid URL/URI/IRI (whatever)? It seems appropriate to reference the relevant RFCs, but outside the scope of the HTML spec to repeat the contents of those RFCs. 21164 2 ian 2008-07-12 23:03:56 +0000 It already defines it, by deferring to those RFCs. 21423 3 ian 2008-08-01 01:04:39 +0000 turned out to be a non-issue 32981 4 mjs 2010-03-14 13:15:12 +0000 This bug predates the HTML Working Group Decision Policy. If you are satisfied with the resolution of this bug, 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 This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.