commit | 96db3558cd5847112cb93c39bb33bc1b8ffb511a | [log] [tgz] |
---|---|---|
author | Vasiliy Telezhnikov <vasilyt@chromium.org> | Wed Nov 13 17:53:35 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Nov 13 17:53:35 2024 |
tree | a6cd6aa08cd50962c53ca96489eb3b851c42cadf | |
parent | af15897547c092c1dfe84b0a4fe9f38b737873e7 [diff] |
Remove flip from UnacceleratedStaticBitmapImage::CopyToResourceProvider The only resource provider that can have bottom-left origin is CanvasResourceProviderPassthrough, but it doesn't implement CreateSkSurface [1] which is needed for default WritePixels implementation [2] and it doesn't provide it's own. In practice this code is only called from WebGPU which uses CanvasResourceProviderSharedImage. There quite a few limitation on what we can do with bottom-left origin images, but in unlikely event if we need to support WritePixels to them flip should happen inside of the implementation. [1] https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/platform/graphics/canvas_resource_provider.cc;drc=981ce1e8f82050b33153a9c4652f2ad1cefabff1;l=852 [2] https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/platform/graphics/canvas_resource_provider.cc;drc=61318fca180640aa6607e78d67ec4dbe2ed00bfb;l=1790 Bug: 378688985 Change-Id: I6374b3d6c59330f623d8322c7c8ee20d9b97e089 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6017066 Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org> Reviewed-by: Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/main@{#1382435}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.