diff options
| author |  Brian Osman <brianosman@google.com> | 2017-01-05 10:41:39 -0500 |
|---|---|---|
| committer |  Skia Commit-Bot <skia-commit-bot@chromium.org> | 2017-01-05 18:07:55 +0000 |
| commit | efcc41805b43347444b83c1705d3d60c8d0caa70 (patch) | |
| tree | 705426a2eec1856364552d03c3648c319fe9e0bc /gm/gradientDirtyLaundry.cpp | |
| parent | 08d57e6ae6510a7724119ab548485b4fcbd0a48d (diff) | |
Explicitly fail read/writePixels in invalid color space scenarios
It's not well defined what to do when moving from a nullptr color space to
a tagged destination (drawing, reading, writing, etc...). In these
scenarios, at least, we can choose to disallow the operation (rather than
produce an unexpected or inconsistent result).
BUG=skia:
Change-Id: I033b23c6f2bb00664efc8fdab1b3f52053d77695
Reviewed-on: https://skia-review.googlesource.com/6600
Commit-Queue: Brian Osman <brianosman@google.com>
Reviewed-by: Brian Salomon <bsalomon@google.com>
Reviewed-by: Matt Sarett <msarett@google.com>
Diffstat (limited to 'gm/gradientDirtyLaundry.cpp')
0 files changed, 0 insertions, 0 deletions