- From: Raphael Kubo da Costa via GitHub <sysbot+gh@w3.org>
- Date: Fri, 18 Oct 2019 09:46:56 +0000
- To: public-web-nfc@w3.org
For more context: my commit fixed w3c/wake-lock#238 after following https://w3ctag.github.io/design-principles/#state-and-subclassing, as our `WakeLockEvent` had a single `lock` member that also happened to be identical to `Event.target` anyway. I'm not very familiar with the NFC spec though, I guess if you were to drop `NFCErrorEvent` you'd still need to find a way to put that `error` attribute somewhere. -- GitHub Notification of comment by rakuco Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/391#issuecomment-543638597 using your GitHub account
Received on Friday, 18 October 2019 09:46:59 UTC