- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Oct 2020 09:08:56 +0000
- To: public-secondscreen@w3.org
A couple of comments: 1. Doesn't the note actually contradict the note that's right before it and that says: "The connection *must provide a two-way messaging abstraction* [...]"? 2. In particular, many apps will expect a communication channel to be available. This note suggests that user agents may not provide one. Isn't that going to break the user experience? In other words, I believe that the controlling user agent should never offer to connect to a receiving user agent that wouldn't be able to provide a communication channel, unless the application is explicit that the communication channel is optional (or unless we're talking about a URI scheme different from `http` and `https`, but then that's out of scope of the spec). That is the reason why I was proposing some sort of option to the `PresentationRequest` constructor. In any case, if there are no implementation plans for such a feature, it should probably just be dropped. -- GitHub Notification of comment by tidoust Please view or discuss this issue at https://github.com/w3c/presentation-api/pull/484#issuecomment-709021683 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 15 October 2020 09:08:58 UTC