I believe the WebKit project's position, historically, on this topic is that embedders should supply their own implementation of this API rather than having the implementation in WebKit proper. The "external" interface is used in a number of user agents to supply "external" interfaces that are more about interacting with the user agent than about interacting with the rendering engine.
It's certainly possible that we should change our approach here. I don't have strong feelings about it, but others might. Adam On Thu, Oct 25, 2012 at 2:07 PM, Otto Cheung <[email protected]> wrote: > Hello webkit-dev, > > I'm a software developer working for the RIM browser team. > > The team would like to add support for the "external" interface. The > interface is defined in > http://developers.whatwg.org/timers.html#the-external-interface > > We will be submitting a final patch for review soon. Please feel free to > voice your comments or concerns in: > https://bugs.webkit.org/show_bug.cgi?id=90501 > > Thanks, > Otto Cheung > > --------------------------------------------------------------------- > This transmission (including any attachments) may contain confidential > information, privileged material (including material protected by the > solicitor-client or other applicable privileges), or constitute non-public > information. Any use of this information by anyone other than the intended > recipient is prohibited. If you have received this transmission in error, > please immediately reply to the sender and delete this information from your > system. Use, dissemination, distribution, or reproduction of this > transmission by unintended recipients is not authorized and may be unlawful. > _______________________________________________ > webkit-dev mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo/webkit-dev _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo/webkit-dev
