http://www.w3.org/Bugs/Public/show_bug.cgi?id=13990
Summary: Need a spec for CloseEvent constructor
Product: WebAppsWG
Version: unspecified
Platform: PC
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13996
Summary: Don't wrap invisible nodes when doing inline styling
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
On 2011-08-11 06:36, Brian Raymor wrote:
What is the rationale for also failing the websocket connection when a response
for authentication is received such as:
401 Unauthorized
407 Proxy Authentication Required
...
Note that the web socket setup request can still use http auth; it just
On Thu, Sep 1, 2011 at 4:53 AM, Rich Tibbett ri...@opera.com wrote:
Adam Barth wrote:
Generally speaking, browsers have been moving away from triggering
authentication dialogs for subresource loads because they are more
often used for phishing than for legitimate purposes. A WebSocket
This is a Last Call Working Draft transition announcement for the
following 3 documents:
Performance Timeline
http://www.w3.org/TR/2011/WD-performance-timeline-20110901/
User Timing:
http://www.w3.org/TR/2011/WD-user-timing-20110901/
Resource Timing:
http://www.w3.org/TR/2011/WD-resource
:
This is a Last Call Working Draft transition announcement for the
following 3 documents:
Performance Timeline
http://www.w3.org/TR/2011/WD-performance-timeline-20110901/
User Timing:
http://www.w3.org/TR/2011/WD-user-timing-20110901/
Resource Timing:
http://www.w3.org/TR/2011/WD-resource-timing
Hi All,
We've been working on finishing up our implementation of the WebSocket
API for firefox and have mostly one outstanding issue.
The problem is the .binaryType property. There are two problems that I
see with how it's currently defined.
1. It doesn't allow receiving textual messages as
