Steps to reproduce
- Click on a deep-link to a bot with a
start parameter, such as (this is a real link that you can use to test the issue): https://t.me/fume_bot?start=123 (paste this e.g. into your saved messages so you can click it from there)
- This opens a private chat with the bot, with a "START" button, so click the "START" button
- Now go back and click on the initial link again
Expected behaviour
This time, this should immediately send the start message to the bot with the (unfortunately hidden, but that's a separate issue in both Desktop and app, probably by wrong design) parameter, to which the bot will immediately respond. That is, this second interaction shouldn't show the "START" button again and require to click it. This is how the mobile Telegram app behaves, and there's no reason for the Desktop application to behave differently
Actual behaviour
No matter how many times you have already talked to the bot and/or sent it a /start command, every single time you click on the deep-link, it will display the START button and you'll need to click it in order for the /start command to be sent. This is inconsistent with the mobile app behavior.
One may argue on which of the two behaviors is better. I personally think the mobile behavior makes much more sense. Either way, the two should have the same behavior.
Operating system
Manjaro Linux
Version of Telegram Desktop
4.11.5
Installation source
Other (unofficial) source
Crash ID
No response
Logs
No response
Steps to reproduce
startparameter, such as (this is a real link that you can use to test the issue): https://t.me/fume_bot?start=123 (paste this e.g. into your saved messages so you can click it from there)Expected behaviour
This time, this should immediately send the start message to the bot with the (unfortunately hidden, but that's a separate issue in both Desktop and app, probably by wrong design) parameter, to which the bot will immediately respond. That is, this second interaction shouldn't show the "START" button again and require to click it. This is how the mobile Telegram app behaves, and there's no reason for the Desktop application to behave differently
Actual behaviour
No matter how many times you have already talked to the bot and/or sent it a /start command, every single time you click on the deep-link, it will display the START button and you'll need to click it in order for the /start command to be sent. This is inconsistent with the mobile app behavior.
One may argue on which of the two behaviors is better. I personally think the mobile behavior makes much more sense. Either way, the two should have the same behavior.
Operating system
Manjaro Linux
Version of Telegram Desktop
4.11.5
Installation source
Other (unofficial) source
Crash ID
No response
Logs
No response