Same-name shorthand (:type
) breaks radio group behavior
#13169
Labels
🔨 p3-minor-bug
Priority 3: this fixes a bug, but is an edge case that only affects very specific usage.
has workaround
A workaround has been found to avoid the problem
scope: compiler
scope: v-model
Vue version
3.5.13
Link to minimal reproduction
https://play.vuejs.org/#eNrlVcFuGjEQ/ZWRT0QK0KQ9uSRSU3FoUUOURD1Zqja7XmritS3bS0Fo/71jm12WhiC1x+bCembejJ+fx8OWfDJmtKo5oWTiciuMB8d9ba6ZEpXR1sMWLC+hgdLqChhBLCMfu+ijXixk9iT5Te29Vj/msxY4Gr+MhZ1OZd/cz2fT29crpHhXhalcK+chr63lyn/PZM3hKvAdqFrKsx5EGy9wMX9a8twjZssUAJbm8oKGU4XUC0bOO/dl576M7gaLTcZJIhQHDc8rIzPP0QKYVJlQcYXrQqyu+5wobLeHJJtmMg6oUCimOKSFBHcVAOYz2sZ2BVsDzZfC7oMAq2Gp7RUjg8j+HJ755gyEOpSAkX4KRQxm4O+hfzWsdMElhvrs/8iNch3LppEARuL3MOY3JkRsVgjdj4y7c7YCpfVen1cES63xF6KlhDckXLB2XToZ95oXTec3Miyp1RpffMCWWvlhmVVCbii4TLmh41aU+AoapkKZBCuEwzoIKSVfYxATcTEshE37Usi1rCsVQ4vMULh4ZwIQqyC53b7knHiHD7UUi9HSaYXTKFZH+XRlhOR2nu6AEXxL6WiMZFLqX1+jz1u8sNaf/+T58xH/0q2Dj5E7y/EwK1S2i/nMLjhebghPH275GtddEO+ylog+EbznDs8ZOCbYTa0KpN3DRbZf4twTavHopmvPlWsPFYgGZBPxccx+PnH0Pd33ow8xDxVFFY+P3CPDveClUPzOauMG+1lI4cFbZBdJhE47cMRupBBGaxiI/fEaux3Hair7LViD7a5CwENEn5qfcf+2a4Uyte89ovhlBOiu+8MnmJFRbP2UiGM21sH5mvq9rXrQ8Ed02v+x/F9a/bNEzW/E86KX
Steps to reproduce
TogglableButton_OK.vue
andTogglableButton_BROKEN.vue
.TogglableButton_OK.vue
, the input'stype
is bound explicitly using:type="type"
.TogglableButton_BROKEN.vue
, the same-name shorthand:type
is used instead.⊚ label1
then⊚ label2
) in the first section (named "OK"). Then, either reload the page or not, and try switching radios in the second section (named "BROKEN").What is expected?
label1
radio button, it should be checked and updatecurrentValue
to 'value1'.currentValue
to 'value2'.TogglableButton_OK.vue
andTogglableButton_BROKEN.vue
What is actually happening?
With the same-name shorthand
:type
attribute binding:currentValue
remains null.System Info
Any additional comments?
In the linked Vue SFC Playground Reproduction, compare
TogglableButton_OK.vue
withTogglableButton_BROKEN.vue
. The only difference is in how the:type
attribute is bound.The text was updated successfully, but these errors were encountered: