Timeline for How to capture the text user enters in the `ui:inputText`
Current License: CC BY-SA 3.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Oct 18, 2016 at 17:10 | history | edited | Praveen | CC BY-SA 3.0 |
added 252 characters in body
|
Oct 18, 2016 at 17:08 | comment | added | Praveen |
@Rao and @NickKahn By default aura, updates searchKey attribute when the ui:inputText loses focus(i.e onblur), since you are access value in keyup ; we have to explicitly tell aura to update the value when there's keyup event in the ui:inputText .
|
|
Oct 18, 2016 at 17:01 | vote | accept | Nick | ||
Oct 18, 2016 at 16:55 | comment | added | Rao | @Praveen thanks for the pointer on updateon , I never knew that :) | |
Oct 18, 2016 at 16:51 | comment | added | Praveen | @NickKahn check the updated answer.It would solve the issue. | |
Oct 18, 2016 at 16:51 | history | edited | Praveen | CC BY-SA 3.0 |
added 64 characters in body
|
Oct 18, 2016 at 16:50 | comment | added | Nick |
interesting and i did see that .... second time i see the old value so first time i entered 'jo i got undefined second time i entered joh i got jo , what event should I use? in order for that to work
|
|
Oct 18, 2016 at 16:47 | comment | added | Rao | @NickKahn you will get undefined for the first time because on keyup the old value was "undefined", try assigning a default value to the searchKey attribute (or) change the event to be based on button click. | |
Oct 18, 2016 at 16:44 | comment | added | Nick |
i'm still getting undefined , when i debug the code from developer console.
|
|
Oct 18, 2016 at 16:38 | history | answered | Praveen | CC BY-SA 3.0 |