- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Feb 2020 11:44:37 +0000
- To: public-device-apis-log@w3.org
>@hadriann: If I understand correctly, that would mean to tailor a specification based on an implementation - while usually things are the other way around. The W3C process requires "adequate implementation experience" to enter [Proposed Rec](https://www.w3.org/2019/Process-20190301/#rec-pr) stage. "Adequate" means two or more interoperable implementations in practice. If implementers choose to implement only a subset of the spec, then that in practice defines the scope that has "adequate implementation experience". The spec has technically been at Candidate Rec (revised CR is due) for over 2 years so this requirement kicks in at next advancement and will block us progressing further unless addressed (possible solutions discussed below). Some say this approach means the spec reflects reality. I'm sympathetic to the alternative viewpoint, but the following data supports the proposal to advance the screen wake lock feature on its own: Screen wake lock: - strong use cases - one implementation shipping experimentally w/ positive web developer feedback - another implementer possibly interested System wake lock: - no strong use cases - no implementation(s) >@reillyeon @marcoscaceres re Levels: I'd like us to choose a path that makes the editing task the least painful for the editors and makes it easiest to gain more implementation experience, in practice addresses Mozilla's concerns in the most fitting way possible. "Spin up a separate doc for the new wake locks" sounds like the path of least resistance to me. We can integrate the system wake lock spin-off back if more interest emerges. The spin off could live in the same repo to keep things simple. Alternative approach is to keep both the "screen" and "system" wakelocks in the same spec as currently but annotate "system" wake lock as at risk feature so that it can be dropped without penalty when transitioning from (republished) CR to PR. -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/253#issuecomment-591385167 using your GitHub account
Received on Wednesday, 26 February 2020 11:44:39 UTC