New issue on

GitHub project “dap-charter”

DASWG: Leave System WakeLock API in WICG until there is a second implementer

on (ttk.me b/57V4) using BBEdit

Per DAS charter feedback: We believe it would be prudent for the System WakeLock API to go through the WICG process until it gets implementation commitment from at least a second browser vendor.

Having said that, we would be comfortable with having WICG incubated specs being explicitly listed as charter as work items the working group could adopt at a future date. However, we'd like to see them listed in a manner similar to the Web Apps WG Charter's section on WICG Specs (i.e., separated out of the main deliverables list for the working group).

cc: @dwsinger @pes10k @marcoscaceres