You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems there is no data channel receive procedure that can be followed, e.g. nothing tells us when a message event is invoked and what validation steps are required (check for open [or closing], ...).
The WPT tests reference this WS spec section (When a WebSocket message has been received [...]) and I would propose to copy that.
The text was updated successfully, but these errors were encountered:
We should discuss whether messages can still be received by the peer who initiates the closing procedure or not (see this discussion beginning at comment 55).
@lgrahl Agree that the closing procedure doesn't provide enough detail. As discussed in Issue 559394, when a peer calls close() (resulting in readyState transitioning to "closing") more messages can't be sent, but data can still be received until readyState becomes "closed".
It seems there is no data channel receive procedure that can be followed, e.g. nothing tells us when a message event is invoked and what validation steps are required (check for open [or closing], ...).
The WPT tests reference this WS spec section (When a WebSocket message has been received [...]) and I would propose to copy that.
The text was updated successfully, but these errors were encountered: