Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

supportsSession() -> isSessionSupported() #25770

Merged
merged 1 commit into from Feb 15, 2020

Conversation

@Manishearth
Copy link
Member

Manishearth commented Feb 15, 2020

r? @jdm

fixes #25596

@highfive
Copy link

highfive commented Feb 15, 2020

Heads up! This PR modifies the following files:

  • @asajeffrey: components/script/dom/webidls/XR.webidl, components/script/dom/xr.rs
  • @KiChjang: components/script/dom/webidls/XR.webidl, components/script/dom/xr.rs
@highfive
Copy link

highfive commented Feb 15, 2020

warning Warning warning

  • These commits modify script code, but no tests are modified. Please consider adding a test!
@jdm
jdm approved these changes Feb 15, 2020
@jdm
Copy link
Member

jdm commented Feb 15, 2020

Needs a mach fmt.

@Manishearth Manishearth force-pushed the Manishearth:sessionsupport branch from b2b91cf to 184a916 Feb 15, 2020
@Manishearth
Copy link
Member Author

Manishearth commented Feb 15, 2020

@bors-servo r=jdm

@bors-servo
Copy link
Contributor

bors-servo commented Feb 15, 2020

📌 Commit 184a916 has been approved by jdm

@bors-servo
Copy link
Contributor

bors-servo commented Feb 15, 2020

Testing commit 184a916 with merge a8999e9...

bors-servo added a commit that referenced this pull request Feb 15, 2020
supportsSession() -> isSessionSupported()

r? @jdm

fixes #25596
@bors-servo
Copy link
Contributor

bors-servo commented Feb 15, 2020

💔 Test failed - status-taskcluster

@Manishearth Manishearth force-pushed the Manishearth:sessionsupport branch from 184a916 to 95b41f6 Feb 15, 2020
@Manishearth Manishearth force-pushed the Manishearth:sessionsupport branch from 95b41f6 to eab70b3 Feb 15, 2020
@Manishearth
Copy link
Member Author

Manishearth commented Feb 15, 2020

@bors-servo r=jdm

@Manishearth Manishearth force-pushed the Manishearth:sessionsupport branch from eab70b3 to 54c8cac Feb 15, 2020
@bors-servo
Copy link
Contributor

bors-servo commented Feb 15, 2020

📌 Commit 54c8cac has been approved by jdm

@bors-servo
Copy link
Contributor

bors-servo commented Feb 15, 2020

Testing commit 54c8cac with merge 222b4d5...

bors-servo added a commit that referenced this pull request Feb 15, 2020
supportsSession() -> isSessionSupported()

r? @jdm

fixes #25596
@bors-servo
Copy link
Contributor

bors-servo commented Feb 15, 2020

💔 Test failed - status-taskcluster

@jdm
Copy link
Member

jdm commented Feb 15, 2020

@bors-servo
Copy link
Contributor

bors-servo commented Feb 15, 2020

Testing commit 54c8cac with merge 3fa2497...

bors-servo added a commit that referenced this pull request Feb 15, 2020
supportsSession() -> isSessionSupported()

r? @jdm

fixes #25596
@bors-servo
Copy link
Contributor

bors-servo commented Feb 15, 2020

💔 Test failed - status-taskcluster

@jdm
Copy link
Member

jdm commented Feb 15, 2020

@bors-servo
Copy link
Contributor

bors-servo commented Feb 15, 2020

Testing commit 54c8cac with merge 3475790...

bors-servo added a commit that referenced this pull request Feb 15, 2020
supportsSession() -> isSessionSupported()

r? @jdm

fixes #25596
@bors-servo
Copy link
Contributor

bors-servo commented Feb 15, 2020

☀️ Test successful - status-taskcluster
Approved by: jdm
Pushing 3475790 to master...

@bors-servo bors-servo merged commit 54c8cac into servo:master Feb 15, 2020
2 checks passed
2 checks passed
Community-TC (pull_request) TaskGroup: success
Details
homu Test successful
Details
bors-servo added a commit that referenced this pull request Feb 15, 2020
Always trigger an input sources change event on session creation

Fixes our behavior to match the spec, and to specifically do it in a way
that makes sense. This is also what Chromium does currently, though I'm
not sure if it does the scheduling the same way.

The spec for this may change, see immersive-web/webxr#961.

This fix, along with #25770 , makes
three.js content work on servo. Instead of this fix we can also wait for
mrdoob/three.js#18638 to land (which isn't
certain until we figure out more about
immersive-web/webxr#961 )

Even if immersive-web/webxr#961 decides to
choose the option that obviates this patch, we should probably keep it
for now since there's already content out in the wild relying on this
behavior.

r? @jdm @asajeffrey
@bors-servo bors-servo mentioned this pull request Feb 15, 2020
4 of 5 tasks complete
bors-servo added a commit that referenced this pull request Feb 15, 2020
Always trigger an input sources change event on session creation

Fixes our behavior to match the spec, and to specifically do it in a way
that makes sense. This is also what Chromium does currently, though I'm
not sure if it does the scheduling the same way.

The spec for this may change, see immersive-web/webxr#961.

This fix, along with #25770 , makes
three.js content work on servo. Instead of this fix we can also wait for
mrdoob/three.js#18638 to land (which isn't
certain until we figure out more about
immersive-web/webxr#961 )

Even if immersive-web/webxr#961 decides to
choose the option that obviates this patch, we should probably keep it
for now since there's already content out in the wild relying on this
behavior.

r? @jdm @asajeffrey
bors-servo added a commit that referenced this pull request Feb 16, 2020
Always trigger an input sources change event on session creation

Fixes our behavior to match the spec, and to specifically do it in a way
that makes sense. This is also what Chromium does currently, though I'm
not sure if it does the scheduling the same way.

The spec for this may change, see immersive-web/webxr#961.

This fix, along with #25770 , makes
three.js content work on servo. Instead of this fix we can also wait for
mrdoob/three.js#18638 to land (which isn't
certain until we figure out more about
immersive-web/webxr#961 )

Even if immersive-web/webxr#961 decides to
choose the option that obviates this patch, we should probably keep it
for now since there's already content out in the wild relying on this
behavior.

r? @jdm @asajeffrey
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

4 participants
You can’t perform that action at this time.