Ok, so special characters should be shown as they are and not as html entities.
What about special characters which form tags? Should they be shown? Isn't that a security issue?

My call for fixing this was to use strip_tags.
So, sending special characters to look good. But tags are not sent.

So, the attached example (which has special characters resembling tags on the WYSIWYG editor, not the source view) should look like this on the side bar: Weight: {wiehfdj}

What do you think?

PR: https://github.com/LimeSurvey/LimeSurvey/pull/1452

Text is flatten. After that. special chars are sent to the sidebar. Tags, which could be formed by special chars re-coded, are not sent.

But : viewHelper::flatEllipsizeText($questionText, true) must already remove p tag here.

Seems test is not really flatten here ?

https://github.com/LimeSurvey/LimeSurvey/blob/af172d9dcbd46a4ebb9a43428cf45162c2741420/application/helpers/viewHelper.php#L216

Oh : here

is not a tag , it's a HTML false tag ?

Can you send the lss please ?

If right : 3.X have same issue

Capture d’écran du 2020-06-29 16-45-30.png (26,341 bytes)   

Capture d’écran du 2020-06-29 16-45-30.png (26,341 bytes)   

Capture d’écran du 2020-06-29 16-46-04.png (37,217 bytes)   

Capture d’écran du 2020-06-29 16-46-04.png (37,217 bytes)   

FYI. We have followed discussion with @Denis on github PR.

Made me think, how should special characters travel from server to front end. I believe they should travel as text.
Then Vue takes care of escaping.

That's how it is set now.
So wouldn't change the current PR.

If it is fine, I will wrap it there and then open a new ticket for v3

Json send totally filtered caracter : it's the purpose of flatellipsise

vue escape it again

This is the issue

Tested the issue by checking out to the branch. Special characters are not diplayed in question code,working as expected
Please refer the screenshot for more details

Since

are shown in HTML editor : it must be shown in management :)

It's a false tag.

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=30243

Fixed in Release 4.3.3+200707