W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2020

Re: [csswg-drafts] [css-images] image-orientation:none violates same-origin policy (#5165)

From: Stephen Chenney via GitHub <sysbot+gh@w3.org>
Date: Mon, 27 Jul 2020 18:25:33 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-664562566-1595874331-sysbot+gh@w3.org>
As I understand it there is some agreement around baking the EXIF orientation (and other EXIF derived properties) into opaque images at decode and then pretending through the rest of the rendering pipeline that there is no EXIF data on opaque images (option 2 from https://github.com/w3c/csswg-drafts/issues/5165#issuecomment-654127723). In practice right now, that means opaque images with EXIF data would always behave like "image-orientation: from-image" regardless of any CSS style that might apply. Plus any style query would always respect orientation.

I support this because it is chromium's long term intent to remove the "image-orientation" property and moving closer to that goal while improving security seems like a win.

GitHub Notification of comment by schenney-chromium
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5165#issuecomment-664562566 using your GitHub account
Received on Monday, 27 July 2020 18:25:34 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:11 UTC