I think we currently don't really try to handle these cases:

That tip probably does not fit on screen in any of the orientations: it obviously won't fit to the north or east. If we try to put it to the south, part of it will be offscreen to the right. If we try to put it to the west, part of it will be off the top of the screen (the rectangle we use to detect the size of the tip box is slightly larger than the actual pixel size of the tip because we get weird scrollbar interactions if we use the size of the tip exactly).

My trick is:

Yeah I couldn't quite grab a screen

Here's what I see:

Chrome:

• Go to Workboard
• Click Fullscreen
• Hover over Fullscreen - tooltip is elsewhere?

I see, it must be a text file.

Safari / OSX:

word-break: break-all; seems to be working fine.

I can't reproduce this, is there a specific browser/OS I should test? Also, feel free to upload a test file to rGITTEST

Probably will implement in Badges and see how it goes. I'd mildly agree with your (only) mild concern about mild confusion if admins do a poor job labeling stuff.

Also I very probably meant "inline comment" and not "inline diff"

Oh, I missed "inline". That reproduces for me. I'll file a separate issue.

I do not have persistent chat open.

Do you have persistent chat open?

I came across a small bug with the "auto-suggest" feature. In differential I was writing an inline diff, and ended with :/ to show my face in plain ascii, and hit ⌘+⏎ immediately after to complete my inline diff. After typing :/ the auto-complete popped up and when I saved the draft with ⌘+⏎ it forever immortalized the auto-complete popup on screen with no seeming way to get rid of it (refreshing probably fixes~). I can reproduce on this install.

In T12139#208563, @chad wrote:

If you're on linux, I think emojione extension likely only choice. What OS/Browser?

hmm everything seems in order

Click here for 🐱

He's so little. :)

These are still so painful on non-Safari

Poor 🐈.

yup it works

💯

I rolled the server for the bug testers.

🐱

🐱

🐱

🐱

🐱

🐱

🐈

🐈

🐈

🐈

🐈

🐈

I guess I don't even have a glyph for :lion_face: anyway.

I've already started the 2 minute arc diff process

Also while you're in there maybe replace _ with (space) in the strings? I can't find :lion_face: by typing :fac... right now, but I think if you swap the underscores for spaces it will work. Then :cat should be able to find crying_cat_face and stuff, too.

not memorizing emoji collation order in 2017 pfft

FINE IT IS MY FAULT

The list is sorted by emoji. 🐈 is "alphabetically" earlier than 🐱 in the list of emoji.

cats are naturally dubious so i'm not surprised

I can't figure out the sort thing, don't think it's an emoji issue.

sort by awesome, descending

Cat2 is twice as good as Cat

Typing :cat will list the cat2 emoji before cat
🐱

Found the Chrome issue / Mac: https://bugs.chromium.org/p/chromium/issues/detail?id=551420

@johnny-bit I had good luck using https://chrome.google.com/webstore/detail/chromoji-emojis-for-googl/negakbijaemdgbhklopmghphgaeadmpo on Ubuntu/Chrome.

If you're on linux, I think emojione extension likely only choice. What OS/Browser?

Oh, woe is me, for there are no colours in my emoji. One thing to notice though - where can I find that beautiful emoji example in ui examples? Would be cool place to check for emoji support on different browsers/platforms :)

wow! the beautiful colors!

@avivey let me know how this looks now

https://www.tjvantoll.com/2016/06/15/emoji-on-windows/

Well, not non-existent, just black and white line art.

Yeah emoji on Windows is non-existent still. At least, on Windows 10 Chrome / Firefox / Edge it's just what @avivey posted above.

Crazy

In T12139#208257, @epriestley wrote:

Pros

• Users on old versions of Windows or who compiled their own Gentoo don't have occasional missing/fallback emoji.
• Users see the same picture of a smiling cat instead of different pictures of smiling cats.

If I can get most places to appear like Safari shows them, this will probably be good for a v1. The reason I like EmojiOne is mostly aesthetic, they are less busy visually (flatter) and are easier to determine what they are individually. I can also control the size. Let me futz with our emoji remarkup rule and see if I can normalize the display better. Though, not sure that's really possible still given Google search results.

Chrome/Firefox seems to be shrinking them smaller. I think we can maybe cheat that with font-size and the emoji remarkup rule...

This is what I see on my Macbook in Safari:

oh man, at least in Safari they look way better.

I believe Firefox is adopting EmojiOne. If I could CSS style the emojis, it would help. I find them small and hard to identify in text. Basic ones like ❤️ are easy, but all the different emotions are somewhat harder. 😁 vis. 😂 really are hard for me to visually focus on (and on my laptop, which is smaller dpi, is even harder).

Emoji look terrible on nearly every platform / browser

phurl autocomplete might be nice too

All I've learned is:

Maybe someday this will be easier; https://lists.w3.org/Archives/Public/www-style/2016Mar/0370.html

I'll get back to you

Well

I think the pros and cons are something like:

oh man these crack me up.

Haha, sorry I think this might be a good JS learning side project for me on the weekends if I have free time.

I think we should just use actual emoji for this, not sprite sheets?

In D17238#205025, @epriestley wrote:

Yep, go for it.