Thread

I upgraded to 1.6.9, and noticed in my pre blocks that EECore is interpreting my text as smileys. I did a test post;

 pre square bracket block :: 😊 :roll:  :lol:  😊  😡 

 pre angled bracket block :: 😊 :roll:  :lol:  😊  😡 

code square bracket block :: :blush: :roll:  :lol:  :blush:  :rage:

\[pre\] and \[code\] are not interpreted but <pre> is, and it should not be.

I dont know if this EE allows angled pre blocks in the forum, buy my EE install allows all html.

I would expect nothing inside a <pre> block to be touched.

I have a test post on my site;
test post

MadAussie - EE doesn’t know about < code > nor about < pre > - these are HTML formatting things that are done in the browser. EE can only protect it if you use [ code ].

So this isn’t a bug.

sorry, my browser does not interpret 😊 and place an image in its location. EE does that.

http://ellislab.com/forums/viewthread/97685/
see this thread for similar problem and note where Robin says “Right- it’s parsing inside the pre and code tags (unless you use pm code).  It shouldn’t touch it in either”.
That was for converting dashes and other things when it should not have. Smileys were not a problem then, now they are.

Hi, MadAussie -

EE is the one creating the smileys, but EE does not look for pre or code HTML tags; it has no idea how you are displaying this on the front end unless you explicitly tell it so.

I’ll ask Robin to have another look at this since it appears I may be incorrect based on the thread you found, for now, please use [ code ] if you need to avoid parsing.

Yep- it was an ‘iffy’ one- the typography comparison isn’t exact, but it does seem more in tune w/that logic to not parse them.  I went ahead and added it to the bug tracker- we’ll update there once it’s cleared out.  For now- Lisa’s advice to go w/bb code is the way to go if possible.

Thanks for the ‘heads up’.