Jump to content
Search Community

pixel-fiend

Members
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

1,352 profile views

pixel-fiend's Achievements

1

Reputation

  1. 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.
  2. It's a character for defining skin tone. I've posted on SO, too. http://stackoverflow.com/questions/34421887/splitting-emoji-safely#34422128
  3. Here's a new pen with some invisible fleshy blocks http://codepen.io/positlabs/pen/QyEOEG?editors=011
  4. I found a very long regex that might help. https://github.com/mathiasbynens/emoji-regex/blob/master/index.js
  5. Here's my fork http://codepen.io/positlabs/pen/XXKeJX
  6. 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?
  7. 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*/ http://eslint.org/docs/user-guide/configuring.html
×
×
  • Create New...