Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Scrolling only works when long pressing on content and then scroll

  • 1 antwurd
  • 2 hawwe dit probleem
  • 1 werjefte
  • Lêste antwurd fan Znert

Znert
Znert
more options

I am currently working on an Angular/Ionic web app, but have trouble with scrolling on Firefox Android.

My issue is, that I cannot scroll any content on the webpage.

So I would like to know how I could debug the app. I'm already using the WebIDE to access my phone and debug Event Listeners (going to Debugger -> side panel -> Events), but it seems that only a few events are listed because I cannot see any listener on any touch events or scroll events that could cause such behaviour.

Any suggestions on what I'm doing wrong here?

I am currently working on an Angular/Ionic web app, but have trouble with scrolling on Firefox Android. My issue is, that I cannot scroll any content on the webpage. So I would like to know how I could debug the app. I'm already using the WebIDE to access my phone and debug Event Listeners (going to Debugger -> side panel -> Events), but it seems that only a few events are listed because I cannot see any listener on any touch events or scroll events that could cause such behaviour. Any suggestions on what I'm doing wrong here?

Keazen oplossing

I found the culprit:

From an older commit there was still some temporary code lying around which listened to touchmove and calling preventDefault.

Dit antwurd yn kontekst lêze 👍 0

Alle antwurden (1)

Znert
Znert Fraacheigener
more options

Keazen oplossing

I found the culprit:

From an older commit there was still some temporary code lying around which listened to touchmove and calling preventDefault.