This behavior has been resolved and deployed to the production environment as of 2/25/26.
Summary:
When opening the editor for the Syllabus in a course the exact HTML which is currently being displayed on the Syllabus (the contents of the course_syllabus div) are loaded into the editor instead of the actual HTML saved for the syllabus. This leads to a number of issues because we have front end code which spruces up user content (indicating external links, adding download/preview icons for files, etc.) and there may also be custom JS in customer instances modifying how the saved content displays to end users. This extra HTML formatting will cause issues if it is then saved so you end up with situations where someone could open the editor for the syllabus, make no changes to the content, then save and the appearance of the page and saved HTML will be changed.
Expected behavior:
The currently saved HTML for the course syllabus should be loaded in the editor, not content of the course_syllabus div from the syllabus page as that will have had a number of modifications made by the front end (and possibly custom JS).
Steps to Reproduce:
Prerequisites: A course containing a file.
- Go to the Syllabus page of a course and press Edit.
- Add some text, embed the file, and add a link to an external site then save the changes.
- Refresh the syllabus page then select the Edit button. Note that the HTML for the “Links to external site” and “Download” icons for the link and file have now been included in the HTML in the editor.
- Save without making and changes and note that the external link and download icons are now missing
Note: This is just one way that loading the HTML from the page (after it has been modified by the front end) instead of from what we have saved is breaking things, but there are surely going to be other issues with loading the editor this way.
