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

LPD-45795 Check element exists #218

Merged
merged 2 commits into from
Jan 13, 2025

Conversation

fortunatomaldonado
Copy link
Member

https://liferay.atlassian.net/browse/LPD-45795

When an image tag is surrounded by several span tags, CKEditor cannot find the widget element the image belongs too and causes an error.

In order to prevent this, we need to check if the element exists before continuing.

Please let me know if there are any questions or comments about this.
Thank you!

Copy link
Member

@bryceosterhaus bryceosterhaus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes to check element seem fine to me. All of the other changes seem odd, the ones that change all the hashes. But I'm also unfamiliar with ckeditor updates. maybe @markocikos can confirm this is all good

Copy link
Member

@markocikos markocikos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fortunatomaldonado LGTM! ✨

@bryceosterhaus The hash changes are output of automatic rebuild of ckeditor from dev to production minified version. @fortunatomaldonado it's not wrong, but we don't need to do this on every PR. It can be done once, as a part of release.

Speaking of release, @fortunatomaldonado do you still have permission issues when making a release?

@markocikos markocikos merged commit ddfd2cb into liferay:master Jan 13, 2025
1 check failed
markocikos added a commit to markocikos/liferay-ckeditor that referenced this pull request Jan 13, 2025
…795"

This reverts commit ddfd2cb, reversing
changes made to 65d7c6c.
@markocikos
Copy link
Member

@fortunatomaldonado This time you don't have to do the release, I'll do it to after fix for LPP-57356

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.

3 participants