Vanwege onderhoudswerkzaamheden die uw ervaring zouden moeten verbeteren, heeft deze website beperkte functionaliteit. Als een artikel uw probleem niet verhelpt en u een vraag wilt stellen, kan onze ondersteuningsgemeenschap u helpen in @FirefoxSupport op Twitter en /r/firefox op Reddit.

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Text entry on webpage sometimes blocked, cannot see key entry.

  • 1 antwoord
  • 1 heeft dit probleem
  • 3 weergaven
  • Laatste antwoord van Kevin

more options

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

Alle antwoorden (1)

more options