In T12516#218475, @rabahmeradi wrote:

Is this really the new 'Needs review' icon or I have problem with fonts?

Is this really the new 'Needs review' icon or I have problem with fonts?

Happy to accept a patch for these!

Feel free to submit patches for these!

is srs bsness mode taking over? i'm in a panic :[

THANKS FOR RUINING THE JOKE EVERYONE

I think we could even default it to "fancy mode" without a setting, at least to start with. I'm not sure anyone will want to access the plain text mode with enough frequency that we need it to be sticky.

We've started using countdowns on our dashboard as well and it's a little distracting/stressful to have that keep updating. It would be cool to have it fully customizable but the compromise plan you posted about would work well for us too.

They support a set of 12 currently.

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.

(I renamed the "Up for Grabs" column to "Ready", and kicked this out since it doesn't have detailed technical instructions that a new contributor could follow like the other tasks in that column do.)

T12000 isn't really a duplicate. It's more of an enhancement for today's tokens. Of course, it'd be useful for this eventually, too, but that's tangential.

This search UI also needs to be updated:

My only (mild) concern with this is that object types may become slightly ambiguous in some contexts: currently, icons are (at least mostly) unique across object types. A tag icon or a briefcase icon is always a project. A calendar icon or a cocktail glass is always an event.

• Prototype applications must be enabled.
• security.outbound-blacklist must not blacklist the target server (build servers may be on an internal network and on the default blacklist).
• The link protocol must be "http" or "https".
• You must not have exceeded your fetch quota for the last hour.
• You must have file storage configured.
• The image MIME type must be part of files.image-mime-types and files.viewable-mime-types.
• The Phabricator server must be able to make outbound requests on the network.

In T4190#199608, @epriestley wrote:

(But note that it's cached for a trillion years, so it won't work for build status.)

Does the {img } thing work yet? I've been trying to use it locally but have not been able to get it to actually show an image. This would be super useful for us to be able to show the build status on a remarkup page (like the README.MD of our repo, for example). Thanks.

Just encountered this problem on my setup too.

(I'll follow up on this once I have a chance to bang on it a bit, but I want to try to finish up the RRULE stuff while it's still somewhat fresh in my mind.)

I did order an iPhone 7 plus, so I'll have a better understanding if 2x is actually noticeably bad.

This isn't like something I'm looking for immediately, btw. Just like, next time I have to make 50 images.

I'm also not sure if we can use SVG as a data: URL in CSS. It probably should work, but if it doesn't we'll have to rasterize (and, I guess, serve 5+ different sizes to every user).

Alright -- we can have bin/celerity map rasterize SVG into arbitrary sizes if I'm not comfortable serving SVG directly from Celerity.

I'd like to generate 1 image and have them work 1x, 2x, 3x, etc or any size I need. I can't think of any other long term solution.

• Create a badge.
• Award it to a user.
• Visit their profile page.
• On the profile page, the badge title should link to the badge detail page (currently: no way to get to the badge detail page).

I'm not really sure this is actually useful given that every method is now named <application>.whatever and you can search by substring.

(That will give us slightly bad scale-downs on 1X screens, but I bet they're not worse than scaling down an SVG would be.)

I think we can just do 2x in all cases for these, if that's reasonable?

fwiw, I want to convert all bitmaps to SVG if possible, so we can skip building 1x and 2x images.

Don't know if D16178 is worth comandeering? But feel free.

This one is a little scattered, so let me know where I can fill in any gaps. Most of the details are in D16178.