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

Image is missing the restricted exception class in the data #16218

Closed
Mgsy opened this issue Apr 16, 2024 · 1 comment · Fixed by #16275 · 4 remaining pull requests
Closed

Image is missing the restricted exception class in the data #16218

Mgsy opened this issue Apr 16, 2024 · 1 comment · Fixed by #16275 · 4 remaining pull requests
Labels
package:restricted-editing squad:core Issue to be handled by the Core team. support:2 An issue reported by a commercially licensed client. type:bug This issue reports a buggy (incorrect) behavior.

Comments

@Mgsy
Copy link
Member

Mgsy commented Apr 16, 2024

📝 Provide detailed reproduction steps (if any)

  1. Go to the editor with Restricted editing and configuration allowing inserting inline images to the exception fields
  2. Set the following initial data: <span class="restricted-editing-exception">This is example content</span>
  3. Put the caret inside the exception marker
  4. Insert an image
  5. Call editor.getData()

✔️ Expected result

The image markup includes the restricted exception class, so it could be properly recognized during editor initialization

❌ Actual result

The image markup is missing the restricted exception class, so after reloading the editor (or calling editor.setData( editor.getData() )) it's impossible to edit the image.

It is correct in the editing view.


If you'd like to see this fixed sooner, add a 👍 reaction to this post.

@Mgsy Mgsy added type:bug This issue reports a buggy (incorrect) behavior. support:2 An issue reported by a commercially licensed client. package:restricted-editing squad:core Issue to be handled by the Core team. labels Apr 16, 2024
@stevenrai
Copy link

This effectively makes the fix for #15521 unusable. Timeline to resolve this so images can be successfully inserted in to restricted docs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment