In Chrome (Version 64.0.3282.140 (Official Build) (64-bit)) the inline comment buttons have a hot-spot for tooltips to party

I might make some more tweaks to the UI, but this looks like it's in better shape now.

A similar issue occurs when the "Visible To" control wraps with spaces enabled. To reproduce this...

...

Here's the fate of the various issues discussed here:

We should log all the paths used to get to each page, and then show all of them in a big combo box, and when you select one, update your browser's history to match that path!

Probably a bad idea but maybe I'll revisit this at some point.

Maybe T6038.

At least for now, copy/paste is keeping these largely consistent.

This sounds similar to "Customize Fields Shown In List View", except that it allows per-view customization (And a DSL for "view" instead of property on the Field, as in T418).

This originally came up in the context of PHI706, which asks for a "Query for all tasks mentioned in wiki page X" feature, although the actual feature request there is more involved and this would only be an approximate approach.

Yeah, I'm looking at here, assuming it's ahead of last release.

Just to make sure we're talking about the same thing, that feedback is true even of the version at HEAD (blue/grey/orange) vs the version that originally shipped (green/grey/red)?

You could maybe leave the element off unless it is a larger change. I think my concern here is seeing it on every revision becomes something extra I have to mentally process, but if the intent is to either help show small changes, or large changes, it could just be visible in those edge cases. In those cases at least, the element provides context as to why it's shown at all vs. all the time?

I think there's possibly at least some argument that this element could serve noble goals:

I feel your instincts are correct, this information isn't useful in a list form and shouldn't be included. You could make the argument to include it in a hovercard, or bring it into the header on the diff page, and I think those are both fine. Outside of that this seems mostly geared towards avoiding code review, a practice I don't think is well aligned with the overall product goals.

D19384 cleans this up a little bit and mostly fixes the "phantom unread notification" issue in T8953.

The "Notification server not enabled" text should also link to the Aphlict documentation or something.

(These are in the menu.)

This feels a bit like a return to the era of "epriestley design", but I think it's an improvement overall:

This never got fleshed out into an actionable plan, see T13077 for the next planned phase here.

In Chrome (Version 64.0.3282.140 (Official Build) (64-bit)) the inline comment buttons have a hot-spot for tooltips to party

I'd probably lean towards just increasing the padding under the text to make sure the field is clearly separate from the one below it.

If that suggestion looks valid, I'd be happy to implement it (I'm thinking "Add RemarkupCaption into Control, render above actual field", and maybe "migrate Caption field to use that too").

The bulk of the work here is finished, no plans on approaching a re-design for diffusion home this pass.

Closing out, thanks for all the feedback. Will follow up with individual tasks not addressed.

New search shipping with last week's stable release.

I could totally be imagining that.

it shouldn't have changed, just now a border. I don't know how to update the colors since it some sort of strange math only engineers know.

If it matters, my laptop is actually 13" with 1080, but it's only because the store said they don't have a smaller version.

Going to pass on this, not really worth time.