When creating a codeblock element and select "plain text," any special characters are encoded if they are wrapped in quotation marks. Most notably, the ampersand symbol (&) will be outputted as & even though "Plain Text" was selected.
Hello there, @Christopher Zack !
As I understand, special characters are escaped inside the Codeblock Macro even though you selected Plain Text as format.
With this behavior in mind, I tried to replicate the issue locally. I was ultimately unable to. Here is a screen capture of my attempt:
Since I was unable to replicate, I would like to take a deeper look into this behavior with you. Here are a few questions:
- Is this happening regardless of browser being used?
- Is this issue affecting all Codeblock macros you placed?
- Are you typing in the special characters or are you pasting them from somewhere else?
Looking forward to your reply, Christopher!
Hi Diego, here is an example to replicate this issue from. Doesn't seem to exclusively be ampersands inside quotation marks as something else is in play here but on publish (and preview), the ampersand becomes encoded:
<!-- Facebook Pixel Code -->
<script>
!function(f,b,e,v,n,t,s){if(f.fbq)return;n=f.fbq=function(){n.callMethod?
n.callMethod.apply(n,arguments):n.queue.push(arguments)};if(!f._fbq)f._fbq=n;
n.push=n;n.loaded=!0;n.version='2.0';n.queue=[];t=b.createElement(e);t.async=!0;
t.src=v;s=b.getElementsByTagName(e)[0];s.parentNode.insertBefore(t,s)}(window,
document,'script','//connect.facebook.net/en_US/fbevents.js');
fbq('init', '123456789');
fbq('track', "PageView");</script>
<noscript><img height="1" width="1" style="display:none"
src="https://www.facebook.com/tr?id=691433037612974&ev=PageView&noscript=1"
/></noscript>
<!-- End Facebook Pixel Code -->
Here is an additional screenshot of the issue: https://www.screencast.com/t/00S1uNlpYx
Hope this is helpful!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Christopher Zack , thanks for the quick feedback on the issue!
Interesting to see your results. Here is what I see in both Firefox and Chrome:
Here is my environment:
Could you give more details on the Browser version and operating system? We need to better understand and try to replicate it.
If we are able to replicate the behavior, we can file a report to try and tackle the issue!
Let us hear from you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Google Chrome:
Version 79.0.3945.88 (64-bit)
Firefox:
71.0 (64-bit)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Windows specifications
Edition: Windows 10 Enterprise
Version: 1809
OS build: 17763.379
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.