jquery-deserialize does not remove selection before deserialization multiple select about jquery-deserialize HOT 8 CLOSED

@EnricoU i think the use case here is that calling deserialize on the form will potentially not properly set multiple select list values if there are existing values on the element -- basically after deserialization the form values would be in an invalid state because they don't match what was serialized.

from jquery-deserialize.

@dshiryaev-plesk hmm, why hardcode selected="selected" if you don't want it?

from jquery-deserialize.

But it does seem like a bug, so I will look at it soon.

from jquery-deserialize.

It's just for the example. If you delete selected="selected", then select the options manually, then run javascript code, you will get the same result.

@dshiryaev-plesk hmm, why hardcode selected="selected" if you don't want it?

from jquery-deserialize.

@dshiryaev-plesk please try out https://github.com/kflorence/jquery-deserialize/releases/tag/2.0.0-rc1

from jquery-deserialize.

I think there is no need to update the selected attribute programmatically as the browser will automatically know which element is selected. The selected attribute is intended to set a default option on page load.

From: https://www.w3schools.com/tags/att_option_selected.asp

"When present, it specifies that an option should be pre-selected when the page loads."

A pre-selected option seems "selected", but the $('#selectid option:selected').val() command just returns the new value set by the deserialization function.

from jquery-deserialize.

@kflorence, exactly.

from jquery-deserialize.

Closing, as this should have been addressed with #39.

from jquery-deserialize.