[Bug]: Markdown Autosave not firing properly

[makakken]

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

When working on a Markdown Document in Nextcloud via Webbrowser, the File does not get autosaved for around 60 seconds. Since this behavior wasn't there 2 weeks ago, i believe it's a bug.

Steps to reproduce

1. create a new markdown document
2. open it and edit it in the webbrowser (Web Editor inside NExtcloud)
3. Count the seconds till the document gets saved... (around 40 to 60)
4. type again some characters (autosave timer restarts)
5. close the document immediately
6. reopen the document, your last changes are not save

Expected behavior

every time i close the document, i expect the changes to get saved properly.

Nextcloud Server version

28

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

i've tested this on an instance hosted at datenkollektiv.net and another one storage-share@hetzner. in both cases this was reproducible.

[carolyna]

We are seeing the same issue on version 29.05 just after upgrading from 25

[joshtrichards]

Likely #6280 and fixed in upcoming maintenance releases.

[mejo-]

Yes, indeed. Should already be fixed in 29.0.6, and should as well be fixed with the upcoming 28.0.10 release next week.