W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

[Bug 10213] 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 slashes afte

From: <bugzilla@jessica.w3.org>
Date: Tue, 20 Jul 2010 21:34:36 +0000
To: public-webapps@w3.org
Message-Id: <E1ObKSS-0006CX-60@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10213


Simon Pieters <simonp@opera.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |public-webapps@w3.org
          Component|HTML5 spec (editor: Ian     |WebSocket API (editor: Ian
                   |Hickson)                    |Hickson)
            Product|HTML WG                     |WebAppsWG
          QAContact|public-html-bugzilla@w3.org |member-webapi-cvs@w3.org




--- Comment #1 from Simon Pieters <simonp@opera.com>  2010-07-20 21:34:35 ---
Changing component so Hixie sees this while working on websockets.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 20 July 2010 21:34:37 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:39 GMT