You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using when conditions in blueprints with a radio field controlling the visibility of other fields, the value of the radio field resets unexpectedly during drag & drop file uploads in a files field. This causes a frustrating user experience where the field linked to the when condition disappears, even though the file upload is successful.
In the panel, select Option 2 in the radioField (do not save changes).
Drag & drop a file into the conditionalField.
Observe that the radioField value resets to option1, causing the conditionalField to disappear (although the file was correctly uploaded to Kirby).
Expected Behavior
The value of the radioField should not reset during the file upload process, and the conditionalField should remain visible.
Actual Behavior
The radioField value resets to its default (option1).
The conditionalField disappears immediately after the file is uploaded, even though the file upload itself is successful.
Setup
Kirby Version v5.0-beta.1
The text was updated successfully, but these errors were encountered:
Description
When using
when
conditions in blueprints with aradio
field controlling the visibility of other fields, the value of theradio
field resets unexpectedly duringdrag & drop
file uploads in afiles
field. This causes a frustrating user experience where the field linked to thewhen
condition disappears, even though the file upload is successful.To reproduce
Expected Behavior
The value of the radioField should not reset during the file upload process, and the conditionalField should remain visible.
Actual Behavior
The radioField value resets to its default (option1).
The conditionalField disappears immediately after the file is uploaded, even though the file upload itself is successful.
Setup
Kirby Version v5.0-beta.1
The text was updated successfully, but these errors were encountered: