- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Mar 2017 20:29:05 +0000
- To: public-media-capture-logs@w3.org
If I remember rightly: The reason all constrainable types are DOMString not enum is that enums behave badly when extended - new values will throw exceptions (or rejected promises) on old browsers, which means that it's quite hard for an app to add values without extensive probing to figure out which values are acceptable. The WG decided that it would prefer to have DOMString so that any value can be passed, but the UA can deal with them appropriately (ignore ideal constraints it doesn't understand the value of, and return "impossible to satisfy" when those are encountered as "exact" values). Yep, consistency is nice. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/mediacapture-image/pull/150#issuecomment-285472913 using your GitHub account
Received on Thursday, 9 March 2017 20:29:11 UTC