[csswg-drafts] [css-images] image-orientation and canvas drawImage (#4666)

schenney-chromium has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-images] image-orientation and canvas drawImage ==
More questions on https://drafts.csswg.org/css-images/#the-image-orientation 

As of Canary version 81.0.4017.0 chromium supports the image-orientation property for all images in all locations, defaulting to the "from-image" value but also supporting "none" to turn off exif image-orientation.

In numerous cases where there is not yet a code path to access the CSS property,  chromium will use "from-image". Right now that means that canvas drawImage calls will always respect the exif orientation.

1. Assuming we support image-orientation: none for drawImage, which element's image-orientation property should take priority when there is a conflict between the source element and the canvas element? I argue for the source but welcome feedback.

2. Given Safari does not support "none", should chromium just always use image-orientation: from-image in this situation?

There are some other similar cases: when an image is dragged and maybe when WebGL binds an image as texture. In all cases I argue that we respect the source's preferred orientation as that will avoid the image appearing to rotate when dragged or copied.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4666 using your GitHub account

Received on Monday, 13 January 2020 16:08:13 UTC