-
Notifications
You must be signed in to change notification settings - Fork 11.1k
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
4.7.0 regression: edit button not displayed in the first minute after sending a new message #25478
Comments
Confirm that issue on 4.7.0! |
Same on 4.7.1 |
Same for me. |
Same for me - if the "block edit after ..." option is set Workaround: set " Block Message Editing After (n) Minutes" Option to 0 (to disable it) |
Still there on 4.8.1 |
same problem like @saschafoerster mentioned before |
@debdutdeb @sampaiodiego This is quite "breaking" for most of our users, since they've used the edit button mostly. Also we've set a limit to disable editing after one minute - so for us the button is gone completely... This should be an easy and fast fix - please take a look at it. |
Hey, thanks for the ping. I'll look into it tonight. In the meantime if someone would like to open a PR, we'll pf course accept that too. |
See #25724 |
Description:
In rooms where editing is enabled and limited in time, the client does not display the edit button in the first minute after sending.
Editing by pressing the up arrow key or with other clients still work as expected. It's only a UI issue.
I think I tracked this down in messageActionDefault.ts:
where
currentTsDiff
is the difference in minutes between the current time and the message timestamp.During the first minute,
currentTsDiff
is0
hence!!currentTsDiff
isfalse
and the edit button is not displayed.This was introduced here.
Steps to reproduce:
Expected behavior:
The edit button is available as soon as the message is sent.
Actual behavior:
The edit button only appears one minute later.
Server Setup Information:
Client Setup Information
Additional context
Relevant logs:
The text was updated successfully, but these errors were encountered: