Text rendering fix for Android (and arguably for Windows) #132
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…dows, and garbles text on Android
|
I'm in favor of removing this and have done so for the 1.2 release already. This setting should be reserved for the OS-level (if you want it on OS X, just turn off LCD font smoothing entirely). |
|
+1 for this. I just posted a comment on the previously closed issue: |
|
Word. Going to close this since the next release is coming soon and we have this in there. |
|
This is still an issue on 2.0.2 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I understand that your project doesn't officially support WebKit on Android as a browser, but it's a shame to have Bootstrap sites be garbled on Android when they don't have to be. I've found the CSS rule that was causing failure on Android (text-rendering: optimizeLegibility) and commented it out.
As a side effect of removing this line, I have found that fonts on my site render much better on Windows. The "optimizeLegibility" declaration was causing Windows to adopt an aggressive hinting strategy that actively changed the heights of some glyphs, giving text a haphazard appearance.
Of course, you should weigh this benefit against whatever motivation you had to include that rule.