UDOIT Does Not Remove Suggestion/Error After Editing the Webcourse Page

[lastingParadox]

While completing tickets, I ran into an issue regarding errors/suggestions that cannot be edited on UDOIT. Whenever I edited a page's content, for instance, changing a styled paragraph to a header or removing white highlight behind a text element, UDOIT would not recognize the page being altered upon reloading the LTI. This means that the error/suggestion would not be removed, and in the error/suggestion, the problematic HTML snippet before my change to it would still show up.

While I can occasionally get UDOIT to recognize the fix upon re-saving the page, sometimes UDOIT will just outright not recognize that the page was changed, making the error seem bugged. Trying to manually resolve the error will just give a red error alert.

Below is are images that show the warning still persisting after having changed the "Action Item" text from a paragraph to an h2 header.

Running Firefox if that makes a difference.

[taheralfayad]

Issue Description:

After further investigation of this issue, I think I've found where the conflicts might be happening. If a user were to change the html of an issue prior to marking it as resolved, then UDOIT will not be able to find that HTML upon reloading the state, hence the "Fixed HTML was not replaced in LMS" error. Important to note however, is that every time I fixed an error manually and marked it as resolved, that error was not found after a refresh of the UDOIT LTI (but it was also not found in the resolved issues filter as well. I think the two fixes to this issue would be:

1.) Find a less generic and a less intimidating error message than "Fixed HTML was not found in LMS. Please contact administrator" so as to let the user know that their changes will actually be reflected in both UDOIT and the LMS.

2.) Find a way to retain the previous state of the issue in order to show it in the resolved issues section.

Images:

Before manually fixing the issue:

The issue after the user checks "mark as resolved" after the html content has been altered:

Searching with the "resolved issues" filter (as you can see, the issue in question does not show up in as a manually resolved issue):

Number of issues after the user manually fixes the issue: