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

update-items not working on mobile Chrome #75

Open
miloskrca opened this issue Oct 2, 2018 · 8 comments
Open

update-items not working on mobile Chrome #75

miloskrca opened this issue Oct 2, 2018 · 8 comments

Comments

@miloskrca
Copy link

miloskrca commented Oct 2, 2018

Hi,
the update-items event does get triggered on change but the value that the event handler gets invoked with is always the same.

E.g.

  1. initialise the component with value "foobar"
  2. set an update-items listener as defined in the docs
  3. add a console.log to log the "text" value
  4. start typing in the input and changing the value

After de-focusing the input (click anywhere else outside the input field), the "text" value gets updated to the current input value.

What I expect?
The "text" value changes to reflect the input value changes.

What happens?
The "text" value is always "foobar".

OS
Android 8.0.0

Browser
Chrome 69.0.3497.100

@mishanino
Copy link

@miloskrca hello, did you find any solution for this issue?

@miloskrca
Copy link
Author

hi @mishanino, no, sorry, I implemented my own solution.

@mishanino
Copy link

@miloskrca Got it, thanks for your reply

@mishanino
Copy link

mishanino commented Oct 23, 2018

input event is not fully supported on mobile devices
https://developer.mozilla.org/en-US/docs/Web/Events/input

@alexeydg
Copy link

hi, i have this bug. If the ajax mode is on and autocompletion (T9) is enabled on the android mobile phone, the system does not start searching until you press "enter (loop)" Pls fx bug then switch on autocompletion on android 8 and high

@rangermeier
Copy link

This is caused by this: vuejs/vue#9777 (comment)

@tolgap
Copy link

tolgap commented Jun 25, 2019

@paliari Is there a reason why a fix like #83 is not being done? Does that fix break other functionalities?

I'm hurt by this bug a lot. If there's any other workarounds like using the input bind attributes, please let me know!

@fabianlugones
Copy link

I could manage to solve this using the change event of the autocomplete. Follow these steps:

  1. Add a function to the change event of the autocomplete
  2. Add an input-attrs object with an unique id identifier.
  3. Inside of that change event function, get the input's search value through document.getElementById('your-input').value.
  4. Do the desired search inside of this function.

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

No branches or pull requests

6 participants