Re: [sensors] No way to express an abstract constructor in WebIDL

Reopening this as I'm not sure we have consensus here.

We have to two options here:

1. Make constructing `Sensor` throw. This is inline with how abstract 
classes behave on the platform.
2. Make `Sensor` construct an instance that does nothing with future 
compatibility in mind (see @rwaldron's 
[proposal](https://github.com/w3c/sensors/issues/19#issuecomment-103134780)
 above).

I see the following arguments to help us decide between the two:
- is testing made easier by either of them?
- would developer experience be better either way should we implement 
@rwaldron's suggestion in the future? That is: is it better to have a 
legacy browser throw when using constructing a `Sensor` instance or 
fail silently?
- consistency.

-- 
GitHub Notification of comment by tobie
Please view or discuss this issue at 
https://github.com/w3c/sensors/issues/19#issuecomment-180327069 using 
your GitHub account

Received on Friday, 5 February 2016 12:21:11 UTC