diff options
author | bors-servo <lbergstrom+bors@mozilla.com> | 2019-10-10 12:09:32 -0400 |
---|---|---|
committer | GitHub <noreply@github.com> | 2019-10-10 12:09:32 -0400 |
commit | ab8d99856ec50752f1ec58086fc684d5e83eeaaf (patch) | |
tree | a12b1d368c8160bcab00e4b2def53c4682ba8e02 /components/layout_2020/flow/construct.rs | |
parent | 4ce72bb4d13a6fe9138b5c01ba08a98553f5b2b4 (diff) | |
parent | c53680b282aa5bf77ca15b8a4f9ae84afb8b9361 (diff) | |
download | servo-ab8d99856ec50752f1ec58086fc684d5e83eeaaf.tar.gz servo-ab8d99856ec50752f1ec58086fc684d5e83eeaaf.zip |
Auto merge of #24386 - jdm:no-preserve-drawing-buffer, r=nox
webgl: Clear the drawing buffer when preserveDrawingBuffer is false.
This adds an explicit clear operation to a webgl canvas when the preserveDrawingBuffer attribute is false when creating the context. Because we're not using double buffering this may end up making some demos worse (ie. a clear operation at a random time while drawing a frame), but this problem is expected to go away when #24256 is fixed and we move to a multi-buffered frame setup. This change is important at this time because so many babylon.js demos rely on the engine clearing the frame, per the specification.
---
- [x] `./mach build -d` does not report any errors
- [x] `./mach test-tidy` does not report any errors
- [x] These changes fix #21132
- [x] There are tests for these changes
<!-- 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/24386)
<!-- Reviewable:end -->
Diffstat (limited to 'components/layout_2020/flow/construct.rs')
0 files changed, 0 insertions, 0 deletions