This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13700 - W3C SotD of this document still mentions whatwg.org version of the WebSocket protocol which is out of date.
Summary: W3C SotD of this document still mentions whatwg.org version of the WebSocket ...
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: WebSocket API (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Michael[tm] Smith
QA Contact: public-webapps-bugzilla
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
: 14322 15830 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-08-07 10:14 UTC by contributor
Modified: 2012-02-07 10:46 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2011-08-07 10:14:56 UTC 
Specification: http://dev.w3.org/html5/websockets/
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top

Comment:
W3C SotD of this document still mentions whatwg.org version of the WebSocket
protocol which is out of date.

Posted from: 83.85.115.123
User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.7.0; U; en) Presto/2.9.168 Version/11.50
Comment 1 Ian 'Hixie' Hickson 2011-10-31 22:48:47 UTC 
*** Bug 14322 has been marked as a duplicate of this bug. ***
Comment 2 Julian Reschke 2012-02-01 13:24:23 UTC 
*** Bug 15830 has been marked as a duplicate of this bug. ***
Comment 3 Julian Reschke 2012-02-06 13:57:08 UTC 
This bug has been open for almost six months now.

Pointing to a completely outdated protocol spec is harmful.

Why doesn't get this fixed?
Comment 4 Michael[tm] Smith 2012-02-07 09:51:08 UTC 
(In reply to comment #3)
> This bug has been open for almost six months now.
> 
> Pointing to a completely outdated protocol spec is harmful.
> 
> Why doesn't get this fixed?

You're right and it didn't get fixed because it wasn't assigned to me and I'm the current maintainer of the boilerplate stuff from which that SoTD is generated, so I imagine everybody was just waiting on me to fix it.

Anyway, I just checked in a change:

http://dev.w3.org/cvsweb/html5/boilerplate/header-w3c-websockets.diff?r1=1.2;r2=1.3;f=h

If that's not what you had in mind, please re-open this with a comment about any further refinements needed.
Comment 5 Julian Reschke 2012-02-07 10:32:35 UTC 
Looks good to me.

http://dev.w3.org/html5/websockets/ hasn't changed however, I guess that'll occur with the next regular update?
Comment 6 Michael[tm] Smith 2012-02-07 10:46:02 UTC 
(In reply to comment #5)
> Looks good to me.
> 
> http://dev.w3.org/html5/websockets/ hasn't changed however, I guess that'll
> occur with the next regular update?

Yes, it changes only when Hixie makes a change upstream and pushes a new version to W3C CVS. I can't regenerate it myself from the W3C side alone. But at the rate at which Hixie has been making changes lately, it should get regenerated by tomorrow this time. If not, I will ask Hixie to generate a new version.