Skip to content

MdSwitch has the opposite expected behavior when not using v-model #2275

@domphan

Description

@domphan

Steps to reproduce

Use v-bind:value on md-switch without passing in a v-model prop. (My intention was to set up a v-bind and v-on:change to handle changes explicitly)

Which browser?

Chrome Version 85.0.4183.83 (Official Build) (64-bit)

What is expected?

If v-bind:value = true, it's expected that the switch is toggled on. If v-bind:value = false, it's expected that the switch is toggled off.

What is actually happening?

The opposite of what is expected

Reproduction Link

https://codesandbox.io/s/vue-material-switch-forked-tttcy?file=/App.vue

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions