- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Fri, 12 Jan 2018 14:57:25 +0000
- To: public-secondscreen@w3.org
That's a good point. The specification is clear that behavior for schemes over than `http` and `https` is not defined, but in that case, we probably want to clarify that implementations must ignore the URLs that they do not understand, so that an `https` URL can be used as a fallback to a URL that the user-agent does not understand. One way to solve this would be to complete current step 5.1 to say something like: "and add the resulting absolute URL (if any, **and if the resulting scheme is supported**) to `presentationUrls`" ... and introduce a new step 6. that says: "If `presentationUrls` is an empty list, then throw a `NotSupportedError` and abort all remaining steps" -- GitHub Notification of comment by tidoust Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/446#issuecomment-357259779 using your GitHub account
Received on Friday, 12 January 2018 14:57:29 UTC