-
Notifications
You must be signed in to change notification settings - Fork 75
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
Typing in the CKEditor 5 is ridiculously slow #3584
Comments
Hi escix, this can happen for really long emails, and to our understanding especially if there are a lot of nested citations. "Normal" sized emails should not have this problem, though (I tested one with 15000 characters right now again, to be able to give a number, which, on my pc didn't have any issues). CK5 is a topic still in various places in any case, unfortunately we had to make the change, because CK4 is not updated anymore. CK5 was completely rewritten and has some drawbacks, which we are not totally happy with, ourselves. Currently for this specific issue I can only say, that we are aware, and that it has a relatively high priority, but that we do not know of an "easy fix". Best regards, Sven |
Hi Sven, |
internally, indicate boolean attributes by setting it to $Types::Serialised::true. Require the Perl distribution Types::Serialiser. This is no new requirement and JSON::XS already required that module.
internally, indicate boolean attributes by setting it to $Types::Serialised::true. Require the Perl distribution Types::Serialiser. This is no new requirement and JSON::XS already required that module.
The referenced commits actually belong to #3583 . Sorry for messing up. |
Unfortunately we also suffer from this issue. There was now lag or slow typing with the older CKEditor 4, but version 5 seems ridiciously slow even with small emails. We use an embedded logo for our corporate signature, but this wasn't changed since the migration to OTOBO 11.x. I have already tried to further limit the lines of the original quoted request, but we didn't notice a big difference yet. |
I commented out this section and it solved the issue. But not sure if there is any other issue pop up due to this. File: var/httpd/htdocs/js/Core.UI.RichTextEditor.js `
` |
the data copying seems to cause a huge chunk of the lag, so i moved this into the timeout. i also increased timeout to half a second as that should be sufficient.
that was a great find, thank you. i adapted the code you commented out and the fix should arrive soonish. |
Just a quick feedback: we are using the quick-fix suggested by @escix since last friday and it's working quite well. No more lags or slow-typing. 👍 |
works for us as well, thank you |
the data copying seems to cause a huge chunk of the lag, so i moved this into the timeout. i also increased timeout to half a second as that should be sufficient.
the data copying seems to cause a huge chunk of the lag, so i moved this into the timeout. i also increased timeout to half a second as that should be sufficient.
the data copying seems to cause a huge chunk of the lag, so i moved this into the timeout. i also increased timeout to half a second as that should be sufficient.
the data copying seems to cause a huge chunk of the lag, so i moved this into the timeout. i also increased timeout to half a second as that should be sufficient.
the data copying seems to cause a huge chunk of the lag, so i moved this into the timeout. i also increased timeout to half a second as that should be sufficient.
the data copying seems to cause a huge chunk of the lag, so i moved this into the timeout. i also increased timeout to half a second as that should be sufficient.
the data copying seems to cause a huge chunk of the lag, so i moved this into the timeout. i also increased timeout to half a second as that should be sufficient.
the data copying seems to cause a huge chunk of the lag, so i moved this into the timeout. i also increased timeout to half a second as that should be sufficient.
Hi Team,
When I reply to email tickets, it takes long time for the typing to display on the screen. Like 10 to 20 seconds.
Which makes it hard to know if there's any spelling mistakes while typing.
The text was updated successfully, but these errors were encountered: