On 05/27/2012 12:53 PM, Scott Wilson wrote:
On 27 May 2012, at 17:49, Anant Narayanan wrote:
On 05/27/2012 05:11 AM, Marcos Caceres wrote:
Sure, but doesn't that lead to the original complaint that certain
developers don't want their application to install at all for PR reasons?
In
The protocol spec has defined 1015, but I think we should not pass through
it to the WebSocket API.
http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/0437.html
I think 1006 is the right code for all of WebSocket handshake failure, TLS
failure and TCP connection failure. If the
Travis would like to publish a new Working Draft of the DOM 3 Events
spec and this is a Call for Consensus to do so, using
http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html
as the basis.
Note this is Not a Last Call WD and the comment tracking document for
the last LCWD
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17222
Summary: treat status code 308 consistently with 301, 302, and
307
Product: WebAppsWG
Version: unspecified
Platform: All
URL:
On Mon, May 28, 2012 at 5:20 AM, Scott Wilson
scott.bradley.wil...@gmail.com wrote:
I understand the intention, which is to give web app developers some means
of steering users away if they are using a device they don't think will
work well for them using the app.
On the other hand, this is
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17224
Summary: Possible typo in section 6: Ping and Pong Frames
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: minor
On Wed, May 23, 2012 at 9:32 PM, Anne van Kesteren ann...@annevk.nl wrote:
On Wed, May 23, 2012 at 2:05 PM, Kinuko Yasuda kin...@chromium.org
wrote:
https://dvcs.w3.org/hg/quota/raw-file/tip/Overview.html
I noticed something else. StorageInfo is marked as Supplemental and
