- From: Marcos Cáceres <notifications@github.com>
- Date: Wed, 23 Jun 2021 21:37:13 -0700
- To: w3c/permissions <permissions@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 24 June 2021 04:37:39 UTC
Thanks for clarifying, @reillyeon. I can see the logic in that, particularly as we figure out if we need a permission... however, Chrome might be stuck with it if we decide we don't need a permission, but I guess that's ok. @martinthomson, @annevk, Mozilla indicated that the Screen Wake Lock API is "[worth prototyping](https://mozilla.github.io/standards-positions/#screen-wake-lock)", but I understand that it's not a priority at the moment. Would it be too advantageous to add this to spec? I could add it and mark it "at risk" waiting on further implementer feedback. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/permissions/pull/247#issuecomment-867327845
Received on Thursday, 24 June 2021 04:37:39 UTC