-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
createImageBitmap: stop clipping sourceRect to the source's dimensions #6346
Conversation
It has been found in whatwg#6306 that this was an oversight at the time of its introduction. Current behavior goes against web-authors expectations and no implementers has opposed against the change to "no-clip".
@whatwg/canvas could you please review this PR and the linked tests. Thanks! |
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.
I believe this is a no-op for Firefox one we revert the spec here.
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.
Hopefully this won't introduce too much complexity in implementations, because of the need to produce transparent pixels for the region outside of input
, but I understand the application-level concerns. Looks good to me.
@kenrussell @jdashg could you review web-platform-tests/wpt#27040 as well? |
Neither Ken nor I have write access, so our Approvals are treated as unofficial. It looks like we either need Approval from someone with existing write access, or we need to get added somehow. |
Thanks everyone! (@jdashg yeah, the editors/maintainers (of which I'm one) sometimes delegate review to ensure all is in order with the technical change, and then only review editorial matters and ensure https://whatwg.org/working-mode#changes is followed.) |
…ing, a=testonly Automatic update from web-platform-tests HTML: createImageBitmap() for out of bound clipping For whatwg/html#6346. -- wpt-commits: f480960da2cb3cc827f6fe4ac629b6dd229b0fea wpt-pr: 27040
…ing, a=testonly Automatic update from web-platform-tests HTML: createImageBitmap() for out of bound clipping For whatwg/html#6346. -- wpt-commits: f480960da2cb3cc827f6fe4ac629b6dd229b0fea wpt-pr: 27040 UltraBlame original commit: 10a1015aa806f8b426d358d9f4546a2240b6b8ee
…ing, a=testonly Automatic update from web-platform-tests HTML: createImageBitmap() for out of bound clipping For whatwg/html#6346. -- wpt-commits: f480960da2cb3cc827f6fe4ac629b6dd229b0fea wpt-pr: 27040 UltraBlame original commit: 10a1015aa806f8b426d358d9f4546a2240b6b8ee
…ing, a=testonly Automatic update from web-platform-tests HTML: createImageBitmap() for out of bound clipping For whatwg/html#6346. -- wpt-commits: f480960da2cb3cc827f6fe4ac629b6dd229b0fea wpt-pr: 27040 UltraBlame original commit: 10a1015aa806f8b426d358d9f4546a2240b6b8ee
…ing, a=testonly Automatic update from web-platform-tests HTML: createImageBitmap() for out of bound clipping For whatwg/html#6346. -- wpt-commits: f480960da2cb3cc827f6fe4ac629b6dd229b0fea wpt-pr: 27040
Currently the specs ask that when a ImageBitmap is created, its source rectangle should get clipped to the source image's dimensions.
It has been found in #6306 that this was an oversight at the time of its introduction.
Current behavior goes against web-authors expectations and no implementer has opposed against the change to "no-clip".
(See WHATWG Working Mode: Changes for more details.)
/imagebitmap-and-animations.html ( diff )