-
Notifications
You must be signed in to change notification settings - Fork 39
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
define the behavior while receiver calls connection.terminate() #222
Comments
Option 2 sounds better from the developer ergonomics point of view i.e. regardless of which side is invoking Also, the web developers might expect this work similarly to |
The current algorithm for terminating a presentation connection currently implements proposal #2 by @schien; see the text starting "When a receiving user agent is to terminate a presentation using connection..." http://w3c.github.io/presentation-api/#terminating-a-presentationconnection However the description could be improved. I think we should split it into two algorithms, one for terminating in the controlling context and one for terminating the receiving context. I'll leave this issue open until the editorial improvements are made. Pull requests are welcome :) |
Per @anssiko the implementation is to behave identically to |
It sounds like we're settled on option 2? To provide further data, I'd like to note the behavior in option 1 could be provided as a polyfill rather easily: Given option 2 implemented natively, a web developer could implement option 1 in JS to alter the behaviour of the
The opposite (option 1 implemented natively, option 2 in JS) would be slightly trickier. Looking this from the use case perspective: are there good use cases that would require throwing an exception if the receiving side calls |
This should be addressed with the merged PR. |
In section 6.2.4, we only define the behavior that receiver app must be terminate while controlling side invokes
connection.terminate()
. But what should happen if receiver side invokesconnection.terminate()
?Two approaches I have in mind:
NotSupportedError
exception because we don't allow receiver app to close controller app.terminated
just like the behavior thatconnection.terminate()
is invoked in controlling side.The text was updated successfully, but these errors were encountered: