pixel-fiend
Content Type
Profiles
Forums
Store
Blog
Product
Showcase
FAQ
Downloads
Posts posted by pixel-fiend
-
-
It's a character for defining skin tone.
I've posted on SO, too. http://stackoverflow.com/questions/34421887/splitting-emoji-safely#34422128
- 1
-
Here's a new pen with some invisible fleshy blocks
See the Pen QyEOEG?editors=011 by positlabs (@positlabs) on CodePen
-
I found a very long regex that might help. https://github.com/mathiasbynens/emoji-regex/blob/master/index.js
-
-
I'm trying to use SplitText with some text that contains emoticons. However, splitting an emoticon with an empty string will yield two garbage characters
" ??:".split("")
["�", "�"]
Here's an article that mentions the problem:
https://mathiasbynens.be/notes/javascript-unicode
I can hack a workaround, but is there any chance this will be supported in the future?
-
I'm guessing you should define TweenMax as a global var, so ESLint doesn't complain about it.
"Any reference to an undeclared variable causes a warning, unless the variable is explicitly mentioned in a /*global ...*/ comment."
So you need to include this /*global TweenMax*/
Emoticons in SplitText
in GSAP
Posted
For now, I'm only concerned with it working in Chrome. My lazy solution was to simply remove the skin-tone blocks from the string.
The skin-tone characters are definitely there, and have a purpose. They just fail to render correctly in some cases. I've seen it fail on twitter, but not every time.