Re: [screen-wake-lock] explainer: Expand on why WakeLock.request() still requires an argument. (#288)

The way I see it is that defaults would be fine if we had something like `request(type, options)` and `options` was optional. If we were to add more values to `WakeLockType` such as "system" and others, having `navigator.wakeLock.request()` behave like `navigator.wakeLock.request("screen")` feels like something we'd do just to maintain backwards compatibility -- i.e. would there be any other reason to make the default "screen" at that point?

-- 
GitHub Notification of comment by rakuco
Please view or discuss this issue at https://github.com/w3c/screen-wake-lock/pull/288#issuecomment-697468642 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 23 September 2020 14:42:34 UTC