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

Code Block with '&' (ampersand) does not work as expected #6563

Closed
itsopi opened this issue Apr 6, 2020 · 3 comments
Closed

Code Block with '&' (ampersand) does not work as expected #6563

itsopi opened this issue Apr 6, 2020 · 3 comments
Labels
resolution:duplicate This issue is a duplicate of another issue and was merged into it. type:bug This issue reports a buggy (incorrect) behavior.

Comments

@itsopi
Copy link

itsopi commented Apr 6, 2020

πŸ“ Provide detailed reproduction steps (if any)

  1. Add 'codeBlock' plugin.
  2. Set this data - <pre><code class="plaintext hljs">&</code></pre>

βœ”οΈ Expected result

I expect to see '&'

❌ Actual result

I see '&amp;' - escaped ampersand, which is unexpected.

πŸ“ƒ Other details

This occurs only when the ampersand is in code block.

  • Browser: Does not matter
  • OS: Does not matter
  • CKEditor version: Latest
  • Installed CKEditor plugins: Does not matter but codeBlock is mandatory

If you'd like to see this fixed sooner, add a πŸ‘ reaction to this post.

@itsopi itsopi added the type:bug This issue reports a buggy (incorrect) behavior. label Apr 6, 2020
@Mgsy
Copy link
Member

Mgsy commented Apr 6, 2020

Hi, we're aware of this issue. Please, see more details here.

@Mgsy Mgsy closed this as completed Apr 6, 2020
@Mgsy Mgsy added the resolution:duplicate This issue is a duplicate of another issue and was merged into it. label Apr 6, 2020
@itsopi
Copy link
Author

itsopi commented Apr 9, 2020

@Mgsy Sorry, but is there any quick fix (workaround) for this issue?

@Mgsy
Copy link
Member

Mgsy commented Apr 9, 2020

@Mgsy Sorry, but is there any quick fix (workaround) for this issue?

It's hard to say because we didn't investigate this issue. For sure it's an important problem and we'd like to fix it, however, our capabilities limit us, so we're focused on issues with higher priorities. I'm afraid that the only solution I can recommend is trying to debug it on your own, as we can't promise any date for fixing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resolution:duplicate This issue is a duplicate of another issue and was merged into it. type:bug This issue reports a buggy (incorrect) behavior.
Projects
None yet
Development

No branches or pull requests

2 participants