Web Direct Glitch
Operating system version
Mac OS 10.10.1
Description of the issue
Hidden fields affect the behaviour of the web direct UI.
Steps to reproduce the problem
Create two fields, one for read and one for write, and a field for marking record as locked.
Set the read field to read-only in the UI by disabling data entry in Browse Mode.
Set the read field to be hidden when the locked field is empty.
Set the write field to be hidden when the locked field is not empty.
Make the locked field a checkbox with a single value valuelist 'Yes'.
Important: Place the read field on top of the write field.
The read and write fields should each appear, depending on the state of the locked field. You should be able to enter data into the read field when the locked field is unchecked. You should not be able to enter data when the locked field is checked.
You can't enter text into the read field under any circumstances.
The fix is to place the write field on top of the read field.
The issue is that the behaviour is different between App Client and Web Direct Client.