We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug Submitted by a test user: Smart invert is inverting photos (i.e. profile, cover images)
To Reproduce Steps to reproduce the behavior:
Expected behavior I believe photos shouldn't get inverted at all? Or the opposite? Regardless, some are getting inverted and some are not.
Screenshots
The text was updated successfully, but these errors were encountered:
I don't think there's anything we can do to change this as it's Apple trying to be "smart" :)
AFAIK, all we can do is apply accessibilityIgnoresInvertColors = true where we don't want views/imageviews to be inverted
accessibilityIgnoresInvertColors = true
Sorry, something went wrong.
I don't think there's anything we can do to change this as it's Apple trying to be "smart" :) AFAIK, all we can do is apply accessibilityIgnoresInvertColors = true where we don't want views/imageviews to be inverted
This is right also is needed to add a CSS to the images or other media @media (inverted-colors) { img, video { filter: invert(100); } }
@media (inverted-colors) { img, video { filter: invert(100); } }
I've found a way to inject the CSS via App side when is detecting the smart invert. I should be uploading a PR soon
Should this issue be closed as there was a PR made and it was merged?
No branches or pull requests
Describe the bug
Submitted by a test user: Smart invert is inverting photos (i.e. profile, cover images)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I believe photos shouldn't get inverted at all? Or the opposite? Regardless, some are getting inverted and some are not.
Screenshots
The text was updated successfully, but these errors were encountered: