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

Re: [wake-lock] Avoid cases like |options|.|signal| as that creates a new variable signal (#208)

From: Raphael Kubo da Costa via GitHub <sysbot+gh@w3.org>
Date: Tue, 14 May 2019 16:04:48 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-492302386-1557849887-sysbot+gh@w3.org>
The version that landed in #201 did not include the `|foo|.|bar|` notation. The closes we have is `|foo|.{{[[ActiveLocks]]}}`, and I have no idea if that one makes sense.

-- 
GitHub Notification of comment by rakuco
Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/208#issuecomment-492302386 using your GitHub account
Received on Tuesday, 14 May 2019 16:04:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 14 May 2019 16:04:52 UTC