Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upRemove XR canvas dirtying step. #25837
Conversation
highfive
commented
Feb 24, 2020
|
Heads up! This PR modifies the following files:
|
highfive
commented
Feb 24, 2020
|
r? @Manishearth |
|
@bors-servo r+ |
|
|
|
@bors-servo r=Manishearth |
|
|
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.
|
|
|
|
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 |
|
|
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.
|
|
|
@bors-servo retry |
|
|
jdm commentedFeb 24, 2020
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.