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
Remove XR canvas dirtying step. #25837
Conversation
Heads up! This PR modifies the following files:
|
r? @Manishearth |
@bors-servo r+ |
📌 Commit a832d72 has been approved by |
@bors-servo r=Manishearth |
📌 Commit c12a994 has been approved by |
Remove XR canvas dirtying step. Alan tells me that this is no longer necessary, and it causes layout operations to appear in immersive mode profiles when there should not be any.
💔 Test failed - status-taskcluster |
|
If it failed during cleanup that means |
I can reproduce those timeouts when running the tests with |
With the change in servo/webxr#135 the test passes for me. |
Run headless device on its own thread. We really want to stop using the main thread code path as much as possible, and it avoids timeouts in servo/servo#25837 when the main thread blocks in other parts of the pipeline and never ends up processing the pending XR events.
@bors-servo r=Manishearth |
📌 Commit aa060df has been approved by |
Remove XR canvas dirtying step. Alan tells me that this is no longer necessary, and it causes layout operations to appear in immersive mode profiles when there should not be any.
💔 Test failed - status-taskcluster |
☀️ Test successful - status-taskcluster |
Alan tells me that this is no longer necessary, and it causes layout operations to appear in immersive mode profiles when there should not be any.