- From: Anssi Kostiainen <anssi.kostiainen@nokia.com>
- Date: Fri, 10 Feb 2012 15:22:04 +0200
- To: ext Robin Berjon <robin@berjon.com>
- Cc: ext Dominique Hazael-Massieux <dom@w3.org>, <public-device-apis@w3.org>
On 9.2.2012, at 15.58, ext Robin Berjon wrote: > On Feb 9, 2012, at 10:58 , Anssi Kostiainen wrote: >> Thanks to Robin this issue fixed itself :) > > Note that it would probably still be better to actually remove the exception's definition from the source ;) Whoops. For some reason I was looking for warnings in console and happily missed these. Fixed now. >> Throwing an exception and the NotSupportedError are defined in DOM4, so I guess the following terse wording should be enough: > > Yes. This will come back to haunt us when we want to exit CR and DOM4 isn't mature enough, but we can cross that bridge when we get there. I reckon we can justify an exemption in this specific case. I hope we are able to work around that. I believe this is not the only spec with such a dependency, e.g. HTML5 depends on DOM4. -Anssi
Received on Friday, 10 February 2012 13:22:41 UTC