Skip to content

Conversation

@ddorwin
Copy link
Contributor

@ddorwin ddorwin commented Jun 17, 2019

After #685, there is only one failure path at this point, and these steps can be simplified.

This also addresses incorrectly rejecting with null.

After immersive-web#685, there is only one failure path at this point, and these steps can be simplified.

This also addresses incorrectly rejecting with `null`.
1. Follow the steps for the first matching conditions:
<dl class="switch">
<dt> If the [=XR/XR device=] is <code>null</code>
<dd> [=Reject=] |promise| with <code>null</code>.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to lose this distinction between promises rejected as null and notsupported? I don't think it's important.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think it's an important distinction either. I can't imagine that a developer is going to do anything useful with that knowledge besides maybe fingerprinting.

@toji
Copy link
Member

toji commented Jun 17, 2019

LGTM, thanks!

@toji toji merged commit 56a038a into immersive-web:master Jun 17, 2019
@toji toji added this to the June 2019 milestone Jun 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants