Return to Answer

From 2015 to 2019, you could disable this feature manually via chrome://flags/#disable-pull-to-refresh-effect - opened directly from the URL bar.

Since 2019, Google made pull-to-refresh mandatory. The update to Chrome 75 removed this flag. See https://support.google.com/chrome/thread/8152831/missing-android-chrome-75-flags-disable-pull-to-refresh-effect-how-to-disable-it-now

One of the proposed solutions below in css seems to be working though:

html { 
  touch-action: pan-down
}

At the time of writing you could disable this feature via chrome://flags/#disable-pull-to-refresh-effect - open directly from your device.

But Google removed this flag with Chrome 75, so this is no longer an option.

From 2015 to 2019, you could disable this feature manually via chrome://flags/#disable-pull-to-refresh-effect - opened directly from the URL bar.

Since 2019, Google made pull-to-refresh mandatory. The update to Chrome 75 removed this flag.

You could try to catch touchmove events, but chances are very slim to achieve an acceptable result.

From 2015 to 2019, you could disable this feature manually via chrome://flags/#disable-pull-to-refresh-effect - opened directly from the URL bar.

Since 2019, Google made pull-to-refresh mandatory. The update to Chrome 75 removed this flag. See https://support.google.com/chrome/thread/8152831/missing-android-chrome-75-flags-disable-pull-to-refresh-effect-how-to-disable-it-now

One of the proposed solutions below in css seems to be working though:

html { 
  touch-action: pan-down
}

At the moment you can only disable this feature via chrome://flags/#disable-pull-to-refresh-effect - open directly from your device.

You could try to catch touchmove events, but chances are very slim to achieve an acceptable result.

From 2015 to 2019, you could disable this feature manually via chrome://flags/#disable-pull-to-refresh-effect - opened directly from the URL bar.

Since 2019, Google made pull-to-refresh mandatory. The update to Chrome 75 removed this flag.

You could try to catch touchmove events, but chances are very slim to achieve an acceptable result.