2 ms·
If people took the time to build a custom solution using CSS/js to display the images, why not just pre-process them instead? IMO respecting the orientation tag
by ricardobeat 13y ago
If people took the time to build a custom solution using CSS/js to display the images, why not just pre-process them instead? IMO respecting the orientation tag by default wouldn't be unexpected at all.
Btw, images are oriented correctly on Mobile Safari.
- untog 13y agoMuch like the CSS border-box box sizing property makes a lot more sense, it would still cause issues if the browser changed behaviour. However, if it's your site, it's as simple as adding *{ image-orientation: from-image } to your CSS file to apply it everywhere.
- erichurkman 13y agoI know having a wildcard the end of a rule is non-performant ("ul > " for example has to check the parent of every* element to see if is a UL element; or even worse, "ul *" would have to check the entire ancestor tree of every element). Is there a performance impact of applying that rule to every element?
- ricardobeat 13y agoI don't think that's a fair parallel. Box models are different standards, whereas displaying an image in the wrong orientation is just wrong. A better comparison would be the <audio> tag playing everything at 22khz, then requiring { sampling-rate: from-audio } to work correctly. I haven't seen any examples of a website implementing custom rotation using css or canvas, it wasn't even possible to read EXIF data on the client until a year or so. Is it a real concern?