Maybe vertical-align: top? Or display: inline-flex?

FYI Chrome/Windows after the change (extra whitespace added?)

I believe we see the same issue in our environment, but I didn't think much of it/rule out actual problems with our setup and just restarted the daemons the first few times it's happened.

This would be useful for us as well, we want to migrate from using local authentication (which was very easy to setup when initially bringing up our server) to using LDAP authentication. We had most/all of our users create accounts using their LDAP username but using local authentication, but really we should have set up LDAP from the beginning.

It's possible T10872 is also related/is a duplicate.

D17245 returned everything to normal, and can confirm windows 10 has fancy color Emoji 👍

What it looked like before

(On windows/chrome) this seems to have changed the overall font for many Phabricator elements to a slightly different font that in my mind is just a little less readable. Apparently re-ordering 'Segoe UI Web Regular', 'Segoe UI Symbol' in front of the regular Segoe UI changes how the font looks.

Is anyone encountering this on a https:// protocol install? I was plagued by this issue for a while and switched to https:// and it seemingly disappeared. Although I can't reproduce today on the http:// protocol either.

I'm 100% fine with that, I have no idea if there's some ugly interactions here, just wanted to chime in that we were affected too. The average skill level of users interacting with Phabricator makes the workarounds not a big deal in general (although I think an administrator can lock users out of the necessary IE settings to turn off compatibility mode)

Yeah, we're also affected by this... it's mostly a non-issue since no one really uses IE but IE11 renders incorrectly in IE7 compatibility mode since the Phabricator server is determined to be in the intranet domain.

This would be really nice to see, as we do post-commit code review with Audit and we semi-frequently encounter commits that have near-100% changes due to white space as someone hits an auto-formatter or changes svn:eol-style to match convention and doesn't split this out into separate commits.

Awesome, thanks! Updated to latest and confirmed.

Yeah, cut-off would also be acceptable (although I like wrapping slightly better). It might motivate users to pick shorter names but there's not even a lot of space for reasonable names when combined with milestones/subprojects like:

+1 for this from me, internally for us getting a new gmail account (provides IMAP/POP access) is relatively easy, but getting necessary MX records/mail routing/etc... for a local copy of sendmail is significantly more difficult.

I'll chime in with my 2c as well, the new "Set Sail For Adventure" button in Maniphest was also a bit confusing to me and another member of my team, and we're usually fans of the flavor and have pushed to keep it instead of switching over to serious_business.

That sounds like a good solution, I hadn't looked at the information on mail commands (since our installation can't get incoming mail).