whatwg/websockets issues and pull requests

#62 - Create a `fetch`-based WebSocket wrapper

Issue - State: closed - Opened by dead-claudia 4 months ago - 3 comments
Labels: addition/proposal, needs implementer interest

#61 - Close status is not optional?

Issue - State: open - Opened by rotu 5 months ago - 4 comments

#60 - Suggestion to Add Translated Link for websockets (Simplified Chinese 简体中文)

Issue - State: open - Opened by JinDX 5 months ago

#59 - add protocols option to WebSocket constructor

Pull Request - State: open - Opened by KhafraDev 9 months ago

#57 - AbortController but for Websockets

Issue - State: closed - Opened by amills-vibeirl 12 months ago - 7 comments

#56 - Meta: update repository files

Pull Request - State: closed - Opened by annevk about 1 year ago

#55 - Allow programmatic configuration of maximum frame size?

Issue - State: open - Opened by mccolljr about 1 year ago - 3 comments
Labels: addition/proposal, needs implementer interest

#54 - serverCertificateHashes

Issue - State: open - Opened by martenrichter about 1 year ago - 4 comments
Labels: addition/proposal, needs implementer interest

#53 - Meta: update repository files

Pull Request - State: closed - Opened by annevk over 1 year ago - 1 comment

#52 - Meta: update repository files

Pull Request - State: closed - Opened by annevk over 1 year ago

#51 - Review Draft Publication: September 2023

Pull Request - State: closed - Opened by annevk over 1 year ago

#50 - Incorrect Mixed Content tests

Issue - State: open - Opened by annevk over 1 year ago - 1 comment

#49 - Add readable and writable stream properties to Web Socket API

Issue - State: open - Opened by AMorgaut over 8 years ago - 4 comments
Labels: addition/proposal

#48 - The WebSocketStream Interface

Pull Request - State: open - Opened by ricea over 1 year ago - 10 comments
Labels: needs implementer interest, topic: websockets

#47 - Are subprotocols case-insensitive?

Issue - State: open - Opened by ricea over 1 year ago

#46 - Use current settings object instead of relevant settings object

Issue - State: closed - Opened by zcorpan over 1 year ago - 4 comments
Labels: clarification

#45 - Allow HTTP(S) schemes in the WebSocket constructor

Pull Request - State: closed - Opened by annevk over 1 year ago - 1 comment

#42 - Allow dictionary as second param in WebSocket constructor

Issue - State: open - Opened by KhafraDev almost 2 years ago - 4 comments

#40 - Cookie processing

Issue - State: open - Opened by annevk over 2 years ago

#39 - Investigate 401 handling for WebSocket

Issue - State: open - Opened by annevk over 6 years ago - 5 comments
Labels: topic: websockets

#38 - Refactoring WebSocket connections

Issue - State: open - Opened by annevk over 2 years ago

#37 - Allow relative URLs and http(s) scheme

Pull Request - State: closed - Opened by devsnek over 2 years ago - 3 comments

#36 - Meta: export obtain a WebSocket connection

Pull Request - State: closed - Opened by annevk over 2 years ago - 1 comment

#35 - Meta: update repository files

Pull Request - State: closed - Opened by annevk over 2 years ago

#34 - Review Draft Publication: September 2022

Pull Request - State: closed - Opened by annevk over 2 years ago

#33 - Queueing/Throttling

Issue - State: closed - Opened by prettydiff over 2 years ago - 3 comments

#32 - Fix small editorial issue

Pull Request - State: closed - Opened by Reububble over 2 years ago - 11 comments
Labels: editorial

#31 - Editorial: fix The WebSocket Protocol references

Pull Request - State: closed - Opened by annevk over 2 years ago

#30 - Interoperability for servers that send HTTP/1.0 101 BLAH

Issue - State: open - Opened by annevk over 2 years ago - 3 comments
Labels: interop

#29 - Editorial: Remove stray "]"

Pull Request - State: closed - Opened by ricea almost 3 years ago

#28 - Unmatched bracket "If ready state ]is not OPEN"

Issue - State: closed - Opened by pxeger almost 3 years ago

#28 - Unmatched bracket "If ready state ]is not OPEN"

Issue - State: closed - Opened by pxeger almost 3 years ago

#27 - WebSocket new features

Issue - State: open - Opened by MuratovBektur almost 3 years ago - 5 comments

#26 - Review Draft Publication: March 2022

Pull Request - State: closed - Opened by annevk almost 3 years ago

#24 - Is there a reason the only 1xxx close code allowed is 1000?

Issue - State: open - Opened by dead-claudia almost 3 years ago - 2 comments

#23 - Test what browsers do when a server replies multiple Sec-WebSocket-Protocol headers

Issue - State: open - Opened by nox almost 8 years ago
Labels: topic: websockets

#22 - What should happen when the WebSocket constructor is called for a global whose document is not current?

Issue - State: open - Opened by bzbarsky about 8 years ago - 2 comments
Labels: topic: multiple globals

#21 - Connection status code

Issue - State: closed - Opened by shaharmor almost 8 years ago - 6 comments
Labels: addition/proposal, needs implementer interest

#20 - WebSocket and relative URLs

Issue - State: closed - Opened by devsnek over 3 years ago - 15 comments
Labels: addition/proposal, needs implementer interest

#19 - Give hints about HTTP/2 and HTTP/3 support when opening a WebSocket

Issue - State: open - Opened by ddragana over 3 years ago - 3 comments
Labels: addition/proposal, needs implementer interest

#18 - Configure credentials of cookies for WebSocket

Issue - State: open - Opened by regseb almost 5 years ago - 5 comments
Labels: addition/proposal, needs implementer interest

#17 - WebSocket - enable backpressure support by supporting Streams integration

Issue - State: open - Opened by travisleithead about 6 years ago - 4 comments
Labels: addition/proposal, needs implementer interest

#16 - Support for custom headers for handshake

Issue - State: open - Opened by Misiu over 7 years ago - 108 comments
Labels: addition/proposal, needs implementer interest

#16 - Support for custom headers for handshake

Issue - State: open - Opened by Misiu over 7 years ago - 108 comments
Labels: addition/proposal, needs implementer interest

#15 - WebSocket options object

Issue - State: closed - Opened by timreichen over 3 years ago - 1 comment
Labels: addition/proposal, needs implementer interest

#14 - Meta: define events instead of relying on HTML's definitions

Pull Request - State: closed - Opened by domenic almost 3 years ago

#13 - Unclear wording for "in parallel" while running WebSocket constructor

Issue - State: closed - Opened by mikkorantalainen about 3 years ago - 5 comments

#12 - Meta: update repository files

Pull Request - State: closed - Opened by annevk about 3 years ago

#11 - Link Japanese translation

Pull Request - State: closed - Opened by domenic about 3 years ago

#10 - Expose ping/pong mechanism for user integration

Issue - State: open - Opened by dead-claudia about 3 years ago - 1 comment
Labels: addition/proposal, needs implementer interest

#9 - Export terms used in whatwg/fetch

Pull Request - State: closed - Opened by yutakahirano about 3 years ago - 1 comment

#8 - Editorial: Update the protocol alterations note to reflect the spec move

Pull Request - State: closed - Opened by andreubotella about 3 years ago - 1 comment

#7 - Meta: add Acknowledgments section

Pull Request - State: closed - Opened by domenic about 3 years ago

#6 - Meta: correct typo in README

Pull Request - State: closed - Opened by annevk about 3 years ago

#5 - Editorial: slightly modernize API definitions

Pull Request - State: closed - Opened by domenic about 3 years ago - 3 comments

#4 - Update the constructor

Pull Request - State: closed - Opened by yutakahirano about 3 years ago

#3 - Fix small editorial issues

Pull Request - State: closed - Opened by yutakahirano about 3 years ago

#2 - Fetch updates

Pull Request - State: closed - Opened by ricea about 3 years ago

#1 - Use Bikeshed markdown instead of HTML-style markup

Pull Request - State: closed - Opened by ricea almost 4 years ago - 3 comments

GitHub / whatwg/websockets issues and pull requests