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.

Avatar for Username

Cari Bantuan

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.

Pelajari Lebih Lanjut

Utas ini telah diarsipkan. Silakan membuat pertanyaan baru jika Anda membutuhkan bantuan.

Scrolling only works when long pressing on content and then scroll

  • 1 balas
  • 2 memiliki masalah ini
  • 3 kunjungan
  • Balasan terakhir oleh 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?

Solusi terpilih

I found the culprit:

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

Baca jawaban ini dalam konteks 👍 0

Semua Balasan (1)

Znert
Znert Pemilik pertanyaan
more options

Solusi Terpilih

I found the culprit:

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