<sup> tag doesn't work with sanitizeHtml
samilieberman opened this issue · comments
PLEASE NOTE: make sure the bug exists in the latest patch level of the project. For instance, if you are running a 2.x version of Apostrophe, you should use the latest in that major version to confirm the bug.
To Reproduce
const formattedTitle = 'My Company<sup>®</sup>';
console.log(sanitizeHtml(formattedTitle));
The superscript tag doesn't work, even though it is in the default tags
Expected behavior
A clear and concise description of what you expected to happen.
The symbol should be a superscript
Describe the bug
A clear and concise description of what the bug is.
The superscript tag doesn't work, even though it is in the default tags
Details
The superscript tag doesn't work, even though it is in the default tags
Version of Node.js:
PLEASE NOTE: Only stable LTS versions (10.x and 12.x) are fully supported but we will do our best with newer versions.
Node 16
Server Operating System:
The server (which might be your dev laptop) on which Apostrophe is running. Linux? MacOS X? Windows? Is Docker involved?
Mac OS X
Additional context:
Add any other context about the problem here. If the problem is specific to a browser, OS or mobile device, specify which.
Screenshots
If applicable, add screenshots to help explain your problem.
I attempted to reproduce the reported issue but couldn't confirm it. The provided test, which checks for the removal of <sup> tags, did not yield the expected result. The <sup> tags were retained, including the registered trademark symbol. Based on my findings, I believe this issue can be closed.
it('should not remove sup tags as they are in default allowed list', function() {
assert.equal(sanitizeHtml('My Company<sup>®</sup>'), 'My Company<sup>®</sup>');
});Please consider reviewing the test and closing the issue accordingly.
Closing as the issue could not be reproduced. @samilieberman if you think we're missing something feel free to provide a unit test (see test/test.js).
@boutell - We are using another library as a workaround because this is still not working for us. I don't have the bandwidth to look into this at the moment, but my colleague Ganesh is going to pick it up. Thanks!