Thanks. I'll try to finish up my poc for now, using the vibrations api.
I'll take any future questions to the public-device-apis list.
Mkkl.
On Mon, Aug 12, 2013 at 9:53 PM, Ted Mielczarek t...@mozilla.com wrote:
On 8/5/2013 1:11 PM, Tab Atkins Jr. wrote:
On Thu, Aug 1, 2013 at 2:31 AM,
I concur. On hold doesn't mean forever, and the imperative API affords us
nearly identical feature capability. Nailing the imperative and getting the
APIs to market is far more important to developers at this point.
On Aug 12, 2013 4:46 PM, Alex Russell slightly...@google.com wrote:
As discussed
On Tue, Aug 13, 2013 at 9:15 AM, Daniel Buchner dan...@mozilla.com wrote:
I concur. On hold doesn't mean forever, and the imperative API affords us
nearly identical feature capability. Nailing the imperative and getting the
APIs to market is far more important to developers at this point.
On
Quick question: Will we still be able to land HTML Imports sans any Custom
Element reliance/support? I'd like to retain the ability to import HTML
files unbound from the parsing of element declarations. A significant
use-case is easily importing a bunch of template elements for use in the
main
Yep. HTML Imports are standing on their own.
Dimitri, did I ever tell you you're my hero? (#ProTip: to get the full
effect, sing it with that Bette Midler tone)
On Tue, Aug 13, 2013 at 10:02 AM, Dimitri Glazkov dglaz...@google.comwrote:
On Tue, Aug 13, 2013 at 9:59 AM, Daniel Buchner
Hi all,
It's been a while since Quota API's FPWD (http://www.w3.org/TR/quota-api/)
was published and we've gotten several requests/feedbacks so far.
To address some of the requests and to gain more consensus, I'm thinking
about making following changes to the Quota API:
* Use Promises rather
