W3C home > Mailing lists > Public > public-secondscreen@w3.org > May 2016

[remote-playback] connect: NotFoundError and NotSupportedError inconsistencies

From: Mounir Lamouri via GitHub <sysbot+gh@w3.org>
Date: Fri, 20 May 2016 13:56:46 +0000
To: public-secondscreen@w3.org
Message-ID: <issues.opened-155968885-1463752605-sysbot+gh@w3.org>
mounirlamouri has just created a new issue for 
https://github.com/w3c/remote-playback:

== connect: NotFoundError and NotSupportedError inconsistencies ==
Step 1 says that UA should reject with `NotSupportedError` if the UA 
knows the formats are not supported (so it doesn't event try to 
discover).

Step 8 says that the UA should reject with `NotFoundError` if no 
devices were found or all found devices are not compatible.

I wonder if we could do:
- `NotSupportedError` when no compatible devices
- `NotFoundError` when no devices

It would require to reject different errors in substeps 1 and 2 from 
step 8.

Please view or discuss this issue at 
https://github.com/w3c/remote-playback/issues/34 using your GitHub 
account
Received on Friday, 20 May 2016 13:56:48 UTC

This archive was generated by hypermail 2.3.1 : Friday, 20 May 2016 13:56:48 UTC