Try this on a modern (ICS, Jelly bean) Android device:
Open the Messaging app and type a sentence to someone. The keyboard is snappy, the completion works well, and spaces are added after words are completed.
Open www.google.com in the browser or Chrome for Android and type the same sentence in the search field. It sucks. The completion is awful, the correction doesn't work (it suggests corrections but never choose them automatically), and spaces aren't inserted after words.
What's the deal? Is there any way I can improve the completion correction on my HTML pages, maybe by adding some hidden attributes to the <input> elements?
Related
When I focus a text input field on Chrome on Android, the shift key is enabled ⇪, even though I set autocapitalize="none".
The input for this field is case-sensitive, so how can I help Android users to write lower-case strings by default?
Tests
Tested on Android 10, Chrome v85.0.4183.127 with Gboard.
<input autocapitalize="off"></input>
Works as expected, not capitalizing a single word.
<input autocapitalize="none"></input>
Also works as expected, not capitalizing a single word.
Suggestion
You may want to try using autocapitalize="off" (seems to be more restrictive than none in the meaning of the word, but the spec states they should be the same).
Given that this works as expected for me, it is possible that your software keyboard software is being troublesome. Try downloading and checking with Gboard and see if that resolves your issue.
In farsi letters are attach together to form writing scripts. However when I save HTML pages using "UTF-8" or "Windows-1256" encdoings, and try to display them using webview in android, letters are diplayed seperately and in left-to-right direction (instead of RTL).
I should notice that this case is not happening in phones supporting farsi.
Correct form should be like this (snapshot from phone supporting farsi):
Bad-formed text happens in phones not supporing farsi (Persian):
It should be noticed i've used persian font in both cases.
I also see some solutions for normal Strings in java which changes character on by one in this
question
My question: Can i fix this cases (or it should be fix by phone vendors)? if possible what is solution?
I hit this bug a lot when I was doing keyboards. The problem is that the build in canvas.drawText function in Android didn't support RTL languages. There was a patch for it, but it wasn't part of the default build of Android. So only models going out to those parts of the world that used it tended to have it. Unfortunately I know of no way to test whether it has the patch. And if it doesn't, there's no way to fix it. You could try reversing the text, but then you'd break devices which did have the patch.
Long story short- there is no way to fix it. However, I'd be shocked if Google hasn't picked up the patch in mainline by now (it existed back in the 2.2 days), so its a shrinking number of phones effected.
You can try making html with reverse font sequence! just write a windows app to get font and deliver reverse one, and use it in your android device
While I'm developing responsive website I have used this uni-code ( » ) to the read more links. It is displaying correctly in desktop browser but it is not displaying correctly in mobile devices like android or iPhone. Is it possible to display the same as in desktop..? What's the problem..? Whether the mobile device doesn't support uni-code..?
The problem is in the embedded font you use, via #font face. The version used by Android is apparently broken. It does not display “»”, and it has problems with many other Latin 1 Supplement characters too, see my test page. Something may have gone wrong when you set up the font files on your server.
The problem does not appear if you remove the font-family setting, letting each browser use its default font, or if you use Droid Sans as hosted by Google, using <link href='http://fonts.googleapis.com/css?family=Droid+Sans' rel='stylesheet'> and font-family: "Droid Sans", sans-serif.
The problem is most probably not in the display of a character (“»”, U+00BB RIGHT-POINTING DOUBLE ANGLE QUOTATION MARK, is very widely supported in fonts) but in the character encoding. If the encoding is not properly declared, different browsers may make different guesses.
Check out the W3C page Character encodings, and make sure that the declared encoding matches the actual one.
If problems remain, please post a URL and explain what “is not displaying correctly” means (not displaying at all? space shown? some wrong characters shown? which?).
android does not support special characters, in android we need to write > to show ">" character. why don't you use image instead of characters.
I'm trying to perform autocomplete with Cyrillic and English data.
If I type some search text in English everything is fine (except overall speed of jQuery on Android), but when I try to search for something in Russian or Ukrainian the phone sticks.
How does a phone stick?
Ok, seriously - See if this has to do with encoding. Maybe at some stage you didn't define encoding as utf-8. Be sure to do it in HTML head and on the server side.
[edit]
The problem seems to be with keypress event.
After you preform tests I suggested (running on desktop webkit and checking if keypress is triggered at all in android) report back and I will be able to help and fill in this answer
I have testing an app I ported to 2.3 on the Android 2.3 emulator, the app includes Hebrew strings displayed in a WebView required solving three problems:
Telling webview to use hebrew fonts (see my post with solution her Android 2.3 Hebrew fonts in Webview)
Telling webview to display the string right to left, which I solved by adding
<p dir="rtl">
The last problem is that webview mirrors the text: in other words the first word that should be on the right is the last word on the left and also the letters of that word are flipped, the first letter that should be on the right is the first letter from the left.
BTW, the 2.3 emaulator displays the string correctly if in a TextView.
Any ideas on how to fix #3?
I'm using webview that needs to show a complete hebrew website.
I can tell you that I didn't encounter any problem you have listed, but I DO know that sometimes the os (especially when it's custom) doing some problems with hebrew.
If you want to check it more closely, just download the 3.X (Honeycomb) platform to the sdk manager, and try it again (Honeycomb should have built-in hebrew display, so there shouldn't be any problems. If you want, you can send me the link and il'l check it out.