Thank you for the credentials. From what I gathered so far, the unsaved fields have a display condition on a checkbox field. They should display only when the field's value is not equal to 1.
At first sight, I thought that this happens because the field is configured to store the value("1") on the database only when it is checked, which has its benefits for views with search forms.
So, I tried to reproduce this on a clean install, here hidden link
It was reproduced, even if I configured the field to store "0" on the database when the checkbox is not checked.
Recently, in Toolset Types 3.4.13, we fixed a problem when clearing values for fields hidden due to conditionals. This issue may be related to it.
IMHO, besides what will be stored on the database, and from a PHP point of view, an unchecked checkbox does not have a value(NULL) instead of having the value "0", vs "1" when the checkbox is checked.
I tried a test using a Select field("Has Answer Select" on my test site), with two options(No/Yes) with the corresponding values(0/1). Then I configured the conditional display rules based on these custom fields, and they worked as expected.
Unfortunately, the UI does not allow to change the field type once set, otherwise, we can change the type to a select field with two values(0/1) and 0 being the default value. This way, a value will always exist (either 0 or 1) for the conditional display rules.
However, with some browser console manual hacks, I was able to choose a select field type, save the custom fields group. Then, add the options (Yes/No) with values(1/0), No(0) being the default, and it worked correctly.
I hope this helps. Let me know if you have any questions.
