[Bug] 2.27.3 - Start Comms message, try to swipe to scroll history, sends incomplete message

I'd been wondering why another agent kept on sending messages simply tagging my agent name, now I think I know.

  1. Tap an agent name in comm, and select 'Send message'
  2. Don't type anything (but this likely happens if you do as well)
  3. Try to swipe up in the chat history you can see behind the chat input
  4. It will send the current state of the message, which in this scenario is the @agentname and a space.
  5. Curse the bug making you look stupid on comms.

Expected behaviour would be the chat input being closed without sending the draft message, and then preferably re-opening in the same state if you tap the keyboard icon, restoring the partial message.

Tagged:

Comments

  • starwortstarwort ✭✭✭

    I think text input in general is a bit messed up in the Prime ui.

  • jsylvisjsylvis ✭✭✭

    Yes. Everything about text input in prime is frustrating.

    In Redacted, you didn't get some bogus floating text pseudo-input tied to the keyboard. It behaved more like a true text box on a web page or form.

  • Still present in 2.30.2

  • TRIBBLE2331TRIBBLE2331 ✭✭✭
    edited September 4

    I guess that it doesn’t save inputs when you close out of the comm in prime. Not sure if this is a bug or an oversight.

  • It's not just that. It's that it's choosing to send what was in the input buffer just because you swipe above/behind it, nowhere near the send button.

    2.30.2 changelog claims that it has in fact fixed the saving of the buffer.

Sign In or Register to comment.