You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Selecting the "I am a bot" option on the Edit Profile page should result in a user being displayed as a bot but not marked as a bot internally.
Actual behaviour
When this option is selected, there is no visual "bot" indicator next to the user's name when a user link is clicked on via the timeline. If a user has the "This account is automated" selected, the "bot" indicator correctly displays, but not when the "I am a bot" option is selected.
Steps to reproduce the problem
Set a user to use the "I am a bot" option via the Profile / Appearance page in the settings.
Log out and log back in as another user.
Navigate to the user page for the user used step 1 and notice that the "Bot" indicator that should be in the top section of the right column (near where it says when the user joined) is missing.
Specifications
This was observed in both the latest builds of both Chrome and Firefox
It was found in build v3.2.0+beachcity1.20.0 and the current production build of beach.city (v3.1.2+beachcity1.10.0)
The text was updated successfully, but these errors were encountered:
Expected behaviour
Selecting the "I am a bot" option on the Edit Profile page should result in a user being displayed as a bot but not marked as a bot internally.
Actual behaviour
When this option is selected, there is no visual "bot" indicator next to the user's name when a user link is clicked on via the timeline. If a user has the "This account is automated" selected, the "bot" indicator correctly displays, but not when the "I am a bot" option is selected.
Steps to reproduce the problem
Specifications
This was observed in both the latest builds of both Chrome and Firefox
It was found in build v3.2.0+beachcity1.20.0 and the current production build of beach.city (v3.1.2+beachcity1.10.0)
The text was updated successfully, but these errors were encountered: