-
Notifications
You must be signed in to change notification settings - Fork 297
Tile external buffer images when they exceed the maximum texture size. #1036
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
Conversation
Much better, thanks! |
📌 Commit b556ba8 has been approved by |
🔒 Merge conflict |
☔ The latest upstream changes (presumably #997) made this pull request unmergeable. Please resolve the merge conflicts. |
b556ba8
to
16743c5
Compare
Rebased. It doesn't read as nicely anymore due to the verbosity of ExternalImageData. I am tempted to change ImageData::External to be |
webrender/src/resource_cache.rs
Outdated
&ImageData::Raw(_) => { size_check } | ||
&ImageData::Blob(_) => { size_check } | ||
&ImageData::External(ExternalImageData { image_type: ExternalImageType::ExternalBuffer, .. }) => { | ||
size_check |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: could do data.image_type == ExternalImageType::ExternalBuffer && size_check
instead of pattern matching
38b789e
to
97cdf3e
Compare
97cdf3e
to
48d7c6a
Compare
@bors-servo r+ |
📌 Commit 48d7c6a has been approved by |
Tile external buffer images when they exceed the maximum texture size. Fixes issue #1027, and addresses a review comment from PR #1004 about explicitly enumerating all variants instead of using ```_ => { ... }``` in this match expression. r? @kvark <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/webrender/1036) <!-- Reviewable:end -->
☀️ Test successful - status-travis |
Fixes issue #1027, and addresses a review comment from PR #1004 about explicitly enumerating all variants instead of using
_ => { ... }
in this match expression.r? @kvark
This change is