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!

Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

Scrolling only works when long pressing on content and then scroll

  • 1 réponse
  • 2 ont ce problème
  • 1 vue
  • Dernière réponse par 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?

Solution choisie

I found the culprit:

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

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (1)

Znert
Znert Auteur de la question
more options

Solution choisie

I found the culprit:

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