Skip to content
New issue

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

Remove text-rendering #7310

Closed
wants to merge 1 commit into from
Closed

Remove text-rendering #7310

wants to merge 1 commit into from

Conversation

SBoudrias
Copy link
Contributor

text-rendering is causing some pretty bad issue on Windows Chrome. Some special UTF-8 characters won't be shown and some text section can change font-face.

I created a reduced test case here: http://jsbin.com/uqisib/8/edit

  • First title is the default Boostrap breaking an UTF-8 char
  • Second use impact font-face to clearly mark the bug (utf-8 special char and font-face)
  • Third title just remove the text-rendering property to show the bug is resolved and is not related to the font-face

I guess right now the best solution is only to remove this property until better browser support.

This issue only affects Windows Chrome ATM (Firefox, Safari are good and other browser don't implement this property). As Browsers seems to only implement this property on Windows, I don't think it should change anything on Mac and Ubuntu.

@mdo
Copy link
Member

mdo commented Mar 18, 2013

Everything looks fine to me in Chrome for Mac.

@SBoudrias
Copy link
Contributor Author

Yeah, apparently known bugs on text-rendering in Chrome are only in Windows and Linux distribution. https://developer.mozilla.org/en-US/docs/CSS/text-rendering

@retlehs
Copy link
Contributor

retlehs commented Mar 18, 2013

related: i reported a chrome bug a few years ago related to optimizelegibility + font-variant that still isn't fixed

@retlehs
Copy link
Contributor

retlehs commented Mar 26, 2013

also just ran into an issue where optimizelegibility didn't allow a webfont to render on windows xp + chrome

bug: https://code.google.com/p/chromium/issues/detail?id=39017 (it's reported as fixed but i just made a comment)

@morgunder
Copy link

my android phone (htc mytouch) rendered basically wingdings for my h1..h6 tags. looked perfect on chrome on windows 7. the css below fixed it. is there are @media query to exclude just the chrome phone browsers?
h1, h2, h3, h4, h5, h6 {
text-rendering: auto;
}

@SBoudrias
Copy link
Contributor Author

@morgunder auto is the default text-rendering value - so making it default and removing it is the same thing.

There's no @media rules to target specific browsers - that's kind of the point of media queries: no UA sniffing.

Try again with chrome on windows 7 - I don't know if it's a bug related to JsBin, but the stylesheet haven't loaded the first time I accessed it - and it looked like "ok" - but on refresh then the stylesheet came back with the bug.

@mdo
Copy link
Member

mdo commented Apr 1, 2013

Done in v3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants