Cannot execute commands on mobile device browsers

[zynowhere]

Checklist

• [X] I read and understood ASF-ui's Contributing Guidelines
• [X] I also read FAQ
• [X] This is not a question
• [X] This is not ASF problem
• [X] I cleared my cache and localStorage

ASF version

Latest stable release

ASF-ui version

9927878

Bug description

In the command screen, execute the command

Expected behavior

Press Enter after typing the command, execute the command

Actual behavior

The cursor moves to the top, like a new line

Steps to reproduce

No response

Possible reason/solution

In fact, it can be executed in some browsers or with some input methods For example

	Android-Gboard	ios-default
chrome	×	√
safari	/	√
via	√	/

But，use the ENTER NOT NEXT with Unexpected Keyboard or hack keyboard，it always works

It may be a problem with the IPC page, it was made into a form

Can you help us with this bug report?

Somehow, I can test and offer feedback, but can't code

Global ASF.json config file

No response

BotName.json config of all affected bot instances

No response

Additional info

No response

[Aareksio]

https://www.youtube.com/watch?v=jLqTXkFtEH0

I guess we could work around it...

[JLCareglio]

Something new?

[oubeichen]

This issue has been bothering me for years ever since a certain ASF-ui update. Now I can only use ASFBot to execute commands on the Telegram bot.

[JustArchi]

This issue has been bothering me for years ever since a certain ASF-ui update. Now I can only use ASFBot to execute commands on the Telegram bot.

You can always navigate to /swagger and execute the endpoint yourself, you just authorize in top right if you use IPCPassword, then you find the POST /Api/Command endpoint and put the command in the POST body.

ASF-ui is a frontend to ASF API, not a requirement to use it, which is why other solutions work properly with it.

[Abrynos]

While the enter button might be a nice feature, in the meantime you can tap on the > character to the left of the input. This works in chromium based mobile browsers as well.

[oubeichen]

While the enter button might be a nice feature, in the meantime you can tap on the > character to the left of the input. This works in chromium based mobile browsers as well.

Thank you for your reply. I hadn't noticed that character before. However, I think I've identified the cause of the issue and have submitted a Pull Request.

[Abrynos]

However, I think I've identified the cause of the issue and have submitted a Pull Request.

I've seen it. This is why I noticed the issue in the first place. Thank you for that. I'm looking forward to the enter button working as well.