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: Raphael Kubo da Costa via GitHub <sysbot+gh@w3.org>
Date: Tue, 21 May 2019 11:49:21 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-494357684-1558439359-sysbot+gh@w3.org>
To anyone looking at this in the future:
* AbortController is pretty new, which is why it's not very widespread at this point.
* See #199 and #195 for discussions about what happens when we have actual `WakeLock` objects around.
* See #171, #178, #183 and #194 for previous discussions on `AbortSignal` vs an `abort()` method (also related to the lifecycle discussion above).

GitHub Notification of comment by rakuco
Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/214#issuecomment-494357684 using your GitHub account
Received on Tuesday, 21 May 2019 11:49:22 UTC

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