You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
go in the editor and put cursor at the end and press enter a 3/4 times
click "reset dirty"
dirty indicator sticks around
Expected behavior
dirty indicator should reset even with new lines introduced in the editor (use case: after saving the form)
Version
ids-enterprise: 4.35.0-dev (dev), 4.31.4 (prod)
Screenshots
N/A
Platform
Infor Application/Team Name: Infor GHR/FSM
Device: Web/PC
OS Version: Windows 10
Browser Name: chrome
Browser Version: Version 86.0.4240.198 (Official Build) (64-bit)
Additional context
The developer also observed that the dirty indicator is present on load when the content or payload of the editor has new lines "<br>" in it.
The text was updated successfully, but these errors were encountered:
tmcconechy
changed the title
Dirty indicator sticks around (won't reset) when a new line "<br>" is introduced to the editor
Editor: Dirty indicator sticks around (won't reset) when a new line "<br>" is introduced to the editor
Nov 19, 2020
Not exactly sure how the dirty indicator itself related to this. If we had the "Reset Dirty" disabled when the field was not dirty then I could at least see that no "field is dirty" message was being sent when the field changed.
Describe the bug
Dirty indicator sticks around (won't reset) when a new line "<br>" is introduced to the editor (after save)
To Reproduce
Steps to reproduce the behavior:
https://master-enterprise.demo.design.infor.com/components/editor/test-dirty-tracking-reset.html
Expected behavior
dirty indicator should reset even with new lines introduced in the editor (use case: after saving the form)
Version
Screenshots
N/A
Platform
Additional context
The developer also observed that the dirty indicator is present on load when the content or payload of the editor has new lines "<br>" in it.
The text was updated successfully, but these errors were encountered: