Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

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 entry on webpage sometimes blocked, cannot see key entry.

  • 1 பதிலளி
  • 1 இந்த பிரச்சனை உள்ளது
  • 1 view
  • Last reply by Kevin

I am actually trying to make an existing ASP.Net webpage compliant to use on Firefox for Android.

I am finding that in a lot of cases, text fields will turn blue and the keyboard will show, but typed keys will not show in the text fields, until you click onto another tab of Firefox, then back again (some sort of repaint issue?)

On working webpages, the text fields turn blue then turn white again, with a visible text cursor, and typed characters will show immediately as you type.

It seems to have something to do with frames (both iframes and classic frames).

I've found that if I strip the webpage down to minimal fields and tables, I can restore the typeability, but at the expense of features I need, and which don't always fix the problem, eg

  • the problem seems only to occur when the page is nested in a <frame> or <iframe> element (as source page).
  • in one case I found it was a <td> element in the page *later" than the field at fault, which had a style="height:Npx" setting -- when the height was removed, the field worked.
  • in another case, it was the existence of an <iframe> element that caused the problem, and whose removal fixed the problem.

In both these cases, removing these features doesn't of themselves fix the issue generically (only in the particular test page), and in any case are needed for other features of the webpages.

My questions are a) does anyone else experience this, in which case I can put it down to an issue with Firefox for Android (current version)?

b) if yes to above, does anyone have a definite cause and fix for it?

c) is this an acknowledged problem by Firefox for Android, and is there a fix around the corner?

Cheers p

I am actually trying to make an existing ASP.Net webpage compliant to use on Firefox for Android. I am finding that in a lot of cases, text fields will turn blue and the keyboard will show, but typed keys will not show in the text fields, until you click onto another tab of Firefox, then back again (some sort of repaint issue?) On working webpages, the text fields turn blue then turn white again, with a visible text cursor, and typed characters will show immediately as you type. It seems to have something to do with frames (both iframes and classic frames). I've found that if I strip the webpage down to minimal fields and tables, I can restore the typeability, but at the expense of features I need, and which don't always fix the problem, eg * the problem seems only to occur when the page is nested in a <frame> or <iframe> element (as source page). * in one case I found it was a <td> element in the page *later" than the field at fault, which had a style="height:Npx" setting -- when the height was removed, the field worked. * in another case, it was the existence of an <iframe> element that caused the problem, and whose removal fixed the problem. In both these cases, removing these features doesn't of themselves fix the issue generically (only in the particular test page), and in any case are needed for other features of the webpages. My questions are a) does anyone else experience this, in which case I can put it down to an issue with Firefox for Android (current version)? b) if yes to above, does anyone have a definite cause and fix for it? c) is this an acknowledged problem by Firefox for Android, and is there a fix around the corner? Cheers p

All Replies (1)