mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #2053] cant scroll down when picking a sync method on step 0 #1372
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#1372
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JunkyardCat on GitHub (Sep 7, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2053
Which version of floccus are you using?
5.7.0 fdroid
How many bookmarks do you have, roughly?
0
Are you using other means to sync bookmarks in parallel to floccus?
no
Sync method
WebDAV
Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.
none
Which version of Nextcloud Bookmarks are you using? (if relevant)
none
Which version of Nextcloud? (if relevant)
none
What kind of WebDAV server are you using? (if relevant)
none
Describe the Bug
im using android 12 crdroid 8.7
so when i first started the floccus app it shows me step 0 and a list of option but i cant scroll down
Expected Behavior
i should be able to scroll down
To Reproduce
open the app and try to scroll down
Debug log provided
@github-actions[bot] commented on GitHub (Sep 7, 2025):
Hello! 👋
Thank you for taking the time to open this issue with floccus. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud which leaves me with less time for side projects like this one than I used to have. I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general is a place where people meet to make software better together. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already. You can find donation options at https://floccus.org/donate/. Thank you!
One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself.
Thank you for reading through this primer. I look forward to working with you on this issue! Cheers! 💙
@marcelklehr commented on GitHub (Sep 13, 2025):
Hi @JunkyardCat
Can you find out your version of the webview app? if that one is not up to date, floccus cannot display stuff correctly it seems.
@AndrewPy commented on GitHub (Sep 14, 2025):
The same problem occurs with Lineage OS 16 (Android 9). You cannot scroll anywhere in the app.
Floccus 5.6 works fine, but 5.7 does not.
If the cause is an outdated webview version, you may want to mark the app as incompatible with older Android versions or custom ROMs, as no webview updates are available for them.
@marcelklehr commented on GitHub (Sep 14, 2025):
@yougotwill Would you mind having a look at this? It seems our changes to the scrolling behavior are causing issues here
@marcelklehr commented on GitHub (Sep 14, 2025):
My guess is that the .native-scroll-container is missing a
height: 100%, but I cannot really test this, I think.@marcelklehr commented on GitHub (Sep 14, 2025):
@JunkyardCat @AndrewPy Could you still let us know your webview versions?
@AndrewPy commented on GitHub (Sep 14, 2025):
With Lineage OS 16, I have webview version 96.0.4664.104
@yougotwill commented on GitHub (Sep 15, 2025):
Will give this a look over the weekend 🙏
@marcelklehr commented on GitHub (Sep 19, 2025):
Could also be that the inset property is not supported by those old webview versions yet?
@2Kaleb commented on GitHub (Oct 10, 2025):
@marcelklehr FYI, also happening in Floccus Android App on an AYN Gaming Handheld.
Android 13
Floccus apk 5.7.0 from F-Droid
Android System WebView 109.0.5414.123
@marcelklehr commented on GitHub (Dec 3, 2025):
Could you try this again in the latest version?
@AndrewPy commented on GitHub (Dec 4, 2025):
I tried Floccus 5.8.1 with Lineage OS 16, but unfortunately there was no improvement.
@Bidonh commented on GitHub (Dec 9, 2025):
FYI I can't scroll anymore with floccus 5.8.2 on ios 15.8.5
@marcelklehr commented on GitHub (Dec 20, 2025):
Can you please test again with v5.8.3 once it's available via your favorite channel?
@2Kaleb commented on GitHub (Dec 22, 2025):
Yes, it scrolls for me now on 5.8.3. thank you.