[GH-ISSUE #1297] Refresh is triggered to easily and quickly #861

Closed
opened 2026-02-25 22:38:18 +03:00 by kerem · 3 comments
Owner

Originally created by @godfuture on GitHub (Nov 25, 2022).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1297

Which version of floccus are you using?

4.17.1

Sync method

Nextcloud Bookmarks

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Android 12 on Fairphone 3+ Witz lineageOS 19.1

Which version of Nextcloud Bookmarks are you using? (if relevant)

currently latest

Which version of Nextcloud? (if relevant)

24.0.7

What kind of WebDAV server are you using? (if relevant)

Nextcloud 24 with booksmarks app.

Describe the Bug

Scrolling up triggers the sync too easy. Mostly I hit the refresh even though I just wanted to scroll up.

Expected Behavior

The UI should less sensitive to pull down when scrolling. The user should have a good control when to refresh and when not while scrolling the screen. Therefore it needs a certain area of tolerance where the user has to "overscroll" to make the refresh trigger.

To Reproduce

Connect to server
Wait for first sync
Scroll till bottom
Try to scroll till top without triggering refresh

Debug log provided

  • I have provided a debug log file
Originally created by @godfuture on GitHub (Nov 25, 2022). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1297 ### Which version of floccus are you using? 4.17.1 ### Sync method Nextcloud Bookmarks ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Android 12 on Fairphone 3+ Witz lineageOS 19.1 ### Which version of Nextcloud Bookmarks are you using? (if relevant) currently latest ### Which version of Nextcloud? (if relevant) 24.0.7 ### What kind of WebDAV server are you using? (if relevant) Nextcloud 24 with booksmarks app. ### Describe the Bug Scrolling up triggers the sync too easy. Mostly I hit the refresh even though I just wanted to scroll up. ### Expected Behavior The UI should less sensitive to pull down when scrolling. The user should have a good control when to refresh and when not while scrolling the screen. Therefore it needs a certain area of tolerance where the user has to "overscroll" to make the refresh trigger. ### To Reproduce Connect to server Wait for first sync Scroll till bottom Try to scroll till top without triggering refresh ### Debug log provided - [ ] I have provided a debug log file
kerem 2026-02-25 22:38:18 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@marcelklehr commented on GitHub (Nov 26, 2022):

I tend to agree. It would be a nice feature, but implemented like this it's not cool

<!-- gh-comment-id:1328060552 --> @marcelklehr commented on GitHub (Nov 26, 2022): I tend to agree. It would be a nice feature, but implemented like this it's not cool
Author
Owner

@godfuture commented on GitHub (Nov 27, 2022):

I tend to agree. It would be a nice feature, but implemented like this it's not cool

Exactly. Also for users with extend bookmark db size, the sync takes longer. In my case for internal LAN it only syncs with 2 MBits. Dont know why, but somehow there is a bottleneck. If I accidently hit refresh, I always have to wait for sync to finish.

Thanks for your quick help here.

<!-- gh-comment-id:1328287357 --> @godfuture commented on GitHub (Nov 27, 2022): > I tend to agree. It would be a nice feature, but implemented like this it's not cool Exactly. Also for users with extend bookmark db size, the sync takes longer. In my case for internal LAN it only syncs with 2 MBits. Dont know why, but somehow there is a bottleneck. If I accidently hit refresh, I always have to wait for sync to finish. Thanks for your quick help here.
Author
Owner

@github-actions[bot] commented on GitHub (Nov 28, 2023):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

<!-- gh-comment-id:1828907211 --> @github-actions[bot] commented on GitHub (Nov 28, 2023): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/floccus#861
No description provided.