Change Details

Other requirements: [] Add the topic to the inclusion list for sanitization

[] Track successful edits to template pages, … [] … but only if the `<templatedata>` section (or the `{{templatedata}}` template in dewiki) was touched. [] Additionally track if the TemplateData editor was opened before the page was saved. (The dialog might need to set a hidden bool that is send to the server when saving. Or find another way to combine these 2 dimensions. Might as well be possible to do it entirely on the client, i.e. hook into the save button.) [] Ideally track if actual changes have been made in the editor, if possible. Otherwise just track the fact that the dialog was opened and confirmed at least once. Other requirements: [] Add the topic to the inclusion list for sanitization Suggestion: * It sounds like there must be client-side code involved to track if the dialog was used. The server has no way to distinguish between manual and interactive edits otherwise. * To reduce complexity, try to do all tracking client-side.

[] Track successful edits to template pages, … [] … but only if the `<templatedata>` section (or the `{{templatedata}}` template in dewiki) was touched. [] Additionally track if the TemplateData editor was opened before the page was saved. (The dialog might need to set a hidden bool that is send to the server when saving. Or find another way to combine these 2 dimensions. Might as well be possible to do it entirely on the client, i.e. hook into the save button.) [] Ideally track if actual changes have been made in the editor, if possible. Otherwise just track the fact that the dialog was opened and confirmed at least once. Other requirements: [] Add the topic to the inclusion list for sanitization Suggestion: * It sounds like there must be client-side code involved to track if the dialog was used. The server has no way to distinguish between manual and interactive edits otherwise. * To reduce complexity, try to do all tracking client-side.