Closed iiey closed 3 years ago
Right, looks like a bug indeed, thanks for the report.
It looks like the XML tags are interpreted as HTML, I remember we set an innerHTML
somewhere in the add-on, I suspect this is where it happens (looks at the code: we have node.innerHTML = node.textContent.replace(/( +|\t+)/g, replacer);
for replacing spaces by visible characters).
Assuming that replacing the spaces worked correctly, the revert back to the original state should work as well, I don't think this is a separate bug.
I'll look into it, it may take a few days.
Looks like the fix is not too complicated. Would you have a chance to build and try the add-on from branch pr/escape_html? If it works well for you as well, I'll merge and upload a new version to ATN. No worries if you cannot try.
Hey Qeole,
I did try your pr branch escape_html (v2.1.1) and it turns out to work correctly as expected until now no side effects.
Thank you very much for the quick fix!
Awesome, thanks for checking! I'll try to merge & update tonight if I can.
Now up on ATN.
Problem: incorrect parsing tags.
will be showed as follow: or
Reproduction Steps:
Approach 1: activate this option
Approach 2: click on this right button I guess, this is used to toggle tabs/spaces visible modes. But there is no possible to go back to original state (also a bug), where diff is showed correctly.
Expected Behaviours: content of diff should always be correctly display regardless rendering methods