tdesktop icon indicating copy to clipboard operation
tdesktop copied to clipboard

Keyboard focus in sidebar can't be returned from chat

Open Remu-rin opened this issue 2 years ago • 10 comments

Steps to reproduce

  1. Open some chat and sidebar, choose e.g. Photos
  2. Try page down/page up on keyboard
  3. Click on chat (e.g. share button, text, open image)
  4. Try to return focus to sidebar to continue scroll with keyboard

Expected behaviour

There should be a way to return keyboard focus to sidebar without loosing state (e.g. you scrolled down several weeks/months).

Actual behaviour

There is no way to return keyboard focus to sidebar without loosing scroll state. Seems that keyboard focus is changed to sidebar only when you click to open category (Photos, files, etc). If you lose keyboard focus to something else, nothing can return it back to sidebar: clicks in different places, opening photo, selecting items, forwarding. The only way to return keyboard focus is to exit and enter category again, but you lose state you were in and need to scroll down again. And without #17245 it's frustrating.

Operating system

Windows 10

Version of Telegram Desktop

3.6.1

Installation source

Static binary from official website

Logs

No response

Remu-rin avatar Mar 18 '22 14:03 Remu-rin

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 Sep 15 '22 02:09 github-actions[bot]

Still relevant.

Remu-rin avatar Sep 15 '22 09:09 Remu-rin

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 Mar 16 '23 01:03 github-actions[bot]

Still relevant.

Remu-rin avatar Mar 17 '23 00:03 Remu-rin

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 Sep 14 '23 01:09 github-actions[bot]

Still relevant.

Remu-rin avatar Sep 14 '23 10:09 Remu-rin

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 Mar 14 '24 01:03 github-actions[bot]

Still relevant.

Remu-rin avatar Mar 14 '24 09:03 Remu-rin