Status: Submitted
Status: Duplicate
Status: In progress
Status: Implemented
Status: Rejected

Fix the bug in rendering of special HTML characters

Posted Jan 24 by Ferdinand Prantl.
Updated Dec 03.

When a code sample is added to a post (indented by 4 spaces), '>', quotation marks or other special HTML characters are escaped and become "& g t ;", "& q u o t;" etc, when the post is submitted. For example, see the

Note, that I had to put spaces to the escaped sequence samples above: "& g t ;", for example, because if I left them out, the sequences would be converted to the corresponding HTML character. The text of the post should be rendered as-is, when submitted.

It is difficult to write replies about software development to this forum. I see it a serious bug in the software running this forum.



Any chance to get this fixed? It is really annoying, as you can see at, for example.


The preview shown during typing a reply is correct. The wrong encoding happens first after posting the reply.

Any chance of taking care of this bug soon? Thanks!


Testing the character escaping today again:

<!DOCTYPE html>
<html lang="en">

  <meta charset="utf-8">
  <meta http-equiv="X-UA-Compatible" content="IE=edge">
  <meta name="viewport" content="width=device-width, initial-scale=1">

  <title>Browsing Demo</title>

  <link rel="stylesheet" href="//server/otsupport/csui/themes/carbonfiber/theme.css">
  <script src="//server/ot/cs/widgets?crossOrigin=true"></script>

      'csui/lib/marionette', 'csui/utils/contexts/browsing/browsing.context',
    ], function (Marionette, BrowsingContext, NodesTableView) {

      var contentRegion = new Marionette.Region({el: '#content'}),
          browsingContext = new BrowsingContext(),
          nodesTableView = new NodesTableView({context: browsingContext});;

  <div id="content" class="binf-widgets"></div>



Still not fixed :-(

 You have subscribed and will receive email notifications of updates to this topic. To unsubscribe, uncheck the checkbox.


Related categories

Your comment

To leave a comment, please sign in.