W3C home > Mailing lists > Public > public-device-apis-log@w3.org > May 2019

Re: [wake-lock] New API with AbortController is not intuitive for developers. (#214)

From: Kenneth Rohde Christiansen via GitHub <sysbot+gh@w3.org>
Date: Tue, 21 May 2019 11:34:54 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-494353574-1558438493-sysbot+gh@w3.org>

Talked to Mrunal in real life and explained why we will be going with AbortController etc

-- 
GitHub Notification of comment by kenchris
Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/214#issuecomment-494353574 using your GitHub account

Received on Tuesday, 21 May 2019 11:34:55 UTC

This message: [ Message body ]
Next message: Kenneth Rohde Christiansen via GitHub: "Closed: [wake-lock] New API with AbortController is not intuitive for developers. (#214)"
Previous message: Mrunal Kapade via GitHub: "[wake-lock] New API with AbortController is not intuitive for developers. (#214)"
In reply to: Mrunal Kapade via GitHub: "[wake-lock] New API with AbortController is not intuitive for developers. (#214)"
Next in thread: Kenneth Rohde Christiansen via GitHub: "Closed: [wake-lock] New API with AbortController is not intuitive for developers. (#214)"

Mail actions: [ respond to this message ] [ mail a new topic ]
Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]
Help: [ How to use the archives ] [ Search in the archives ]

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:56 UTC