Pressing up to edit latest message stopped working

[thany]

Steps to reproduce

1. In a chat view
2. Send a message
3. Press the up-key to edit that message

Outcome

What did you expect?

The most recently sent message goes into edit mode

What happened instead?

Nothing

Operating system

Windows 10 21H2

Application version

Element version: 1.9.5 Olm version: 3.2.3

How did you install the app?

From https://element.io/, and self-updates

Homeserver

matrix.org

Will you send logs?

No

[t3chguy]

Cannot reproduce

Screen.Recording.2021-11-26.at.12.50.52.mov

[dualfade]

This is not working in linux either ( as I just went hunting I found this ).

UP arrow works --
Clicking any of the message popup buttons does not --

Installed --
[0] % yalocs | ag chromium
local/chromium 96.0.4664.45-2

Button press: edit/reply/options/react... Nothing happens.

Thanks.
~!>D

[thany]

It suddenly started working again, but it now manages to jump to edit a message I sent days ago.
Yes, of course, there are newer messages sent after that.

Clicking the edit icon on newer messages works fine.

Honestly, I'm baffled at why it is so difficult to just grab the latest sent message by the current user and throw it in edit mode... How does it decide which message to edit??

[t3chguy]

Related #16402

[thany]

Maybe, #16402 would merely confirm that it's throwing the wrong message into edit mode...

[clusidc]

Got the same problem with the Desktop client. (Element 1.9.7 and OLM 3.2.8)
Arrow key up sometimes does not do anything. Sometimes it opens a random old message for editing. After a fresh restart (close element from the taskbar) it works again.

The issue happens sporadically, although it might have to do something with the first start after windows boot as the issue only arised (as i remember) one time per day.

[thany]

After a fresh restart (close element from the taskbar) it works again.

Not for me. I haven't seen it working, not once, since I first noticed this issue. And I make a lot of typos, and I'm OCD enough to also want to correct them, so I'm already on the cusp of demanding some bloody priority.

The issue happens sporadically, although it might have to do something with the first start after windows boot as the issue only arised (as i remember) one time per day.

I'm happy for you.

But as for the devs: why is it so hard to:

1. Find the most recent post by the current user
2. Throw it in edit mode

Surely, it can't be more complicated than that. I'm very curious what the logic is currently. How does it find a random older message to be the "most recent" and viable for editing?

[thany]

This is still happening on the latest version:

Element version: 1.9.9
Olm version: 3.2.8

Not trying to be impatient. It's just a really obvious bug and this not working properly is quite annoying when it selects the wrong (or no) message again. It's what I'd call "low hanging fruit".