-
-
Notifications
You must be signed in to change notification settings - Fork 213
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
not able to use <pre><code> syntax in tinymce area #4058
Comments
Tested with simplemde plugin by lonalore that have already this script supported. Before 3 years ago it worked. Now the same result: |
@Moc change label to question, this is probably the intention. I don't need this anymore. |
@Moc I believe this is the parser error we saw on e107.org. It should normally be fixed now. |
It is not. I tried it after that fix. You don't see it normally because HTML entities are displayed correctly, but you can't use it for js |
TinyMce also seems to be adding |
btw.
I think you mean:
TinyMce Source:
Rendered Result:See: https://e107.org/developer-manual/getting-started/hello-world |
@CaMer0n
|
@Jimmi08 I tried what you suggested: TinyMce Source (before saving and after saving/re-editing): |
It was adding spans after inserting text, before saving itself. I had to switch to source code, insert that text there, switch back, and then use preformatted code button. Now I can't reproduce it. I don't understand. Closing. |
@Jimmi08 Maybe you copy/pasted from elsewhere? (so it pasted additional tags) |
Visual Code editor. |
Bug Description
For highlight.js I need to use code
<pre><code> </pre></code>
in tinymce areaNow it's changed to
<pre><code>pre2</code></pre>
by e107.
I already know that
<pre>
and<code>
tags have exceptions and they should not be converted to HTML entities, but if you combine them, this happens
How to Reproduce
Steps to reproduce the behavior:
<code>
tags, and then button for<pre>
tagsExpected Behavior
tag shouldn't be converted to HTML entities
e107 Version
PHP Version
The text was updated successfully, but these errors were encountered: