fix: avoid null on init and destroy the editor too fast makes the DOM is not loaded #1541
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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