This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The definition of close with prejudice is not straightforward. Sometimes it takes minutes to interpret it. I suggest that we replace > If the user agent was required to fail the WebSocket connection or the WebSocket connection is closed with prejudice, fire a simple event named error at the WebSocket object. [WSP] into > If the user agent was required to fail the WebSocket connection or the closed with prejudice flag is true, fire a simple event named error at the WebSocket object. [WSP] and insert this text > When it is said to close the WebSocket connection with prejudice, run these steps: > - Set the closed with prejudice flag. > - close the WebSocket connection and put occurrences of "close the WebSocket connection with prejudice" in the send() definition into an anchor pointing the new text.
I don't really understand how that would change. "with prejudice" is already hyperlinked to the relevant part of the spec. The term is only used four times. It basically already is a flag (actually, an argument). Can you elaborate on what is confusing?
Yes, after clicking the link and thinking a bit, I can understand that. But at least for me and another (English native), the link looked weird ("hmm, this text is also referring to the WebSocket connection is closed with prejudice. where's the actual definition...?") and tried to find explicit definition of close the WebSocket connection with prejudice that could be placed somewhere else. Just adding "flag" to "prejudice" is also fine. When I was reading a text in DOM Promises spec that is using "synchronous flag", I didn't find it confusing.
Yeah, maybe I'm just being too cute here, and it's hurting the readability. I can look into changing the term to something else.
Checked in as WHATWG revision r8298. Check-in comment: Reword the concept of closing a WebSocket with prejudice so that it's more obviously a flag http://html5.org/tools/web-apps-tracker?from=8297&to=8298