We also stumbled upon this when our mobile suddenly behaved differently and finally find the root cause of this.
Both WebKit (iOS) and Android (Chrome) have just recently changed the default behavior of the image-orientation
CSS propterty. While it was none
before, it is now from-image
. This means: Before, they ignored the EXIF data of an image by default, while they are now using it to auto-correct the image. Which break our own auto-correction based on the exifreader
library.
Here are some relevant links:
Funny enough, also the Slack team seems to have run into this:
Fortunately, the author of the exifreader
library (who just some weeks later ran into the same problems) also guided me to a way to detect the behavior. You can find his answer here:
I also noticed that Modernizr has a test for this, so I am actually using a custom modernizr build now to detect the browser behavior.