Text field entry doesn't work on some ASP.Net webpages
I am trying to make an existing ASP.Net application compliant with Firefox for Android.
I am finding that keyboard entry on text fields is not working generally for webforms that are nested in a <frame> or <iframe>. They work ok when not in a frame.
The text field turns pale blue, and keyboard pops up, but typed characters do not appear in the field until you repaint the page, eg by clicking on another Firefox tab and back again. The blue remains on the field also, and focus won't be seen on any other field, even if you tap out of the field and the keyboard is closed, until you do the above repaint.
I've stripped down the resulting webpage and found the following:
- ) removal of "height" from the style attribute of a subsequent <td> table cell element sometimes fixes the problem.
- removal of an <iframe> element from later in the page has also fixed the problem.
Both of these are not consistent and have been found only to work in particular test cases.
Q) Has anyone else had this problem? Q) Do they know the exact cause and fix for this? Q) Is this an acknowledged issue by Firefox for Android? Q) If so, is there a fix around the corner?
Thanx muchly -p
NB -- dismantling the application to not use frames is not a practical option here.
Solução escolhida
We are doing a re-write of our Android application. If your test phone supports installing from non-market locations you can try our work at http://nightly.mozilla.org/
Ler esta resposta no contexto 👍 1Todas as respostas (4)
Try Clearing your Cookies & Cache then Restart Firefox.
- Also update Firefox to the latest version -> Install Firefox on an Android device using Google Play
Check and tell if its working.
Modificado por Hasan a
No, clearing cache and restarting Firefox does not work.
Have tried also with Firefox 10 beta ... still the same issue.
Modificado por pdexter66 a
Solução escolhida
We are doing a re-write of our Android application. If your test phone supports installing from non-market locations you can try our work at http://nightly.mozilla.org/
Thanks K
I installed the nightly build, and it has fixed the problem. I know now the fix is just around the corner :)
Thanks muchly -p