-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Closed
Labels
1: EasyP3: NormalPriority mark - normal priorityPriority mark - normal prioritybugBug reportsBug reports
Description
Current behavior
Radiobutton falsely looks like it is designed to utilize v-model as the primary way of interacting with passed value. Unfortunately, the value after changing is not being emitted to the parent component, so the only way to use them is to use v-model/value properties for passing values to those components and listening to click events in order to update these values (by guessing that the new state is just the opposite of previous one).
Expected behavior
It should be able to read the radio button state by using the v-model alone.
Steps to reproduce the issue
- Place a radio button with v-model property
- click it couple of times
- watch the v-model property values doesn't change as it should (in fact, it doesn't change at all)
Can you handle fixing this bug by yourself?
- YES
- NO
Which Release Cycle state this refers to? Info for developer.
Pick one option.
- This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from
developbranch and create Pull Request2. Feature / Improvementback todevelop. - This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from
releasebranch and create Pull Request3. Stabilisation fixback torelease. - This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from
hotfixormasterbranch and create Pull Request4. Hotfixback tohotfix.
Metadata
Metadata
Assignees
Labels
1: EasyP3: NormalPriority mark - normal priorityPriority mark - normal prioritybugBug reportsBug reports