On Thu, Jun 13, 2013 at 2:07 AM, Chris Lowis <chris.lowis@bbc.co.uk> wrote: > > Chris Wilson writes: > > Chris is absolutely correct that there are some critical apps out there > today > > that use the API as it is. I would not, for example, like to be the one > who > > breaks the sound in Angry Birds > > I don't want to go to far off-topic, but Angry Birds is specifically > marketed as a Chrome application in their URL > (http://chrome.angrybirds.com/). Couldn't Chrome continue to support the > interfaces that Rovio have coded to if you were worried about breaking > the sound in that game, while still allowing us to make changes to the > spec? > Just to put things in perspective, this isn't specifically about Angry Birds, since that's just one example of all the content out there, large and small. But yes, we can certainly work on making these names non-normative while still maintaining backward compatibility in Chrome. I have never been against different ways of handling this in the spec. I started out mentioning these old APIs as "recommended", meaning they were not normative, and the section was simply there in an appendix to show how the API has changed, an informational section which seems very useful for developers to know about. > > Cheers, > > Chris > > > ----------------------------- > http://www.bbc.co.uk > This e-mail (and any attachments) is confidential and > may contain personal views which are not the views of the BBC unless > specifically stated. > If you have received it in > error, please delete it from your system. > Do not use, copy or disclose the > information in any way nor act in reliance on it and notify the sender > immediately. > Please note that the BBC monitors e-mails > sent or received. > Further communication will signify your consent to > this. > ----------------------------- >
Received on Friday, 14 June 2013 18:38:52 UTC