We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am having an issues that I cannot seem to figure out. I am using Nodejs 12.22.1 with vue-multiselect ^2.1.7.
The following screen has placeholders as shown in the screen below:
When I type something, it shows as the following but the placeholders come through as shown below:
This only happens on the ipad using chrome but works fine on the desktop using chrome.
Any ideas?
Thanks -Dimitry
The text was updated successfully, but these errors were encountered:
I am also seeing this issue, Node 12.20.2, vue-multiselect 2.1.6 It only seems to be at smaller resolutions or browser widths
<multiselect v-model="selectActivity" name="chActivity" track-by="activity" :custom-label="customActivityLabel" :options="arrChActivity" @input="onChActivity" :searchable="true" :allow-empty="true" @select="enableComp">
Sorry, something went wrong.
Which iOS version, and Chrome version is this (if it still is an issue) occurring on?
If you could also provide a GIT that I can pull and reproduce the error on, that would be great
No branches or pull requests
I am having an issues that I cannot seem to figure out. I am using Nodejs 12.22.1 with vue-multiselect ^2.1.7.
The following screen has placeholders as shown in the screen below:
When I type something, it shows as the following but the placeholders come through as shown below:
![Screenshot-20230403103640-412x138](https://user-images.githubusercontent.com/69314967/229558199-31d23482-e726-44e0-bc24-c53322e1c292.png)
This only happens on the ipad using chrome but works fine on the desktop using chrome.
Any ideas?
Thanks
-Dimitry
The text was updated successfully, but these errors were encountered: