Ovo će web mjesto raditi na ograničen način, dok obavljamo održavanje stranice. Ako neki članak ne riješi tvoj problem i ako želiš postaviti pitanje, naša zajednica za podršku spremna je pomoći na Twitteru @FirefoxSupport i na Redditu /r/firefox.

Avatar for Username

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Ova tema je arhivirana. Postavi novo pitanje ako trebaš pomoć.

Scrolling only works when long pressing on content and then scroll

  • 1 odgovor
  • 2 imaju ovaj problem
  • 3 prikaza
  • Posljednji odgovor od 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?

Izabrano rješenje

I found the culprit:

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

Pročitaj ovaj odgovor u kontekstu 👍 0

Svi odgovori (1)

Znert
Znert Vlasnik pitanja
more options

Odabrano rješenje

I found the culprit:

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