Like "meow meow meoww".

She sounded really hungry earlier.

There is no relevant "explain why" link because there is no transaction for someone added a commit: rPPfd5a74ad3fa1 on D19839 or someone added a differential revision: D19839 on rPPfd5a74ad3fa1.

Does clicking "Explain Why" explain why?

At HEAD, the messages are folded individually.

In T7447#110475, @scohen wrote:

I don't know @epriestley, I found it really confusing to have my comment on a different line entirely.

The comments persist even when the code that you're talking about is deleted.

You can vote for multiple options, and @cburroughs has.

As a reviewer, I think bringing "Done" comments forward is quite important: it makes it a lot easier for me to verify that they're really done. This is the #1 benefit I've reaped from this feature so far.

• T7999 suggested something along the lines of the "minimal UI".
• Via IRC, "(btw, the 'moving comments over' feature has been a big hit here.)"
• Via Twitter, our heroism was recognized.

(Including discussion of the possibility of summarizing, hiding, etc., older inlines.)

I'm going to merge this into T7447, which has some ongoing discussion about this feature.

We don't currently plan to implement this. I'm going to merge this into T4207, which discusses one of the major technical issues (subtasks are a graph, not a tree).

One reason to show old inlines even when they are marked "Done" is that the reviewer who added the inline may want to verify that it is actually done when they look at the updated diff.

• Implement supportsSearch() in your Editor and return true;.
• Implement a SearchIndexer, like ManiphestSearchIndexer.
• You can test the indexer for non-crashiness easily with bin/search index E123.
• To test with the actual global search in the UI, you need to:
  • be running the daemons; and
  • restart the daemons after you make any changes to your SearchIndexer.

I hear CSS4 has white-space: nowrap-first-space-but-wrap-the-rest-normally;.

• Add viewPolicy and editPolicy fields to the object.
• Add these columns in .sql files.

Particularly after T3670, these might get a lot longer than they are right now in reasonable cases.

Particularly after T3670, these might get a lot longer than they are right now in reasonable cases.

Personally, I felt that (at least in the case of my screenshot) it would be better to push the entire tag to the second line.

When I first read the title of this ticket, I thought that you were going to add gamification.

They could, yeah. We'd probably need a "List all users with badge X" UI to avoid losing functionality, but that seems pretty reasonable.

Could badges be used for policies? For example, Blessed Committers could be replaced with a badge potentially. This would (at least partially) solve T5602.

Yep. I personally intend to create hundreds of badges to award myself once this is built.

Here's a rough sketch of this. This is a ton of work and should be split into like 300 revisions. See T6526#107028 for product details.

If browsers are carrying state across reloads, maybe we just need to initialize JX.Quicksand.id to window.history.state || 0 (and throw away that object patch).

RTL doesn't flip scrollbars for me on that fiddle:

DarkConsole shares the same scrollbar with the rest of the page, but the chat column has its own scrollbar, and needs to scroll independently of the main page content.

Disabling the pretty scrollbar alone wouldn't fix this without also removing the container frame which enables the chat column to exist.

We can possibly fake this with Quickling in the common case once we summon the courage to enable it without the column open.

Presumably resolved.

Nice, I like that.

I think invitees are complex enough that we probably don't want to use edges to store them. Edges are good for simple relationships (like a user subscribing to an object) but not as good for more complex relationships. Invitees are likely to have a lot of state eventually (required/optional, invited/attending/declined, maybe annotations like "Speaker" for a talk, "Co-Host" for a party, or "Bringing Salad" vs "Bringing Desert" for a potluck, maybe tracking who invited you, and so on).

From elsewhere, I think it's so that they're visible in dialogs (like "Edit Task" from a workboard with a custom date field).

Yeah, this should be fixed at HEAD for most workflows, see:

escalate from that to any other account

Are you at HEAD?

No -- you point Phabricator at the new LDAP server by using a compromised administrative account and going to Auth → LDAP and changing ldap.mycompany.com to ldap.evil.com.

Yep, thanks!

See T4213 for discussion of themes/skinning, and an explanation of why we don't expose CSS/HTML as an API.

I think our use cases are pretty much the same, the documents are just laid out a bit differently.

I do think the weight and blackness of the subheadings can overwhelm headings a bit, for instance on the Changelog: