Change Details

I was surprised to see that when I added a ToggleSwitchWidget to a form (replacing a checkbox) that when I submitted the form it did not behave as a checkbox. In fact if I inspect the element I see no evidence of a form input. As a result I'm having to keep a hidden element around and update its value on every change event. As far as I'm concerned this element should be interchangeable with the Checkbox widget - on mobile web we want to use this instead of a checkbox, but still support NON-JS use cases. I realise the primary use case for this is asynchronous saving, but it should also support synchronous saving.

I was surprised to see that when I added a ToggleSwitchWidget to a form (replacing a checkbox) that when I submitted the form it did not behave as a checkbox. In fact if I inspect the element I see no evidence of a form input. As a result I'm having to keep a hidden element around and update its value on every change event. As far as I'm concerned this element should be interchangeable with the CheckboxWidget - on mobile web we want to use this instead of a checkbox, but still support NON-JS use cases. I realise the primary use case for this is asynchronous saving, but it should also support synchronous saving.

I was surprised to see that when I added a ToggleSwitchWidget to a form (replacing a checkbox) that when I submitted the form it did not behave as a checkbox. In fact if I inspect the element I see no evidence of a form input. As a result I'm having to keep a hidden element around and update its value on every change event. As far as I'm concerned this element should be interchangeable with the Checkbox wWidget - on mobile web we want to use this instead of a checkbox, but still support NON-JS use cases. I realise the primary use case for this is asynchronous saving, but it should also support synchronous saving.