Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Spec for PresentationConnectionCloseEvent closeMessage conflicts with note #344

Closed
mfoltzgoogle opened this issue Sep 16, 2016 · 1 comment
Closed

Spec for PresentationConnectionCloseEvent closeMessage conflicts with note #344

mfoltzgoogle opened this issue Sep 16, 2016 · 1 comment
Labels
P2 v1

Comments

@mfoltzgoogle
Copy link
Contributor

The spec for this event states that,

When the reason attribute is error, the user agent should set the error message to a human readable description of how the communication channel encountered an error.

But the note in 6.5.2 describes how the user agent should set the message to the beginning of the first failed message. Perhaps we can tweak the note to include both.
@anssiko anssiko added the v1 label Sep 22, 2016
@tidoust
Copy link
Member

tidoust commented Sep 26, 2016

See discussion at TPAC

ACTION: @mfoltzgoogle to update close message examples to conform to spec

@mfoltzgoogle mfoltzgoogle mentioned this issue Sep 27, 2016
Merged
mfoltzgoogle added a commit that referenced this issue Oct 10, 2016
@mfoltzgoogle
Merge pull request #349 from w3c/issue-344-close-note
05e0cf9 
Implements proposed resolution for Issue #344.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
P2 v1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@anssiko @tidoust @mfoltzgoogle