-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Voice-to-text premium button bugs seeking in voice message #26162
Comments
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! |
Probably still relevant. |
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! |
Probably still relevant. |
Fixed (checked 5.2.3). |
Steps to reproduce
Expected behaviour
Seeking should work as without premium
Actual behaviour
Seeking is bugged because of premium button presence. When you seek to certain moment with mouse, actually it goes before that position (the longer the voice, the bigger the jump will be, for 15-min voice it jumps 2 minutes back).
Visible process is: when user does left click press, it shows one (correct?) seek position, e.g. 0:23, then when user releases left click it jumps back e.g. to 0:19 (window layout is made compact for recording purposes, but the bug reproduces in fullscreen too):
2023-04-11.16-12-28.mp4
Operating system
Kubuntu 22.04, KDE
Version of Telegram Desktop
4.7.1
Installation source
Static binary from official website
Crash ID
No response
Logs
No response
The text was updated successfully, but these errors were encountered: