Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
domphan opened this issue Sep 17, 2020 · 0 comments
Open

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

domphan opened this issue Sep 17, 2020 · 0 comments

Comments

@domphan
Copy link

domphan commented Sep 17, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant