-
Notifications
You must be signed in to change notification settings - Fork 13.5k
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
ion-searchbar bug on 3.1.0, 3.1.1, 3.2.0 for non-latin languages. #11566
Comments
Hello, thanks for using Ionic! We will look into this. |
I've also encountered the same symptom after using 3.1.0. when ion-searchbar had worked correctly with 2.x |
we have the same bug~~~~ But , this bug just fire on IOS and IOS simulator . |
I faced the same bug too during inputting Japanese. I could solve this by replacing from |
I had compared this version3.0.1 and version3.2.1 that I found to modify this function "Searchbar.prototype._inputUpdated" can fixed it |
Hello all! This is going to be fixed in the next release of ionic in this pr #11586 |
@jgw96 you linked to an issue ^^ |
@jgw96 It has a android and web issue too. When I type a Korean in ion-searchbar element, Korean alphabets show ㄱㅏㄴㅏㄱㄷㅏㄱ where it should be 가낙닥. global packages:
local packages:
System:
|
I faced the same problem too . when i am using chinese input method in input[text] . Looks like model would not change after blur event happen on the input box. If using english input method first , there is no problem . |
it had fixed on 3.4.0 |
@woodstream I'm still facing the same issue. |
Still getting error with 3.4.0 |
@DavidRyu123 did you managed to solve your problem? Was that fixed in recent version? |
@tscislo yep. It's solved with update. |
Thanks it works for me as well in 3.4.2 |
I'm using 3.19.1, but still have this issue on IOS. |
@skygragon That's the version for the Ionic CLI, you have to update
|
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out. |
Ionic version: (check one with "x")
[ ] 1.x
[ ] 2.x
[ X] 3.x
I'm submitting a ... (check one with "x")
[X ] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
Replication environment: Mac OS X (for PWA)
Different behaviours in Chrome 58.0.3029.96 and Safari Version 10.1 (12603.1.30.0.34) (see videos)
Currently I have replicated the bug on the ionic-preview-app on ionic versions 3.1.1, 3.1.0, 3.2.0
The bug does not happen on 3.0.1.
Description: The key up on the ion-searchbar seems to be broken since 3.1.0 onwards for non latin keyboards. For example I am using a chinese Hanyu pin yin keyboard to type "青山" (qingshan).
However on Safari, the ion-searchbar goes like "qqqiqiqingqinqingqing sqing sqing shqing... ". See video.
On Chrome, the ion-searchbar seems to dismiss the language bar intended to popup.
Expected behavior:
The ion-searchbar should work normally with the different language inputs.
See video.
Steps to reproduce:
check out and build the ionic-preview-app and build
ionic serve
scroll to the ion-searchbar page.
change input to chinese and type "qingshan". notice on Chrome the input for chinese does not appear, and on Safari multiple letters appear.
Change package.json ionic-angular dependency to 3.0.1
remove node_modules and npm install again
notice that things work normally.
Related code:
https://github.com/driftyco/ionic-preview-app
Other information:
Ionic info: (run
ionic info
from a terminal/cmd prompt and paste output below):Cordova CLI: 6.5.0
Ionic Framework Version: 3.0.1 (or 3.1.1 for the bug)
Ionic CLI Version: 2.2.2
Ionic App Lib Version: 2.2.1
Ionic App Scripts Version: 1.3.5
ios-deploy version: 1.9.1
ios-sim version: 5.0.2
OS: macOS Sierra
Node Version: v7.9.0
Bug on ion-searchbar on 3.1.0 and 3.1.1
Expected behaviour
The text was updated successfully, but these errors were encountered: