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

Enable webxr by default #24777

Merged
merged 1 commit into from Nov 20, 2019
Merged

Enable webxr by default #24777

merged 1 commit into from Nov 20, 2019

Conversation

@jdm
Copy link
Member

jdm commented Nov 18, 2019

This changes two things:

  • enable WebXR by default, since it's not exactly an experimental technology in Servo anymore
  • enable the glwindow webxr backend by default so it's easier to test WebXR on desktop nightlies

Since the glwindow pref is only checked in the glutin desktop port, enabling it for other ports does not hurt us at all and it removes a papercut for testing WebXR content on desktop.


This change is Reviewable

@jdm jdm changed the title Enable webxr by default. Enable webxr by default Nov 18, 2019
@jdm
Copy link
Member Author

jdm commented Nov 18, 2019

@highfive highfive assigned Manishearth and unassigned paulrouget Nov 18, 2019
Copy link
Member

Manishearth left a comment

(Wouldn't this require interfaces.html updates in the mozilla tests?)

So I'm okay with landing this, but also I'm a bit wary: this means we're releasing webxr by default, and we need to figure out how that factors in to web stability stuff. Firstly: Are we allowed to do this? Is it okay to release a browser containing currently-still-in-flux APIs? I guess webxr is very close to shipping/stabilizing so perhaps we're fine on that front.

Also, does this count as a separate shipped implementation according to the w3c? (because then servo+firefox might automatically count for various spec stability requirements). Servo is currently only "shipped" as a nightly, so perhaps none of this is relevant yet. But I don't know.

cc @larsbergstrom

@Manishearth
Copy link
Member

Manishearth commented Nov 18, 2019

@bors-servo r+

from reading https://www.w3.org/2019/Process-20190301/#implementation-experience it seems like it doesn't really matter if it's enabled by default or not

@bors-servo
Copy link
Contributor

bors-servo commented Nov 18, 2019

📌 Commit 4a8e5dc has been approved by Manishearth

@larsbergstrom
Copy link
Contributor

larsbergstrom commented Nov 18, 2019

As Servo is not currently shipping in a production browser to end users, it has not been considered a separate "shipped" browser in the W3C/Khronos sense to date. Once that does happen, the specific browser context (e.g., Firefox Reality on Hololens2) would "count", but the engine would be a slightly different thing, as it is for the difference between blink or webkit implementing something vs. Chrome or Safari shipping it. e.g., last I checked WebVR is in webkit due to some awesome work by Igalia, but is not on by default in any webkit-derived browser.

@bors-servo
Copy link
Contributor

bors-servo commented Nov 19, 2019

Testing commit 4a8e5dc with merge ad9148c...

bors-servo added a commit that referenced this pull request Nov 19, 2019
Enable webxr by default

This changes two things:
* enable WebXR by default, since it's not exactly an experimental technology in Servo anymore
* enable the glwindow webxr backend by default so it's easier to test WebXR on desktop nightlies

Since the glwindow pref is only checked in the glutin desktop port, enabling it for other ports does not hurt us at all and it removes a papercut for testing WebXR content on desktop.
@bors-servo
Copy link
Contributor

bors-servo commented Nov 19, 2019

💔 Test failed - linux-rel-css

@jdm jdm force-pushed the jdm-patch-34 branch from 4a8e5dc to 46ff8a8 Nov 19, 2019
@jdm
Copy link
Member Author

jdm commented Nov 19, 2019

@bors-servo r=Manishearth

@bors-servo
Copy link
Contributor

bors-servo commented Nov 19, 2019

📌 Commit 46ff8a8 has been approved by Manishearth

@bors-servo
Copy link
Contributor

bors-servo commented Nov 20, 2019

Testing commit 46ff8a8 with merge bb68e6b...

bors-servo added a commit that referenced this pull request Nov 20, 2019
Enable webxr by default

This changes two things:
* enable WebXR by default, since it's not exactly an experimental technology in Servo anymore
* enable the glwindow webxr backend by default so it's easier to test WebXR on desktop nightlies

Since the glwindow pref is only checked in the glutin desktop port, enabling it for other ports does not hurt us at all and it removes a papercut for testing WebXR content on desktop.
@bors-servo
Copy link
Contributor

bors-servo commented Nov 20, 2019

💔 Test failed - status-taskcluster

@CYBAI
Copy link
Collaborator

CYBAI commented Nov 20, 2019

 0:09.11�(B ERROR�(B Manifest /repo/tests/wpt/mozilla/meta/MANIFEST.json is outdated, use |./mach update-manifest| to fix.
@jdm
Copy link
Member Author

jdm commented Nov 20, 2019

@bors-servo r=Manishearth

@bors-servo
Copy link
Contributor

bors-servo commented Nov 20, 2019

📌 Commit 0863fc4 has been approved by Manishearth

@bors-servo
Copy link
Contributor

bors-servo commented Nov 20, 2019

The latest upstream changes (presumably #24499) made this pull request unmergeable. Please resolve the merge conflicts.

@jdm jdm force-pushed the jdm-patch-34 branch from 0863fc4 to 5e2f260 Nov 20, 2019
@jdm
Copy link
Member Author

jdm commented Nov 20, 2019

@bors-servo r=Manishearth

@bors-servo
Copy link
Contributor

bors-servo commented Nov 20, 2019

📌 Commit 5e2f260 has been approved by Manishearth

@bors-servo
Copy link
Contributor

bors-servo commented Nov 20, 2019

Testing commit 5e2f260 with merge 994ab2d...

bors-servo added a commit that referenced this pull request Nov 20, 2019
Enable webxr by default

This changes two things:
* enable WebXR by default, since it's not exactly an experimental technology in Servo anymore
* enable the glwindow webxr backend by default so it's easier to test WebXR on desktop nightlies

Since the glwindow pref is only checked in the glutin desktop port, enabling it for other ports does not hurt us at all and it removes a papercut for testing WebXR content on desktop.

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/24777)
<!-- Reviewable:end -->
@jdm jdm force-pushed the jdm-patch-34 branch from 5e2f260 to b816c0f Nov 20, 2019
@jdm
Copy link
Member Author

jdm commented Nov 20, 2019

@bors-servo r=Manishearth

@bors-servo
Copy link
Contributor

bors-servo commented Nov 20, 2019

📌 Commit b816c0f has been approved by Manishearth

@bors-servo
Copy link
Contributor

bors-servo commented Nov 20, 2019

Testing commit b816c0f with merge eb363ec...

bors-servo added a commit that referenced this pull request Nov 20, 2019
Enable webxr by default

This changes two things:
* enable WebXR by default, since it's not exactly an experimental technology in Servo anymore
* enable the glwindow webxr backend by default so it's easier to test WebXR on desktop nightlies

Since the glwindow pref is only checked in the glutin desktop port, enabling it for other ports does not hurt us at all and it removes a papercut for testing WebXR content on desktop.

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/24777)
<!-- Reviewable:end -->
@bors-servo
Copy link
Contributor

bors-servo commented Nov 20, 2019

☀️ Test successful - linux-rel-css, linux-rel-wpt, status-taskcluster
Approved by: Manishearth
Pushing eb363ec to master...

@bors-servo bors-servo merged commit b816c0f into master Nov 20, 2019
2 checks passed
2 checks passed
Community-TC (pull_request) TaskGroup: success
Details
homu Test successful
Details
@bors-servo bors-servo deleted the jdm-patch-34 branch Nov 20, 2019
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.

None yet

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