1. 15 Nov, 2017 1 commit
  2. 14 Nov, 2017 1 commit
  3. 24 Apr, 2017 1 commit
  4. 06 Mar, 2017 1 commit
    • Eric Eastwood's avatar
      Use native unicode emojis · e6fc0207
      Eric Eastwood authored
       - gl_emoji for falling back to image/css-sprite when the browser
         doesn't support an emoji
       - Markdown rendering (Banzai filter)
       - Autocomplete
       - Award emoji menu
          - Perceived perf
          - Immediate response because we now build client-side
       - Update `digests.json` generation in gemojione rake task to be more
         useful and  include `unicodeVersion`
      MR: !9437
      See issues
       - #26371
       - #27250
       - #22474
  5. 18 Jul, 2016 1 commit
  6. 29 Jun, 2016 1 commit
  7. 09 Apr, 2016 1 commit
  8. 30 Mar, 2016 1 commit
    • Yorick Peterse's avatar
      Pre-calculate Emoji digests · 5830d80b
      Yorick Peterse authored
      By pre-calculating the digests we can manually construct the emoji URLs,
      removing the need for using Rails' asset URL helpers. The reason we
      don't want to use these helpers for Emojis is two-fold:
      1. Rails' image_url() method is slow, really slow. For one it _might_
         have to calculate digests but it also performs a lot of other
         intensive operations (judging by the source code and based on
         measuring timings).
      2. We have a lot of Emoji which coupled with the above can result in it
         taking minutes to load Emoji autocomplete data.
      Using this pre-calculation setup generating the digests takes around 7
      seconds (including the time it takes to start Rails/Rake), and only
      around 600 milliseconds to load _all_ the autocomplete data of a project
      (measured locally).
      This commit _does_ change the Emoji URLs from absolute to relative URLs
      as these are much easier to generate.
      To update the Emoji data simply run:
          rake gemojione:digests
      Then commit any changes.
      Fixes gitlab-org/gitlab-ce#14009