tdesktop icon indicating copy to clipboard operation
tdesktop copied to clipboard

Removed Users: "removed by": when admin name too long and truncated, it can't be expanded

Open php4fan opened this issue 2 years ago • 6 comments

Steps to reproduce

  1. In a group where you are admin, go to Manage Group -> Permissions -> Removed users
  2. If some user has been removed by an admin whose full name is too long to display, you get this:

image

Expected behaviour

When some text is truncated with an ellipsis because it's too long to be displayed in its entirety, there MUST ALWAYS be a way to expand it and see it whole. For example, by clicking on it, or on the three dots, or by just hovering over it with the mouse cursor (with care that there's an alternative on touch-screen devices), etc.

In this case it's the name of the administrator that banned the user. I get that it's truncated with an ellipsis because it's too long, but there must be a way to expand it.

Actual behaviour

There's no way to expand it. Hovering over it does nothing. Clicking on it shows a popup with profile information about the user (username, picture and such), but no information about the user's ban/removal.

Operating system

Manjaro Linux

Version of Telegram Desktop

4.11.5

Installation source

Other (unofficial) source

Crash ID

No response

Logs

No response

php4fan avatar Nov 14 '23 16:11 php4fan

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

github-actions[bot] avatar May 13 '24 01:05 github-actions[bot]

Again, the stupid bot. That no progress has been made on an issue is not a reason for closing it.

php4fan avatar May 13 '24 15:05 php4fan

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

github-actions[bot] avatar Nov 10 '24 02:11 github-actions[bot]

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

github-actions[bot] avatar May 11 '25 02:05 github-actions[bot]

I can't test anymore because the bot whose name was on the screenshots has since been renamed to a shorter name, but I'm pretty sure the issue still exists.

And again, closing issues because of lack of activity, especially when there's been no activity ever on the developers' side, is idiotic.

php4fan avatar May 11 '25 08:05 php4fan

And again, closing issues because of lack of activity, especially when there's been no activity ever on the developers' side, is idiotic.

It's not the 1st, 2nd, 10th, 100th time preston fixes some issues and forgets to close related issue.

Aokromes avatar May 11 '25 09:05 Aokromes

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

github-actions[bot] avatar Nov 09 '25 02:11 github-actions[bot]

Issue still exists

php4fan avatar Nov 09 '25 08:11 php4fan