Date field incorrectly considered changed

Issue description

When there is an onChange listener on a date field in a form script, it fires even when there is no change in field. This is a serious issue since it might cause existing data to be overwritten incorrect updates. Many onchange listeners just overwrite without considering the source of the information.

Developer comments

Strict equal on date objects is a problem, just as well as ordinary equal. Improved that. This is the only place on the client where the value is considered native, and not just as a string (=sequence of characters) which makes it kind of difficult.

Affects

Form page(Page)

Reporting date

2026-02-22

Reported by

Robert Cerny

Resolving date

2026-02-25

Resolved by

Robert Cerny

Resolved in version

Topincs 10.1.0 – next release

Work sessions2

Start	2026-02-23T14:15:40
End	2026-02-23T14:43:03
Participant	Robert Cerny

Start	2026-02-24T10:11:07
End	2026-02-24T11:22:05
Participant	Robert Cerny