Value with comma and multiple about virtual-select

[sa-si-dev]

@Jaaap this issue got fixed in the release v1.0.19

To avoid this issue, use setValueAsArray: true property. By doing so, multiple select's value would be available as JSON string in the hidden input (e.g. '["1", "2"]')

[sa-si-dev]

@Jaaap I will check and fix it in the future release.

[Jaaap]

Ah thank you for this solution.
I realise i have not made clear what i want to achieve:
To make it behave exactly like a select[multiple] which means a separate input[type=hidden] for each value.

That way we can use it as a progressive enhancement on an existing select.
Is that feasible?

[sa-si-dev]

Ah thank you for this solution. I realise i have not made clear what i want to achieve: To make it behave exactly like a select[multiple] which means a separate input[type=hidden] for each value.

That way we can use it as a progressive enhancement on an existing select. Is that feasible?

@Jaaap, The concept of this plugin is to improve the performance by avoiding the number of DOM elements on the page.
If we add a separate input[type=hidden] for each option, this might affect the performance.

[Jaaap]

Yes your performance is awesome!
I think it will still be acceptable if you start without any input[type=hidden] for multiple and dynamically add input[type=hidden]'s when users select options.

[sa-si-dev]

@Jaaap I will try this and use it if not affecting the performance.

[Jaaap]

Gentle reminder.
Is this still on your radar?

[sa-si-dev]

Yes your performance is awesome!
I think it will still be acceptable if you start without any input[type=hidden] for multiple and dynamically add input[type=hidden]'s when users select options.

I tried this method. Even though we add hidden input for only selected options, there may be a case where select all action would add hidden input for all options available.