-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Revert "[skwasm] Use transferToImageBitmap instead of createImageBitmap (#163251)"
#171238
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
Revert "[skwasm] Use transferToImageBitmap instead of createImageBitmap (#163251)"
#171238
Conversation
…itmap` (flutter#163251)" This reverts commit 7d22606. It turns out that in many scenarios, resizing the OffscreenCanvas multiple times per frame is prohibitively expensive. It also turns out that neither API works well enough on non-Chrome browsers to make it viable anyway, so we should switch back to `createImageBitmap`.
|
It looks like this pull request may not have tests. Please make sure to add tests or get an explicit test exemption before merging. If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix? Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.If you believe this PR qualifies for a test exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group. |
transferToImageBitmap instead of `createImageB…transferToImageBitmap instead of createImageBitmap (#163251)"
|
Golden file changes have been found for this pull request. Click here to view and triage (e.g. because this is an intentional change). If you are still iterating on this change and are not ready to resolve the images on the Flutter Gold dashboard, consider marking this PR as a draft pull request above. You will still be able to view image results on the dashboard, commenting will be silenced, and the check will not try to resolve itself until marked ready for review. For more guidance, visit Writing a golden file test for Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
harryterkelsen
left a comment
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.
LGTM
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…itmap` (flutter#163251)" (flutter#171238) This reverts commit 7d22606. It turns out that in many scenarios, resizing the OffscreenCanvas multiple times per frame is prohibitively expensive. It also turns out that neither API works well enough on non-Chrome browsers to make it viable anyway, so we should switch back to `createImageBitmap`.
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…eateImageBitmap` (#163251)" (flutter/flutter#171238)
…itmap` (flutter#163251)" (flutter#171238) This reverts commit 7d22606. It turns out that in many scenarios, resizing the OffscreenCanvas multiple times per frame is prohibitively expensive. It also turns out that neither API works well enough on non-Chrome browsers to make it viable anyway, so we should switch back to `createImageBitmap`.
This reverts commit 7d22606.
It turns out that in many scenarios, resizing the OffscreenCanvas multiple times per frame is prohibitively expensive. It also turns out that neither API works well enough on non-Chrome browsers to make it viable anyway, so we should switch back to
createImageBitmap.