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?

Thanks a lot, the user should know what he was doing anyway.

D17242 should fix this, thanks for the report!

I confirm that the task is indeed created with the subproject tag and visible in its workboard when created.

There's now a grayed out page

your phutil is 3 weeks older than the rest

Should I open a new bug?

Actually there's a bug with this behavior in the workboard, I can reproduce that in a test instance in phacility as well.

I couldn't reproduce this.

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 :)

Reproduced on

Great, this works better, although it is mentioned that "Unstable Method", but it is doing the job. Thank you so much.

wow! the beautiful colors!

Related issue on Travis's GitHub:

(I preemptively set the project back to Needs Information since the followup didn't involve reproduction of the issue on a valid install)

Upstream doesn't support Phabricator installed via third-party images (including Bitnami). You need to reproduce the issue on either a blank Phacility test instance, or by following the Installation Guide and reproducing it there providing it's not an environment issue.

@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.

Having a generated-paths variable in .arcconfig with a similar semantics to the differential.generated-paths server configuration -- something like D11537 a couple of years ago was intended to do -- would be really useful!

OK -- I made a new ec2 instance with the phabricator marketplace image to make the install easier. Updated to the latest stable and could still reproduce this. I don't know why the commit branches are saying that it is branched because I git reset --hard origin/stable on all the branches. I repeat -- this is a 100% fresh machine with the latest stable channel fetched from the phacility repos.

Phrequent is a prototype. We do not accept feature requests for prototypes, see User Guide: Prototype Applications.

1. Create a task named This is a test
2. Search for This is a test, nothing found

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.

This is exceptionally rare, strictly user error (i.e., avoidable by entering your email address correctly), and administrators can force-verify email addresses with bin/accountadmin which offers one way out of this state.

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:

I will use a completely clean build tonight and reproduce this but the code hasn't changed since 2015.

Offhand, these don't look like current / valid versions of Phabricator. They are out of date and installed from somewhere other than our source. Please see Contributing Bug Reports for what we require in a bug report.

No worries. I was like... weird there is a random task in "Phacility", so I removed one, then I saw like 50 more... and stopped.

I think it's useful to keep track of bugs which impact customers

I tagged this with Phacility because a Phacility customer was the original reporter. I think it's useful to keep track of bugs which impact customers, but maybe I should make a different tag?

I can't reproduce this. It's possible that you actually experienced T11165 and misremembered exactly what you'd done, or performed one edit in a tab with the other tab open.

This is by design, and explained in the documentation.

Good catch ! This is a disturbing behavior for the end user though.

This is documented in the userguide.

Weirdly, another server restart fixed this for me.