- From: Raphael Kubo da Costa via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Jan 2022 11:18:55 +0000
- To: public-device-apis-log@w3.org
> From a W3C process perspective, we’d land the spec and w-p-t changes as soon as there’s consensus in the WG. Yep, that's what I was thinking. I was asking about this because even though the chance is small, there's still the possibility that there is pushback between Chrome 99 and 102 and we are forced to rethink the deprecation and [SecureContext] change in Blink, in which case the spec would remain out of sync with its only implementation for an indefinite period of time. -- GitHub Notification of comment by rakuco Please view or discuss this issue at https://github.com/w3c/battery/issues/15#issuecomment-1022104294 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 January 2022 11:18:58 UTC