Sometimes I use emoji in my table cells to make them more visual.
In Chrome on Mac emoji + space + text (for example: “
Be more eco friendly”) is displayed without a space between emoji and text. Both when emoji is the first character in the cell or when emoji is in the middle of the text. Space is preserved and displayed when emoji is located after the text.
In Safari on Mac everything is OK.
I have noticed this as well and will check in again with the team, but IIRC, this is a weird issue that might not be easily solved because it has to do with how Chrome renders the emoji and it’s different from first display to rendering from cache. I think it’s when the emoji is cached that we lose the space. And it’s not as much losing the space, but Chrome not reserving enough space for the emoji, so your cursor will show overlapping the right side of it.
We’ll take another look and see if there is something we can do. I’ve found myself adding two spaces after which then looks wrong on other browsers.
Thanks, @BenLee! I don’t usually use Chrome, but thought Coda team would like to know about this as Chrome is probably more popular among your users than Safari
There is a reason @BenLee if all the emoji I am using in my doc are changed to black and white? Are you changing something lately this week?
I don’t think anything has changed to cause emojis to display in black and white instead of color. If you’re not using Chrome, let us know what browser you are using and also check that browser extensions aren’t interfering.
Looks like that I have experienced this in Chrome while on other browsers works like in the past. Thank you for reaching out!
I followed up with our designers and engineers and they let me know that this is a Windows thing and not a Coda thing, so my guess is that you’re on a Windows machine and not a Mac. It’s likely that a Windows update is forcing the loading of a different icons set based off of unicode emojis.
That’s it! I was using Chrome on a Windows Machine. On Edge and on Safari no problem at all. Thank you
This is looking like a Chrome for Windows bug. We’re checking to see if we can work around it without having it break again when Chrome hopefully fixes it. Sometimes these are tricky when it’s really a bug in another system.