Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

escaped sequences preferred in css #1

Closed
krisbulman opened this Issue · 2 comments

2 participants

@krisbulman

I have a question about the decision about using UTF-8 chars instead of css escape sequences in 85ecac6

I have had no problems displaying these icons using css escape sequences in FF, Safari, or Chrome (commit 16cfc6a ).

Besides, wouldn't using special characters force us to use the @charset rule? http://reference.sitepoint.com/css/at-charset

Instead, this css method could be used:

content: "\2665"; /* ♥ */

and expressions can be added for earlier IE support

further reading:
http://coding.smashingmagazine.com/2011/03/19/styling-elements-with-glyphs-sprites-and-pseudo-elements/

Perhaps this has already been thought out, so just looking for some explanation on why that route was chosen.

@puzrin

2-bytes codes are ok, but 3-bytes are broken with escaped chars. Check out 74472c2 in chrome/opera, and you will see what i mean. Pay attention to symbols 1Fxxx.

Smashmag issue doesn't pay attention to 3-bytes chars.

@puzrin

I close this issue, since we can do nothing with it.

Currently:

  • firefox ok
  • opera ok
  • chrome fails to works with 3-byte escape chars.
@puzrin puzrin closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.