This is a brute force approach to support "context blocks" without taking any steps backwards (i.e., it supports older transactions and newer, modular transactions), but it feels like this is a lot of steps sideways and this change would be far better if it took a nuanced approach through T12921.

• T12921 is adjacent to mail rendering.
• T13439 mentioned the hovercard summary text.

D21574 implements the hovercard and summary length changes.

I think (?) this was pretty much resolved by the last round of changes. See T13291 for some followups.

PHI1224 describes a somewhat-adjacent situation: an install would like a way for external automated tooling to reference source files and generate editor links for them.

I don't currently plan to do this. At a bare minimum, T5474 may moot it.

This is also extremely silly, but I sometimes do it because I'm dumb and have muscle-memory for ⌘+1+⇥+⌘+V+⏎: searching for an object URL doesn't jump you to that object URL, but you probably meant to put it in the other box.

Yeah, if you know what information you want.

Tasks, projects, owners packages.

Pick three and I'll spruce them up today/tomorrow.

I'd just redo them on a case by case basic. Too many variables.

@chad, a lot of this is probably ultimately design -- how much passion do you feel for hovercards? The infrastructure is in good shape and I can add the "context hint" piece pretty easily if we want to look at that. Not sure if this is a bigger/more complicated project that you don't want to touch for the moment or whatever, though.

Per the latest update in D17502, this remains involved.

This actually seems a little difficult to fix...maybe just make it truncate with an ellipsis?

heh nice. And I didn't even have to cheat by using U+00A0.

@20after4 😆