LATENT VALUES IN SETTERS UPON REMOVE / RESET - VALUES ARE NOT CLEARED
This may be epically-destructive to undo? Semi non-destructive elsewhere?
Could this semi-benign latent value bug described below be the primary culprit for randomness people are experiencing in the undo. Those variable values persist in most cases and can be invoked / acted upon. They are definitely not clearing unless a user behavior triggers them to. If that is the case that they persist, how can they not adversely affect and trash the undo sequence leaving a trail of hiccups here and there?
This bug appears any time a user elects to remove a style property associated with a class.
press the button to Remove this style
the result generates a latent value (the value captured is expressed as the runtime pixel equivalent, not the value type of the original, unless the runtime attribute in css is in px or hex for color, etc)
This latent value bug converts or captures numeric values to a runtime value type and leaves that conversion in the numeric field within the setter. So, the latent value translates/converts the value of VW, VH, EM, REM, and % to pixels rather than just displaying the default or the inherited value type that should be displayed upon removal (very confusing). The latency is benign if you select some other object as doing so will clear the field (no idea if this actually clears the var or if it persists). It appears that it gets flushed upon deselecting/selecting new object purging the latent value.
If you attempt to drag, nudge or keyboard nudge any of the setter values that still display the latent ghost pixel value, the value iterates from that latent runtime value rather than the null, reset default or inherited value that should be the basis.
RUNNING LIST OF AFFECTED PROPERTIES:
I will update / add to this list as I encounter the issues and add screencaps
- padding (runtime px)
margins (runtime px)
background color ( last used value hex or rgba )