unexpected failure with v-model in some compiled codes before 2.5.0

[KagamiChan]

Version

2.5.0

Reproduction link

https://jsfiddle.net/skagami/b3tkrpmv/2/

Steps to reproduce

• click on the radio element, and no console output
• change vue version to 2.4.4, click on the radio again, and voila the console output

What is expected?

vue can handle the event on the input element

What is actually happening?

vue dose not handle this event

---

The render() part is modified from compiled code with vue@2.4.x from element-ui's radio-button component

It seems that the compilation for v-model for this component has changed between vue@2.4.4 and vue@2.5.0

consider a simplified template:

<input type="radio" v-model="value" :value="foobar" >

with vue-template-compiler@2.4.4 the output is:

render: 'with(this){return _c(\'input\',{directives:[{name:"model",rawName:"v-model",value:(value),expression:"value"}],attrs:{"type":"radio"},domProps:{"value":foobar,"checked":_q(value,foobar)},on:{"__c":function($event){value=foobar}}})}',

with vue-template-compiler@2.5.0, the event name changes:

render: 'with(this){return _c(\'input\',{directives:[{name:"model",rawName:"v-model",value:(value),expression:"value"}],attrs:{"type":"radio"},domProps:{"value":foobar,"checked":_q(value,foobar)},on:{"change":function($event){value=foobar}}})}',

I don't know if this is a feature, or the template is not correctly written.

[posva]

Can you please put the actual template that lead to that output?

[javoski]

In version 2.5, Vue is not using the token '__c' to represent change event for radio and checkbox anymore.
Why are you using Vue 2.5 to run the code generated by v2.4? 🤔

[KagamiChan]

@javoski An example: some UI libraries are released in compiled code to work both in webpack and browser

IMO it might be a little difficult to assure that all 3rd party libraries in a project are always compiled under the same minor version

This seems resulting a breaking change for 3rd party libs, I suggest it be documented

[posva]

It's true that people need to re-bundle their libs. @yyx990803 I think we should communicate on this. I remember we did something similar in the past.

[yyx990803]

FYI this is unintended - we will preserve backwards compat in the next patch release.