mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #33] chrome: Hangs at "Checking..." #31
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#31
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 @hrehfeld on GitHub (Nov 2, 2017).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/33
I can't get the current build of the chrome extension to connect to my server.
I put the following in the account panel:
I also tried
The account panel is also very buggy when you add more than one account.
Extension debugging shows nothing (literally nothing).
Google Chrome | 62.0.3202.75 (Official Build) (64-bit)
Bookmarks 0.10.1
@marcelklehr commented on GitHub (Nov 2, 2017):
Hey @hrehfeld,
I'm sorry it doesn't work for you. Regarding extension debugging, you'll need to inspect the options page, instead of the background page. If that's the problem, could you post the redacted console log of the options page?
Thanks for the hint on multi-account usage, I'll check that out.
@hrehfeld commented on GitHub (Nov 3, 2017):
Hmm, for some reason it seems to work after either a chrome restart or debugging the button view (?) No idea, I don't think I changed anything
@github-actions[bot] commented on GitHub (Mar 21, 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.