diff options
| author | bors-servo <servo-ops@mozilla.com> | 2020-04-13 20:02:48 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-04-13 20:02:48 -0400 |
| commit | 33a74a4f4eb9a4df0b6ccf2b6988331e59ae2baa (patch) | |
| tree | 3aa801dea5093f393c53bb366a0bf7c7e0cdb757 /components/script/dom/keyboardevent.rs | |
| parent | 37b555a2d638e7aae17f9dad6cf8c66503cee899 (diff) | |
| parent | 453be48c94ca93ad092300a7e26d7756aed73c0a (diff) | |
| download | servo-33a74a4f4eb9a4df0b6ccf2b6988331e59ae2baa.tar.gz servo-33a74a4f4eb9a4df0b6ccf2b6988331e59ae2baa.zip | |
Auto merge of #26164 - Manishearth:dirty-endsession, r=jdm
Dirty canvas when exiting immersive sessions
Fixes https://github.com/servo/servo/issues/26162, fixes servo/webxr#155
We basically end up in a situation where the main thread is asleep. It's unclear to me why it doesn't wake up after attempts to interact with the screen, but we stopped dirtying the canvas during the immersive session (https://github.com/servo/servo/pull/26077) so the main thread wasn't awake initially.
This is probably not the cleanest fix -- we really should not be ending up in situations where the main thread is perma-asleep -- however, we should be dirtying the canvas after exiting immersive mode _anyway_ since the contents need to be shown to the user, so this fix is still valid, even if it's not fixing the root cause.
Diffstat (limited to 'components/script/dom/keyboardevent.rs')
0 files changed, 0 insertions, 0 deletions