Separate touched and pristine logic

[jaetask]

touched is not the same as pristine

touched is when a field has had focus and been blurred

• is untouched by default
• is untouched on RESET
• is touched on first BLUR

pristine is when a field has been edited

• is pristine by default
• is pristine on FOCUS
• is pristine on RESET
• is dirty on any CHANGE, SELECT etc That is different from default value

[tomByrer]

Is this to track filling a form?

A few thoughts: BLUR happens when an element is [TAB] into? You might over-track blind people.

Will a text input become pristine when the contents are deleted manually? If so, perhaps 'filled' is easier to understand by ESL? (Though I do like the pristine word.)

[jaetask]

There is a common way this is interpreted by Formik and Angular etc. The settings above are taken from those, so that there is consistency across libraries.

TAB out is still a blur, this is controlled by the browser