Skip to content
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

fix: avoid null on init and destroy the editor too fast makes the DOM is not loaded #1541

Merged
merged 1 commit into from
Nov 4, 2022

Conversation

ces-binhtran
Copy link
Contributor

Related ticket: https://issues.liferay.com/browse/LPS-166754
The root cause is when switch too fast between the cards the editor DOM objects are not loaded, so it could be null on core.js
then the editor is failed to destroy while all the listeners are removed. When the destroy() method is invoked again it gets null when accessing the length of event handlers EditableRichTextFragmentProcessor.es.js

@ces-binhtran ces-binhtran changed the title fix: avoid null on init and destroy the editor so fast that the DOM is not loaded fix: avoid null on init and destroy the editor too fast makes the DOM is not loaded Oct 26, 2022
@dsanz dsanz merged commit 6628d94 into liferay:master Nov 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants