# Broken pull down to reload in Android Chrome

**URL:** https://meta.discourse.org/t/broken-pull-down-to-reload-in-android-chrome/82913
**Category:** Bug
**Created:** [March 13, 2018, 4:17pm UTC](https://meta.discourse.org/t/broken-pull-down-to-reload-in-android-chrome/82913 "2018-03-13T16:17:16Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [March 13, 2018, 4:17pm UTC](https://meta.discourse.org/t/broken-pull-down-to-reload-in-android-chrome/82913/1 "2018-03-13T16:17:16Z")

</div>

Continuing the discussion from [Scroll position issue for topic with 1 unread post](https://meta.discourse.org/t/scroll-position-issue-for-topic-with-1-unread-post/82683/21):

A recent commit broke pull down to refresh in Android Chrome.

It was working in 790c5facc946bd35f569afca3a23241c205c8693, so it’s a change in the last month.

---

<div class="post-metadata">

### Author: ![awesomerobot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/awesomerobot/32/142900_2.png) [@awesomerobot](https://meta.discourse.org/u/awesomerobot)
#### Post date: [March 13, 2018, 4:57pm UTC](https://meta.discourse.org/t/broken-pull-down-to-reload-in-android-chrome/82913/2 "2018-03-13T16:57:57Z")

</div>

ah, that was this

[https://github.com/discourse/discourse/commit/5f133e20f2bf0b051006396eb03f9fed95094b29](https://github.com/discourse/discourse/commit/5f133e20f2bf0b051006396eb03f9fed95094b29)

The reasoning was that the pull to refresh feature can accidentally cause reloads when someone is scrolling up a topic on a slow connection (so the posts aren’t loading fast enough). Fine reverting this if it’s causing issues or there’s a problem with overriding the default browser behavior, it’s currently only supported by Chrome on Android anyway.

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [March 13, 2018, 6:02pm UTC](https://meta.discourse.org/t/broken-pull-down-to-reload-in-android-chrome/82913/3 "2018-03-13T18:02:32Z")

</div>

🤔

I just went to HelloForos in a topic with 1.700 replies, went to the last one, and scrolled top furiously for 400 posts or so.

I never triggered pull down to refresh.

Maybe this only happens when you are indeed in a bad connections, but I’m note sure this is a valid case to override the default browser behavior.

We have a complete valid reason to override the find shortcut and people complain all the time already.

---

<div class="post-metadata">

### Author: ![awesomerobot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/awesomerobot/32/142900_2.png) [@awesomerobot](https://meta.discourse.org/u/awesomerobot)
#### Post date: [March 13, 2018, 6:47pm UTC](https://meta.discourse.org/t/broken-pull-down-to-reload-in-android-chrome/82913/4 "2018-03-13T18:47:27Z")

</div>

> Maybe this only happens when you are indeed in a bad connections, but I’m note sure this is a valid case to override the default browser behavior.

True, the PR asking to implement it was the first I’ve heard someone complain. I was able to reproduce it on a slow connection, but I removed it for now, might not be that big of an issue in practice.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [March 13, 2018, 6:56pm UTC](https://meta.discourse.org/t/broken-pull-down-to-reload-in-android-chrome/82913/5 "2018-03-13T18:56:00Z")

</div>


