The JS change tracker, which sets the dirty states on the edit form "Save" and "Publish" buttons is very inconsistent
Text field on a page - works well changing a value and tabbing out will set a dirty button, reverting the text field will set the button state back to clean
TinyMCE on a page - changing a value and tabbing out will update the change tracker, reverting the text field will not revert the button state
TextField on a ModelAdmin managed DataObject - simply clicking on the TextField sets a dirty state
LinkField - doesn't use the changetracker, instead it directly manipulates the publish button only because that's the only way to set that without also changing the save button
Elemental - works very well, updates state as you type instead of when you tab out of an input, however inline saving an elemental will erroneously set the Publish button to clean
(not the changetracker though somewhat releated) Elemental with a nested LinkField - inline publishing an element will cascade publish the LinkField, though the draft/modified state of the LinkField is unaltered, you need to refresh the page to see it's published
It really doesn't help that the edit form Save/Publish buttons are regular DOM elements, the change tracker using entwine and a large amount of a input fields are react based.
I feel as though there's simply too much complexity an convolution at this point to properly fix this inconsistency. At this point it feels as though we'd really need the entire CMS in react and we'd need to fully redo the change tracking system which would either use some type of application state, or we'd have a good system of emiting events.
The JS change tracker, which sets the dirty states on the edit form "Save" and "Publish" buttons is very inconsistent
It really doesn't help that the edit form Save/Publish buttons are regular DOM elements, the change tracker using entwine and a large amount of a input fields are react based.
I feel as though there's simply too much complexity an convolution at this point to properly fix this inconsistency. At this point it feels as though we'd really need the entire CMS in react and we'd need to fully redo the change tracking system which would either use some type of application state, or we'd have a good system of emiting events.