4 commits

Author	SHA1	Message	Date
Func	0c707ca259	HTMLFormField: Bypass the inverting logic of HTMLCheckField for disable-if and hide-if ... Values loaded from the default wouldn't be inverted, there is no need to copy the conditions to here, we can just simply bypass them. Fortunately, nothing can be affected in a normal use case, since all value of fields would be set to server. Thanks to the newly added tests, which helped me to realize this problem. Change-Id: I5589ba7383587afdd9307c79e88849dacee02706	2022-02-01 13:09:13 +00:00
Func	c574f49f34	HTMLFormFieldTest: Use mFieldData for check of values ... Fields can have some filter to process the data, for example, HTMLCheckField would return true rather than raw string '1', we should also test this. Note that the param indicating 'checked' state is matching the state on client-side, the value would be inverted by HTMLCheckField... Change-Id: Ia9a7a8c46b0a55ecf2d5378a0d0b6cc00cdb54eb	2022-02-01 08:10:14 +00:00
Func	53d4b41be3	HTMLFormField: Split out the validation of cond-state params ... Follow-up changes will use cond-state params in other functions, split this out to make sure it's validated. Change-Id: Icf358794b11a8f986fbd02c8f1b15ea9d1ef4d15	2022-01-28 21:47:52 +00:00
Bartosz Dziewoński	751f050bf3	Add tests for HTMLFormField 'hide-if' / 'disable-if' functionality ... (Test scaffolding code copied from HTMLRestrictionsFieldTest) Change-Id: I9d221059813a6ac362e3e070984abcaae57906dc	2022-01-28 22:44:35 +01:00