Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Text field entry doesn't work on some ASP.Net webpages

  • 4 replies
  • 4 have this problem
  • 9 views
  • Last reply by pdexter66

more options

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.

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.

Chosen solution

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/

Read this answer in context 👍 1

All Replies (4)

more options

Try Clearing your Cookies & Cache then Restart Firefox.

Check and tell if its working.

Modified by Hasan

more options

No, clearing cache and restarting Firefox does not work.

Have tried also with Firefox 10 beta ... still the same issue.

Modified by pdexter66

more options

Chosen Solution

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/

more options

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