LGTM3
/Daniel
On 2025-02-13 11:40, Philip Jägenstedt wrote:
https://chromestatus.com/metrics/feature/timeline/popularity/2416 on
its own makes the risk look very tolerable, and together with the
outreach to WebXR frameworks it seems like a safe move.
LGTM2 with the reviews requested, as Domi
https://chromestatus.com/metrics/feature/timeline/popularity/2416 on its
own makes the risk look very tolerable, and together with the outreach to
WebXR frameworks it seems like a safe move.
LGTM2 with the reviews requested, as Dominik suggested.
On Thu, Feb 13, 2025 at 5:01 AM Domenic Denicola
Can you request the various review gates in ChromeStatus?
On Thursday, February 13, 2025 at 3:55:58 AM UTC+9 Rick Byers wrote:
> A barely used WebXR-specific method that's been deprecated for 5+ years
> seems very low risk to me. LGTM1 to remove.
>
> Rick
>
> On Wed, Feb 12, 2025 at 1:52 PM Bran
A barely used WebXR-specific method that's been deprecated for 5+ years
seems very low risk to me. LGTM1 to remove.
Rick
On Wed, Feb 12, 2025 at 1:52 PM Brandon Jones wrote:
> Primary eng (and PM) emails
>
> bajo...@chromium.org
>
> Summary
>
> navigator.xr.supportsSession was replaced in the W
Primary eng (and PM) emails
bajo...@chromium.org
Summary
navigator.xr.supportsSession was replaced in the WebXR spec by the
navigator.xr.isSessionSupported method in September of 2019 after receiving
feedback on the API shape from the TAG. It has been marked as deprecated in
Chromium since then,
