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

Re: [csswg-drafts] [css-images] Consider changing initial value of 'image-orientation' to from-image (#3799)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 31 Jul 2019 16:14:54 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-516918322-1564589693-sysbot+gh@w3.org>
The CSS Working Group just discussed `Consider changing initial value of 'image-orientation' to from-image`, and agreed to the following:

* `RESOLVED: Accept proposal with an added note current solution is experimental and may change`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Consider changing initial value of 'image-orientation' to from-image<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/3799<br>
&lt;dael> TabAtkins: Some time ago when wrote image-orientation we set initial to none. People requested inital to be from-image so it can auto rotate based on what camera captured. Some safari does and some don't. smfr wants apple stuff consistent<br>
&lt;dael> TabAtkins: We did use counter and found numbers reasonable. Lots of images have default xif value.<br>
&lt;dael> TabAtkins: Less then a millionth have orientation data so will be changed. We don't know how many will change for the better and which for the worse. From personal experience I suspect a lot will be fixed. I see a lot incorrect on the web.<br>
&lt;dael> TabAtkins: Given tiny % of poss breakage we recommend init value is from-image<br>
&lt;tantek> wow I'm guessing lots of bad invisible EXIF data that's been neglected to date is going to start screwing up images<br>
&lt;dael> plinss: A little concerning to me. I wrote code that does exif determination. How do you make that work in fallback if browser won't do that.<br>
&lt;tantek> is there a way to query any web image search service for the EXIF properties (or even existence thereof) ?<br>
&lt;dael> TabAtkins: If you have control over image correct is rotate and fix exif or remove the exif and do the transform on browser side. Either works consistently regardless of browser initial value<br>
&lt;dael> dbaron: It seems like it would be good if you make change to spec you should note it's experimental and might change back if there's compat problems.<br>
&lt;dael> TabAtkins: Yep<br>
&lt;dael> smfr: iOS has been this way for many years. I think...there will be compat problems but benefits outweigh. Most common images with exif orientation are those from mobile devices. This benefits those images most which is common.<br>
&lt;dael> plinss: Agree it's desired. Just concerned on compat and make sure websites can manage if they need to.<br>
&lt;dael> smfr: Can with image-orientation css prop<br>
&lt;tantek> +1 to dbaron's suggestion, and what plinss said<br>
&lt;dael> plinss: Yeah, worst case can change behavior<br>
&lt;dael> dbaron: Is iOS detectable by looking at computed value of image orientation?<br>
&lt;dael> smfr: I don't think we support image orientation yet. Just respect exif. Want to both everywhere at the same time. On iOS I don't think it's detectable by web content if image rotated through exif data<br>
&lt;dael> plinss: I don't remember details. I remember a lot of work to make it cross browser. Don't object right now. I'll look at what I did and see if it's problematic and if it is I'll bring it up.<br>
&lt;dael> Rossen_: Sounds like leaning toward accepting proposal with an added note current solution is experimental and may change<br>
&lt;tantek> no objections, but expecting breakage<br>
&lt;dael> RESOLVED: Accept proposal with an added note current solution is experimental and may change<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3799#issuecomment-516918322 using your GitHub account
Received on Wednesday, 31 July 2019 16:14:56 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:50 UTC