Closed akdotcom closed 9 years ago
Yeah I remember this, any ideas on how to get around it? Call it plus1
instead?
I'd maybe designate an special character, say _
, to indicate that this is a special case and keep it out of the normal namespace? So _plus1
indicates that this is an emoji name requiring special handling. Not sure if it's worth codifying that _plus
means +
or if it's better to look for the _
prefix and branch accordingly
Would you mind checking again on the latest version? Thanks
:+1: working!
Thanks for reporting back!
Thanks for taking a crack at it so quickly! BTW, we're using the library via bower, so eagerly waiting for 1.0.0 to land there =)
You should really thank @adam-lynch and @4ver, this was all their work :smile:
PS: I don't understand why Bower isn't updating, everything seems to be in order :confounded:
Thanks @adam-lynch & @4ver !!
Emoji names aren't currently being sanitized, leading to the creation of a the +1.png filename and the generation of a .emoji-+1 css rule.
'+' is a reserved character in URLs and in CSS. As far as I know, this isn't breaking anything on the URL side, but it does mean that emojify.css's auto generated CSS rule for +1 isn't working.