Skip to main content
Judging from the comments, most people is coming here to find a way to manually disable pull-to-refresh on the client side. This is not possible anymore. Let's give our readers the answer they are actually looking for.

Google has made pull-to-refresh mandatory. Since Chrome version 75, you can not turn it off.

What you can do to avoid unwanted refreshes is scrolling up slowly and looking at the scroll bar so you can stop scrolling in time before hitting the top of the page.

However, you can opt your own website out of pull-to-refresh.

The default action of the pull-to-refresh effect can be effectively prevented by doing any of the following :

  1. preventDefault’ing some portion of the touch sequence, including any of the following (in order of most disruptive to least disruptive):
  • a. The entire touch stream (not ideal).
  • b. All top overscrolling touchmoves.
  • c. The first top overscrolling touchmove.
  • d. The first top overscrolling touchmove only when 1) the initial touchstart occurred when the page y scroll offset was zero and 2) the touchmove would induce top overscroll.
  1. Applying “touch-action: none” to touch-targeted elements, where appropriate, disabling default actions (including pull-to-refresh) of the touch sequence.
  2. Applying “overflow-y: hidden” to the body element, using a div for scrollable content if necessary.
  3. Disabling the effect locally via chrome://flags/#disable-pull-to-refresh-effect)Disabling the effect locally via chrome://flags/#disable-pull-to-refresh-effect). Only available in Chrome 41 to 74. Removed in Chrome 75.

See more

The default action of the pull-to-refresh effect can be effectively prevented by doing any of the following :

  1. preventDefault’ing some portion of the touch sequence, including any of the following (in order of most disruptive to least disruptive):
  • a. The entire touch stream (not ideal).
  • b. All top overscrolling touchmoves.
  • c. The first top overscrolling touchmove.
  • d. The first top overscrolling touchmove only when 1) the initial touchstart occurred when the page y scroll offset was zero and 2) the touchmove would induce top overscroll.
  1. Applying “touch-action: none” to touch-targeted elements, where appropriate, disabling default actions (including pull-to-refresh) of the touch sequence.
  2. Applying “overflow-y: hidden” to the body element, using a div for scrollable content if necessary.
  3. Disabling the effect locally via chrome://flags/#disable-pull-to-refresh-effect).

See more

Google has made pull-to-refresh mandatory. Since Chrome version 75, you can not turn it off.

What you can do to avoid unwanted refreshes is scrolling up slowly and looking at the scroll bar so you can stop scrolling in time before hitting the top of the page.

However, you can opt your own website out of pull-to-refresh.

The default action of the pull-to-refresh effect can be effectively prevented by doing any of the following :

  1. preventDefault’ing some portion of the touch sequence, including any of the following (in order of most disruptive to least disruptive):
  • a. The entire touch stream (not ideal).
  • b. All top overscrolling touchmoves.
  • c. The first top overscrolling touchmove.
  • d. The first top overscrolling touchmove only when 1) the initial touchstart occurred when the page y scroll offset was zero and 2) the touchmove would induce top overscroll.
  1. Applying “touch-action: none” to touch-targeted elements, where appropriate, disabling default actions (including pull-to-refresh) of the touch sequence.
  2. Applying “overflow-y: hidden” to the body element, using a div for scrollable content if necessary.
  3. Disabling the effect locally via chrome://flags/#disable-pull-to-refresh-effect). Only available in Chrome 41 to 74. Removed in Chrome 75.

See more

added 43 characters in body
linusg
  • 6.4k
  • 4
  • 31
  • 80

The default action of the pull-to-refresh effect can be effectively prevented by doing any of the following :

  1. preventDefault’ingpreventDefault’ing some portion of the touch sequence, including any of the following (in order of most disruptive to least disruptive):
  • a. The entire touch stream (not ideal).
  • b. All top overscrolling touchmoves.
  • c. The first top overscrolling touchmove.
  • d. The first top overscrolling touchmove only when 1) the initial touchstart occurred when the page y scroll offset was zero and 2) the touchmove would induce top overscroll.
  1. Applying “touch-action: none”touch-action: none to touch-targeted elements, where appropriate, disabling default actions (including pull-to-refresh) of the touch sequence.
  2. Applying “overflow-y: hidden”overflow-y: hidden to the body element, using a div for scrollable content if necessary.
  3. Disabling the effect locally via chrome://flags (disable-pull-to-refresh-effectchrome://flags/#disable-pull-to-refresh-effect).

See more

The default action of the pull-to-refresh effect can be effectively prevented by doing any of the following :

  1. preventDefault’ing some portion of the touch sequence, including any of the following (in order of most disruptive to least disruptive):
  • a. The entire touch stream (not ideal).
  • b. All top overscrolling touchmoves.
  • c. The first top overscrolling touchmove.
  • d. The first top overscrolling touchmove only when 1) the initial touchstart occurred when the page y scroll offset was zero and 2) the touchmove would induce top overscroll.
  1. Applying “touch-action: none” to touch-targeted elements, where appropriate, disabling default actions (including pull-to-refresh) of the touch sequence.
  2. Applying “overflow-y: hidden” to the body element, using a div for scrollable content if necessary.
  3. Disabling the effect locally via chrome://flags (disable-pull-to-refresh-effect).

See more

The default action of the pull-to-refresh effect can be effectively prevented by doing any of the following :

  1. preventDefault’ing some portion of the touch sequence, including any of the following (in order of most disruptive to least disruptive):
  • a. The entire touch stream (not ideal).
  • b. All top overscrolling touchmoves.
  • c. The first top overscrolling touchmove.
  • d. The first top overscrolling touchmove only when 1) the initial touchstart occurred when the page y scroll offset was zero and 2) the touchmove would induce top overscroll.
  1. Applying touch-action: none to touch-targeted elements, where appropriate, disabling default actions (including pull-to-refresh) of the touch sequence.
  2. Applying overflow-y: hidden to the body element, using a div for scrollable content if necessary.
  3. Disabling the effect locally via chrome://flags/#disable-pull-to-refresh-effect).

See more

Evyn
  • 1.8k
  • 1
  • 11
  • 2

The default action of the pull-to-refresh effect can be effectively prevented by doing any of the following :

  1. preventDefault’ing some portion of the touch sequence, including any of the following (in order of most disruptive to least disruptive):
  • a. The entire touch stream (not ideal).
  • b. All top overscrolling touchmoves.
  • c. The first top overscrolling touchmove.
  • d. The first top overscrolling touchmove only when 1) the initial touchstart occurred when the page y scroll offset was zero and 2) the touchmove would induce top overscroll.
  1. Applying “touch-action: none” to touch-targeted elements, where appropriate, disabling default actions (including pull-to-refresh) of the touch sequence.
  2. Applying “overflow-y: hidden” to the body element, using a div for scrollable content if necessary.
  3. Disabling the effect locally via chrome://flags (disable-pull-to-refresh-effect).

See more