3.4 doesn't respect checked/unchecked in html any more

[morrow95]

checked / unchecked specified in the html of the input is no longer respected with version 3.4. They will always show in an 'off' state regardless of the true state of the input when loaded.

An example is shown below. This worked perfectly fine with version 3.3.4, yet in 3.4 this will show the switch in an off state when it clearly has 'checked' in the html.

<input type="checkbox" class="make-switch" data-size="small" data-label-width="15" data-on-color="success" data-off-color="danger" data-on-text="Yes" data-off-text="No" name="name" value="1" checked>

[RouNNdeL]

Has anyone managed to fix it, other then using an older version?

[poggialim]

It is still not working... Unfortunately!

[morrow95]

I didn't bother comparing the js from the old/new, but something definitely changed within it to cause this issue.

[danielcsorba]

In the getClassesfunction, the filter's return should be return v !== null; instead of ==.

[souzaemarcal]

Solved here with this:

$(function() {
    $('[data-switch="true"]').each(function () {
        $(this).bootstrapSwitch({ state: $(this).is(':checked') }).trigger('change');
    });
});

[jybleau]

In the getClassesfunction, the filter's return should be return v !== null; instead of ==.

Shouldn't it be return v != null; to also include undefined value ? Because v seems to be undefined instead of null...

The strict operator still leads to classes like this: bootstrap-switch-undefined