Android webview Samsung Galaxy S3 / note not receiving text input - android

I've been struggling for a few hours/days now trying to figure out why only on samsung devices would the webview not receive any input in a text field, it appears to be fine on other manufactures e.g Sony and nexus just not Samsung Note running 4.1
The input box gets focus and the keyboard highlights the selected letter it just does not appear in the input text field, but there is one strange thing it will accept other certain characters e.g. € £ and other foreign characters just no other standard ones or numbers.
I have tried a few different things like webView.getSettings().setJavaScriptEnabled(true); and webView.requestFocus(View.FOCUS_DOWN); neither did the trick :(
The page I am trying to do input on is on the web and not an internal page, but the same issue happens when using google. e.g.

Related

Multiple inputTypes won't do numberSigned and numberDecimal simultaneously

For a few specific fields on my app the user needs to be able to enter a number that uses both decimals and negatives. However, the keyboard that shows up for the EditText now only shows the negative sign and no option for a decimal.
This seems to specifically an issue with the model of tablet and it's firmware. The device is a Samsung Galaxy Tab 2 10.0 that is running Android 4.1.2. I have tested on a Samsung Galaxy Note 8.0 running Android 4.4.2, and it works there, but both negatives and decimals are handled with the same key. The biggest issue I need resolved here is the inability to be able to use both negatives and decimals on the Galaxy Tab.
I used:
android:inputType="numberDecimal|numberSigned"
to attempt to set the ability to use both keyboard types.
Is there a different inputType that could achieve both negative and decimal numbers? Is there another way to achieve this same result? (I messed around with using digits, but was unable to get the desired results).

What models of Samsung smartphones have missing period for html5 input type="number"?

HTML5 has a new input type named "number". On most mobile smartphones this brings up a numeric keypad. On pre-html5 phones the type falls back to "text" and we are OK. Yet, on some models the numeric keypad does not have a period and one cannot click the "symbols" button to add one. Known models with this flaw are:
Samsung Galaxy S4, see: Missing period for Samsung Galaxy S4 numeric keypad
Samsung Galaxy Note II
Samsung Galaxy Tab 2 10". see: Samsung Galaxy Tablet does not allow entering floating point numbers to inputs with "number" type
????
What other models? Older Samsung Android 2.2 phone does not have this problem. Other Android devices such as Nabi Tab do not have this problem. I read the Galaxy S3 did not have this problem.
See related discussion:
<input type="number"> in Firefox. Why doesn't Mozilla support number inputs in its browser?
HTML5 - input=number and incompatible browsers
HTML5 input type number vs tel
Also, not noted on those is that input type="tel" works fine for iPad but does not work as a replacement for number on an iPhone. So, a webapp must determine the device model or else resort to input type="text".
What phone and tablet models incorrectly interpret input type="number" as a whole, non-decimal input keyboard?
It turns out to be all SAMSUNG with 4.x as well as HTC with 4.4 and reports of other vendors (Xperia). Long story short, at least put in the fix for anything with User-Agent having SAMSUNG or HTC and running 4.x; but possibly put in the fix for anything having ANDROID.
I have discovered a work around for this problem. It works for my Samsung Galaxy S2 phone and I suspect it will work for all Samsung devices that suffer from the "missing decimal point" problem on the numeric keyboard. Hopefully others with different Samsung devices can check this solution and report their findings.
Unfortunately, it is a client based (phone owner) solution so it does not really help from a web developer standpoint. Here is the solution that worked for me:
While in the browser click on the menu icon (bottom left of phone)
Select Settings
Select Privacy and Security
Scroll down and uncheck "Remember Form Data" and select "Clear Form Data"
Click OK to confirm
After following this procedure, the numeric keypad should show an extra button labelled .-
That is, the same button is used for both minus signs and decimal points. Double-click this button to get a minus sign (provided the field is currently empty) and single click to get a decimal point.

When input type=number android browsers render the input box smaller

I am trying to put together a form with a numeric input that pops up with the numeric keyboard on a mobile device. To do this, I am using an input with type=number. It renders correctly on a desktop (in which case it expectedly looks and behaves exactly like an input with type=text). On my Windows Phone 8, it also displays correctly and pops up with the numeric keyboard.
The problem is when I tested it on my old Android (HTC One V), the numeric input is rendered a little bit narrower than an input with type=text. You can see my code markup here: http://bootply.com/101579. This becomes an issue because I created a Bootstrap 3 input-group with an input-group-addon. On my HTC Android browser, the input is rendered shorter, so there is a gap between the input box and the input-box-addon.
You can see what I mean here:
http://www.browserstack.com/screenshots/a989247294985fc48ab3c3be9f4d1151e301384a. When you look at the screenshots for many of the Android devices (including Samsung Galaxy S III and HTC One X), you can see that the inputs with type=number render more narrowly. When you look at any of the iPhones or the Motorola Droid 4, you can see the form rendered correctly.
Is there a workaround to this issue that will render the input boxes with type=number the same width as those with type=text?
Edit:
I looked at the list of emulators, and I realized that this is only a problem on the Android 4.x stock browser.
Edit:
Neither of the links above work anymore.
Try this css hint
input[type=number]::-webkit-outer-spin-button { margin: 0; }

Angularjs textarea data binding issue in Android 4.0.4 browser

I am working on for creating mobile web application using Angularjs. In one of my page, i used text area for getting some information from user. Also showing users how many characters more remaining, so they aware of maximum limit.
The issue i am getting is, UI is not updating the remaining characters value, during typing inside text area. Furthermore, remaining characters value updates, when user press enter or go to typing next line in text area.
Above issue is not reproducing in PC web browser, iOS safari browsers and Samsung Galaxy phone browser. Only issue i am getting is for Android Tablet running Android OS version 4.0.4.
Here is sample code:
<textarea id="textAreaId" name="textAreaName" class="input-block-level" rows="7" placeholder="Enter your text here." ng-model="oTextArea"></textarea>
<div>length {{oTextArea.length}}</div>
<div>text {{oTextArea}}</div>
In above code length and text div did not update value during typing inside text area for Android Tablet running Android OS version 4.0.4.
if anyone know any solution or reason why it is happening for Android Tablet, then please let me know. Thanks in advance.

My App working fine in Samsung but acting weird in HTC Desire S?

I have created an app demo app using cordova2.7 the app only contains a search box and two buttons in header and the same in the content field. When run the app in Emulator its working fine and then i tried to run it in Samsung mobile its working fine but when i tried to run it in HTC Desire S when i try to enter character to search element its dispalys some white box above the header and when i try to enter the character in the serach field that i have in the content field it does not show the keypad.Please refer the snapshot I have uploaded below from HTC Desire S
Use RIPPLE, an extension to GOOGLE CHROME, which has inbuilt facility to simulate for different devices. You can get the idea from there.
Although, myself being a PhoneGap developer too, it is quite difficult to deal with all the devices. So your design must be Responsive !

Categories

Resources