[Bug 17772] [URL] The definition of "absolute url" makes https:foo not an absolute url, since its behavior depends on whether the base is https: or not. Is that desired? In particular, using this definition for websockets means that wss: urls with no forward... from bugzilla@jessica.w3.org on 2012-07-27 (public-webapps-bugzilla@w3.org from July 2012)

From: <bugzilla@jessica.w3.org>
Date: Fri, 27 Jul 2012 14:37:47 +0000
To: public-webapps-bugzilla@w3.org
Message-Id: <E1Sulfn-000158-IT@jessica.w3.org>

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17772

--- Comment #4 from Boris Zbarsky <bzbarsky@mit.edu> 2012-07-27 14:37:46 UTC ---
Gecko certainly does, in the form of its set of registered nsIProtocolHandlers,
which are what decide how a URI is parsed.  Unknown schemes get handed over to
a protocol handler that assume a non-hierarchical URI.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Friday, 27 July 2012 14:37:52 UTC