HTML Comment out

[chris_slupianek]

Has anyone got the "comment" tags to work in a published Canvas Page?  Every time I add a comment <!-- Comment here --> to the page and publish it, Canvas wipes my code out. 

[Stef_retired · Accepted solution]

 @chris_slupianek ​, the rule of thumb in the HTML Editor is that if you're using a tag that is not listed in the Canvas HTML Editor Whitelist, it will get stripped out. I know we've had specific questions in the past about the "comment" tag, which definitely doesn't stick.

[Stef_retired · Accepted solution]

 @chris_slupianek ​, the rule of thumb in the HTML Editor is that if you're using a tag that is not listed in the Canvas HTML Editor Whitelist, it will get stripped out. I know we've had specific questions in the past about the "comment" tag, which definitely doesn't stick.

[szarka]

Since an HTML comment isn't an HTML element , an allowlist of elements doesn't actually address whether comments are allowed. (And there is no security reason I am aware of that they should be stripped, so it seems odd that they're stripped.)

I'm also working on a related problem, which is that although the src attribute for an img element is in the allowlist, the HTML editor strips out the entire attribute when a data URL is used. Again, it's difficult to see why this poses a security risk, since external URL references can deliver the same payload.

[a_p_g_robinson]

Edited to add - use <div> rather than <span>

There is a bit of a workaround although it is not ideal.

Click to edit the page and then click on HTML Editor.

Surround the text to be hidden with:

<span style="display:none;">

</span>

Then save without returning to the Rich Text Editor.

The reason that it is not ideal is that when you go in to the Rich Text Editor it will strip the tags out, so the next time you edit you will lose them (as edit always starts up in RTE as far as I know).

[a_p_g_robinson · Accepted solution]

Update -

If you use

<div style="display: none;">

</div>

instead of <span...

then it appears to be persistent. Info found here: Re: Aceptable HTML Elements

[karen_bowden]

Well, what stinks is I just learned this the hard way. It not only strips out the comment tags but *everything* that was between them too. Thanks a lot.

[JillRho]

I can't believe that after 6 years that this is still an issue...grr

I hate the workaround...

<div style="display: none;">
<p>-------------- // START ROW #1 // --------------</p>
</div>

That and my **bleep** code has to deal with foreign characters being made into &crap;

[james_neill]

+1 request to allow HTML comments.

The links to the whitelist HTML pages in this thread are broken.

@JillRho's workaround works. 

[Chris_Hofer]

Good evening, @james_neill ...

The HTML allow list can be found in the blue box at the top of this Guide: How do I use the HTML view in the Rich Content Edi... - Instructure Community (canvaslms.com).

Also, if you would like to see this element added to the HTML allow list, then you could certainly submit this as a Feature Idea request.  Here are some documents for you to look through:

• How do idea conversations work in the Instructure ... - Instructure Community
• What is the feature development process for Instru... - Instructure Community
• How do I create a new idea conversation in the Ins... - Instructure Community

Hopefully these links will be of some help to you.

[ARBYDICKERT]

I just lost a week of work the hard way. The HTML tag should be OK to use WW3 has it. It is not deprecated. It is valuable and in wide use in other HTML applications. This should be changed so that code is not wiped out. I did not know this was a problem until I lost all my planning for the next month. I use tables to create a calendar and the students were getting confused, so I commented out the parts of the table I did not want them to see. So I lost all of it for the next 4 to 5 weeks.

So I learned the hard way.