Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chat UI input onchange event missing. No way to detect text change. #2313

Closed
1 of 2 tasks
mudassir93 opened this issue Apr 7, 2020 · 3 comments · Fixed by #2735
Closed
1 of 2 tasks

Chat UI input onchange event missing. No way to detect text change. #2313

mudassir93 opened this issue Apr 7, 2020 · 3 comments · Fixed by #2735

Comments

@mudassir93
Copy link

mudassir93 commented Apr 7, 2020

Issue type

I'm submitting a ...

  • bug report
  • feature request

Issue description

Current behavior:

No method/event to detect the change in the input.

Expected behavior:
There must be an event which should be fired when the text is changed in the input.

@gonzalo42
Copy link

Any news on this??? I find it shocking that a basic feature such as detecting text change is not in the control

@crates
Copy link

crates commented May 10, 2021

@akveo / @nnixaa / @mishkolesnikov / @Tibing / @yggg / @piotrbrzuska / @SashaSkywalker / @sashaqred / @elupanov:
Sorry to tag so many people from your team, but we really need movement on this item right away.
This is an important feature for us immediately. If we issue a pull request, can we get it merged?
Let us know if we can help out with this item. It seems pretty straightforward to get it implemented.
Thank you for everything you're doing with Nebular!

@piotrbrzuska
Copy link
Contributor

@crates, CEO of something - i am not a Akveo member, i'm just a developer, who made some fix in this module. If you write that it's a rather simple thing to do, just do it and send Pull Request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants