v-on dynamic argument doesn't work with .native modifier

Version

2.6.0

Reproduction link

https://codesandbox.io/s/r749jp21o4

Steps to reproduce

I made a simple button component which does not emit any events. In the app there are three instances of it with the @click.native event bound in different way.

You can see the first button component which was bound with @click.native works and increases the counter, but the rest which use v-on and the new conditional binding syntax do not.

I thought it might have been some limitation of native events but this also happens with other modifiers, like keydown.somekey.

What is expected?

The events should be bound and all the buttons should work.

What is actually happening?

The buttons do not work. The events are not bound. Only the first button actually gets a listener attached when I inspect them with chrome’s devtools.

[bonno123]

hey @yyx990803, how can I use @[condition].native here in this codition where one condition has a modifier (v-on:keyup.enter) and another has no modifier(v-on:change)

<component 
    :is=" isCompDropdown(field) ? Dropdown : InputText"
    @keyup.enter="!isCompDropdown(field) && getUsers()"
    v-on="isCompDropdown(field) ? { change: getUsers } : {}"
/>  

[yyx990803]

Directive arguments and modifiers are separate concepts. Argument is the part after v-xxx: and before any modifiers. Modifiers always start with a .. The dynamic arguments feature in 2.6 applies only to the argument, not modifiers.