[Bug]: `CInput` @input event not emitted when wrapped inside `CInputGroup` component
See original GitHub issueDescribe the bug
When the CInput
component is wrapped inside the CInputGroup
the @input event is not emitted.
To Reproduce Steps to reproduce the behavior:
- Go to https://codesandbox.io/s/gifted-torvalds-c9nud?file=/src/App.vue
- Type in first input. Logs are not shown in console.
Expected behavior
@input
events should be emitted for inputs wrapped inside the CInputGroup
component
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:11 (5 by maintainers)
Top Results From Across the Web
V-chip not issuing input event to parent - Stack Overflow
I suspect Vue not reacting to the first click due to using an array like this. You could wrap it in a function:...
Read more >html input change event propagates out of wrapping component
When wrapping an html input in a component, without giving the component an explicit @Output change the html input's change event propagates out ......
Read more >Inputs — Essentials ⚡️ FormKit — Vue Forms, Supercharged
Emitted when the component's setup is complete. This is the internal FormKitNode object at the heart of the input. Vue events.
Read more >Vue custom input - DEV Community
Most of us have faced it: build a custom input component. There are multiple reasons behind it but in general, it has custom...
Read more >Inputs | Vue Formulate ⚡️ The easiest way to build forms ...
The label to display inside "add more" button on group and file[multiple] inputs. attributes, An object of non-prop attributes passed to the input...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey guys, I ran into this as well during my development but forgot to record it to later create an issue. This problem is not only isolated to the
input
event, you will also experience this with others such asfocus
andblur
. The.native
workaround proposed by @codebender828 will work in the meantime, however, I would like to pose an additional workaround that I found myself using. Oddly enough you can successfully listen to the input event my attaching listener through the component instance’s$on
method.I’ve forked @codebender828 codesandbox demonstrating this incase you were curious. Check out the sandbox here.
Closing this as it looks to be fixed (update in the next release). Feel free to reopen if this isn’t the case