Page MenuHomePhabricator

Active Bot usernames are struckout in search suggestions, like disabled accounts
Open, LowestPublic

Description

If I search for any active bot name, the autocomplete list shows it as struckout and faded, which is the same formatting that is applied to a useraccount that is "disabled" (i.e. blocked).
This is confusing.

Event Timeline

Quiddity created this task.Jul 14 2019, 1:59 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 14 2019, 1:59 AM
Quiddity updated the task description. (Show Details)Jul 14 2019, 1:59 AM
Peachey88 edited projects, added Phabricator (Upstream); removed Phabricator.EditedJul 14 2019, 2:27 AM
Peachey88 added a subscriber: Peachey88.

Confirmed its happening upstream on secure.phabricator.com as well.

Reported upstream in their discourse environment.

Restricted Application added a project: Upstream. · View Herald TranscriptJul 14 2019, 2:27 AM
Peachey88 moved this task from Backlog to Reported Upstream on the Upstream board.Jul 14 2019, 2:34 AM
Aklapper renamed this task from Bot usernames are struckout in search suggestions to Active Bot usernames are struckout in search suggestions, like disabled accounts.Jul 14 2019, 10:36 AM
Aklapper triaged this task as Lowest priority.

Looks like a valid design decisions to me: Why do you search for a non-human user with which you won't be able to interact?

epriestley added a subscriber: epriestley.

I've filed this upstream in https://secure.phabricator.com/T13340. See that task for more details.

Although part of the goal here is to move these results to the bottom of the list, the strikethru rendering in global results and autosuggest results is a side effect of the internals accomplishing this in a slightly messy way, and I think unnecessarily confusing.

The intent is to: sort these results to the bottom; and render them in a way that makes the fact that the result is special in some way (here, the user account is a "Bot" account) clear to the user. The normal tokenizer accomplishes both these goals:

...but the global typeahead and the inline autosuggest render "closed" attributes differently, in a way that leads to visually conflating "disabled" and "bot":

Thank you @Peachey88 and @epriestley !

Looks like a valid design decisions to me: Why do you search for a non-human user with which you won't be able to interact?

I started typing the name of a bot because I was searching for tasks that involved it.
Then I got the autocompleted result, and initially assumed it was an Archived Tag (because those also display with strikeout and faded).
Finally I clicked through and realized it was a userprofile of an active bot.
(Yes, I should've mentioned all that in my description!).

However, even if someone was trying to find a bot, any active bot should have contact-info for the bot-owner in the userprofile description; hence someone might be discouraged by the formatting of that search autocomplete and not click through.