W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2019

Re: [csswg-drafts] [css-images] Should the values of image-orientation include the <angle> variants? (#4164)

From: Simon Pieters via GitHub <sysbot+gh@w3.org>
Date: Tue, 20 Aug 2019 14:54:59 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-523052636-1566312897-sysbot+gh@w3.org>
@smfr 

Current browser behavior (except for iOS Safari) is to ignore EXIF orientation (in most cases). The change to the default behavior to respect the EXIF orientation could break web content that is currently working (except maybe in iOS Safari). The `image-orientation` property gives web developers an easy fix -- specify `none` to get the old behavior back.

So if we're removing the property, we should have something else to recommend instead. What is it?

I can think of:

1. Fix the EXIF in the image file (requires changing the image file)
2. Change the image data (requires changing the image file)
3. Parse the EXIF in JavaScript and apply it in a `canvas` like in https://github.com/blueimp/JavaScript-Load-Image 

Am I missing some other option? If (1) and (2) are non-options for some people, I wouldn't want to recommend (3). It seems worse than `image-orientation` in several ways (it has worse performance, uses more memory, doesn't integrate well with native image features like `srcset`/`picture` and `loading=lazy`, it requires JS...)

-- 
GitHub Notification of comment by zcorpan
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4164#issuecomment-523052636 using your GitHub account
Received on Tuesday, 20 August 2019 14:55:01 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:31:13 UTC