starred/floccus
1
0
Fork 0
mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-25 22:26:06 +03:00
Code Issues 167 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #593] Floccus "Debug Logs" button does nothing #410

New issue
Closed
opened 2026-02-25 22:37:04 +03:00 by kerem · 11 comments
kerem commented 2026-02-25 22:37:04 +03:00
Owner
Copy link

Originally created by @primesun on GitHub (Jul 6, 2020).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/593

Describe the bug
Clicking on the "Debug Logs" button does nothing. It does not show any debug logs.

To Reproduce
Steps to reproduce the behavior:

  1. Click on 'Debug Logs'

Expected behavior
Debug logs are shown

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser Firefox
  • Browser Version 78.0.1
  • Floccus version: 4.2.5
  • Floccus sync method: nextcloud folders

Server (please complete the following information):

  • OS: Shared hosting, some flavour of Linux
  • Nextcloud version: 16.0.8
  • Bookmarks app version: 2.3.4

Debug log
Debug log button does nothing!

  • Debug log provided
Originally created by @primesun on GitHub (Jul 6, 2020). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/593 **Describe the bug** Clicking on the "Debug Logs" button does nothing. It does not show any debug logs. **To Reproduce** Steps to reproduce the behavior: 1. Click on 'Debug Logs' **Expected behavior** Debug logs are shown **Desktop (please complete the following information):** - OS: Windows 10 - Browser Firefox - Browser Version 78.0.1 - Floccus version: 4.2.5 - Floccus sync method: nextcloud folders **Server (please complete the following information):** - OS: Shared hosting, some flavour of Linux - Nextcloud version: 16.0.8 - Bookmarks app version: 2.3.4 **Debug log** Debug log button does nothing! - [ ] Debug log provided
kerem commented 2026-02-25 22:37:04 +03:00
Author
Owner
Copy link

@marcelklehr commented on GitHub (Jul 19, 2020):

Mh, that's weird. Maybe downloads are saved to the downloads folder for you automatically. Can you check that folder?

<!-- gh-comment-id:660685027 --> @marcelklehr commented on GitHub (Jul 19, 2020): Mh, that's weird. Maybe downloads are saved to the downloads folder for you automatically. Can you check that folder?
kerem commented 2026-02-25 22:37:04 +03:00
Author
Owner
Copy link

@primesun commented on GitHub (Jul 26, 2020):

Could not find any debug logs in the download folder.

<!-- gh-comment-id:663923757 --> @primesun commented on GitHub (Jul 26, 2020): Could not find any debug logs in the download folder.
kerem commented 2026-02-25 22:37:04 +03:00
Author
Owner
Copy link

@cracket commented on GitHub (Aug 28, 2020):

I have similar problem with floccus ver 4.3.0 running on FF 79 on Ubuntu Linux with WebDav account. After error with sync the UI shows status "Syncing" along with greyed out button "Cancel Sync". "Debug Logs" button is blue and changes mouse cursor, so I assume it is active, but does not cause any action.

Tried to enable about:debugging for floccus and read out console errors from "This Firefox" (sorry I'm not a js expert, so not sure if they are relevant) which I attach below:


Content Security Policy: The page’s settings blocked the loading of a resource at eval (“script-src”). options.js:7:125206


UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code. ExtensionStorageIDB.jsm:831
    normalizeStorageError resource://gre/modules/ExtensionStorageIDB.jsm:831
    method chrome://extensions/content/child/ext-storage.js:273
    AsyncFunctionThrow self-hosted:688


Uncaught (in promise) Error: An unexpected error occurred undefined
    dispatch moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:26
    (Async: promise callback)
    dispatch moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:26
    dispatch moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:26
    dispatch moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:20
    onGetLogs moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:20
    onGetLogs self-hosted:935
    Ut moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    a moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    Ut moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    $emit moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    click moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:20
    click self-hosted:935
    Ut moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    a moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    _wrapper moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    (Async: EventListener.handleEvent)
    ue moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    oi moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    _e moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    x moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    m moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    ln moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    _update moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    e moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    get moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    ma moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    mount moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    $mount moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    init moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    m moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    m moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    g moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    m moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    g moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    m moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    g moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    m moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    ln moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    _update moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    e moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    get moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    ma moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    mount moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    $mount moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    init moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7
    m moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7

I assume the button should work no matter if synchronization is in progress?

<!-- gh-comment-id:682261093 --> @cracket commented on GitHub (Aug 28, 2020): I have similar problem with floccus ver 4.3.0 running on FF 79 on Ubuntu Linux with WebDav account. After error with sync the UI shows status "Syncing" along with greyed out button "Cancel Sync". "Debug Logs" button is blue and changes mouse cursor, so I assume it is active, but does not cause any action. Tried to enable about:debugging for floccus and read out console errors from "This Firefox" (sorry I'm not a js expert, so not sure if they are relevant) which I attach below: ``` Content Security Policy: The page’s settings blocked the loading of a resource at eval (“script-src”). options.js:7:125206 UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code. ExtensionStorageIDB.jsm:831 normalizeStorageError resource://gre/modules/ExtensionStorageIDB.jsm:831 method chrome://extensions/content/child/ext-storage.js:273 AsyncFunctionThrow self-hosted:688 Uncaught (in promise) Error: An unexpected error occurred undefined dispatch moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:26 (Async: promise callback) dispatch moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:26 dispatch moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:26 dispatch moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:20 onGetLogs moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:20 onGetLogs self-hosted:935 Ut moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 a moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 Ut moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 $emit moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 click moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:20 click self-hosted:935 Ut moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 a moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 _wrapper moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 (Async: EventListener.handleEvent) ue moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 oi moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 _e moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 x moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 m moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 ln moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 _update moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 e moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 get moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 ma moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 mount moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 $mount moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 init moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 m moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 m moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 g moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 m moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 g moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 m moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 g moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 m moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 ln moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 _update moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 e moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 get moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 ma moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 mount moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 $mount moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 init moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 m moz-extension://4fa3ce81-4f85-45d9-85c7-6e5bf28c8079/dist/js/options.js:7 ``` I assume the button should work no matter if synchronization is in progress?
kerem commented 2026-02-25 22:37:04 +03:00
Author
Owner
Copy link

@primesun commented on GitHub (Aug 28, 2020):

@cracket is right. It looks like the floccus extension is using the default content security policy (since it doesn't appear to set one in manifest.json). The default CSP doesn't allow for eval to be used, according to Mozilla. And that is what the error is complaining about, the line in options.js:

buffer = eval('require(\'buffer\').Buffer')

I don't know where options.js is in the repo... (is it created by webpack??)

Edit: Looks like this eval is coming from js-base64, and they fixed it here: https://github.com/dankogai/js-base64/issues/85. Perhaps floccus can be updated to use the newer version of that dependency.

Edit2: Further, I'm not sure if that error we see in the console is actually related to the Debug logs button not working.

<!-- gh-comment-id:682337728 --> @primesun commented on GitHub (Aug 28, 2020): @cracket is right. It looks like the floccus extension is using the default content security policy (since it doesn't appear to set one in [manifest.json](https://github.com/marcelklehr/floccus/blob/develop/manifest.json)). The default CSP doesn't allow for `eval` to be used, [according to Mozilla](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_Security_Policy). And that is what the error is complaining about, the line in options.js: `buffer = eval('require(\'buffer\').Buffer')` I don't know where options.js is in the repo... (is it created by webpack??) Edit: Looks like this eval is coming from js-base64, and they fixed it here: https://github.com/dankogai/js-base64/issues/85. Perhaps floccus can be updated to use the newer version of that dependency. Edit2: Further, I'm not sure if that error we see in the console is actually related to the Debug logs button not working.
kerem commented 2026-02-25 22:37:04 +03:00
Author
Owner
Copy link

@marcelklehr commented on GitHub (Aug 28, 2020):

@asabbagh thanks for the research!

<!-- gh-comment-id:682581296 --> @marcelklehr commented on GitHub (Aug 28, 2020): @asabbagh thanks for the research!
kerem commented 2026-02-25 22:37:04 +03:00
Author
Owner
Copy link

@marcelklehr commented on GitHub (Sep 1, 2020):

UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code. ExtensionStorageIDB.jsm:831

This seems suspicious. Perhaps the database is corrupt for some reason. Could you try reinstalling floccus?

<!-- gh-comment-id:684881395 --> @marcelklehr commented on GitHub (Sep 1, 2020): > UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code. ExtensionStorageIDB.jsm:831 This seems suspicious. Perhaps the database is corrupt for some reason. Could you try reinstalling floccus?
kerem commented 2026-02-25 22:37:04 +03:00
Author
Owner
Copy link

@primesun commented on GitHub (Sep 3, 2020):

I just tried uninstalling and reinstalling floccus.

Immediately after installing I clicked the Debug Logs button but nothing happened. I tried a sync, and it failed (server error 503). But now the Debug Logs button successfully downloaded a log file. A 2nd sync attempt, same failure and error, and the Debug Logs still works and gives a log file. 3rd attempt the sync succeeded, and the button still works too.

So yes it is possible that it was some sort of database corruption. It's not clear why the button did nothing the first time I clicked it before any syncs were completed, but perhaps that is intended behaviour.

Edit: Even though it is likely off topic, I should note that one of the syncs resulted in one of my bookmark folders and its contents being duplicated.

<!-- gh-comment-id:686228583 --> @primesun commented on GitHub (Sep 3, 2020): I just tried uninstalling and reinstalling floccus. Immediately after installing I clicked the Debug Logs button but nothing happened. I tried a sync, and it failed (server error 503). But now the Debug Logs button successfully downloaded a log file. A 2nd sync attempt, same failure and error, and the Debug Logs still works and gives a log file. 3rd attempt the sync succeeded, and the button still works too. So yes it is possible that it was some sort of database corruption. It's not clear why the button did nothing the first time I clicked it before any syncs were completed, but perhaps that is intended behaviour. Edit: Even though it is likely off topic, I should note that one of the syncs resulted in one of my bookmark folders and its contents being duplicated.
kerem commented 2026-02-25 22:37:04 +03:00
Author
Owner
Copy link

@sixtyfive commented on GitHub (Feb 19, 2021):

Hi @marcelklehr, trying to figure out the JSON parsing problem, I also noticed that the "Debug Logs" button does nothing. It's all good now since reinstalling Floccus solved that problem, but if something like it ever happens again, it would surely be helpful to see debug logs and be able to post them here.

<!-- gh-comment-id:781990292 --> @sixtyfive commented on GitHub (Feb 19, 2021): Hi @marcelklehr, trying to figure out the JSON parsing problem, I also noticed that the "Debug Logs" button does nothing. It's all good now since reinstalling Floccus solved _that_ problem, but if something like it ever happens again, it would surely be helpful to see debug logs and be able to post them here.
kerem commented 2026-02-25 22:37:04 +03:00
Author
Owner
Copy link

@marcelklehr commented on GitHub (Feb 19, 2021):

@sixtyfive Oh, that's not good. Please open a new issue with your installation details, so I can reproduce.

<!-- gh-comment-id:781992954 --> @marcelklehr commented on GitHub (Feb 19, 2021): @sixtyfive Oh, that's not good. Please open a new issue with your installation details, so I can reproduce.
kerem commented 2026-02-25 22:37:04 +03:00
Author
Owner
Copy link

@sixtyfive commented on GitHub (Feb 19, 2021):

too late ... shouldn't have tried the reinstallation idea so quickly. if it ever happens again i'll investigate more! sorry, marcel!

<!-- gh-comment-id:782066901 --> @sixtyfive commented on GitHub (Feb 19, 2021): too late ... shouldn't have tried the reinstallation idea so quickly. if it ever happens again i'll investigate more! sorry, marcel!
kerem commented 2026-02-25 22:37:04 +03:00
Author
Owner
Copy link

@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.

<!-- gh-comment-id:1477135267 --> @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.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
dependabot/npm_and_yarn/fast-xml-parser-5.7.0
dependabot/npm_and_yarn/xmldom/xmldom-0.8.13
dependabot/npm_and_yarn/protocol-buffers-schema-3.6.1
master
fix/xml-entity-limit
all-contributors/add-aaryanvangari
fix/subscanner-residuals
test/subscanner-residuals
test/problematic-seeds
perf/improve-build-time
perf/native-startup
fix/continuation-null-cheks
dropbox
fix/clear-indexeddb-after-sync
dependabot/npm_and_yarn/vuetify-3.11.4
fix/slim-down-continuation
test/background-worker
refactor/fail-build-if-native-uses-browser-api
feat/improve-failsafe-wording
dependabot/npm_and_yarn/multi-0520f5abeb
feat/release-build
fix/more-mapping-errors
dependabot/npm_and_yarn/intl-messageformat-10.7.18
enh/split-sync-interval-and-auto-sync
enh/gdrive-timeout
feat/safari
feat/capabilities
feat/xxhash3
feat/murmur3
fix/gdrive-error-handling
fix/correctness-fixes
fix/linkwarden
feat/orion
fix/nocache-tests
feat/tab-groups
fix/git-never-force-push
fix/xbel-parse-errors
fix/git-push-errors
fix/chrome-main-folder-ids
dependabot/npm_and_yarn/multi-a9f852c250
chore/use-local-linkwarden-container-in-ci
all-contributors/add-balthanon
dependabot/npm_and_yarn/multi-7c5da94753
fix/revert-indexeddb-logger
fix/acknowlegde-abuse
dependabot/npm_and_yarn/eslint-import-resolver-webpack-0.13.10
fix/rip-out-continuations
fix/webdav-filesize-depth-header
fix/changes-while-syncing
fix/addition-failsafe-minimum
feat/indexeddb-logs
feat/addition-failsafe
fix/webdav-check-filesize
fix/orion
fix/bounded-exponential-backoff
fix/dont-repeat-on-sync-fail
fix-tests
fix/speedup-tab-update-cb
all-contributors/add-andybalaam
all-contributors/add-macrogreg
fix/parse-tag-value
fix/cleanup-deps
refactor/partial-set-data-with-lock
fix/nc-bookmarks-update
fix/move-stabiltiy-same-titled-folders
fix/ios-share-extension
fix/update-selenium
fix/chrome-net-errors
enh/nc-bm-js
sentry
fix/unidirectional-scanner-shoudl-use-mappings
enh/interrupts
dependabot/npm_and_yarn/vue-loader-17.4.2
ci/build-ios
enh/manifest-v3
release/4.19.0
fix/codeql
fix/google-drive-ios
all-contributors/add-dmotte
fix/unidirectional-sync
fix/interrupts
all-contributors/add-pinpontitit
all-contributors/add-dsiminiuk
test/old-apis
test/interrupts-on-nextcloud-bookmarks
feature/no-hashing-in-diff
feature/improve-diff-performance
capacitor
enh/rename-nextcloud-folders
fix/complex-hierarchy-reversal-2
tests/coverage
feature/google-drive
dependabot/npm_and_yarn/eslint-plugin-vue-7.6.0
fix/crypto
dependabot/npm_and_yarn/sass-1.32.7
dependabot/npm_and_yarn/css-loader-5.0.2
dependabot/npm_and_yarn/webpack-cli-4.5.0
fix/performance-hash-caching
dependabot/npm_and_yarn/eslint-plugin-standard-5.0.0
dependabot/npm_and_yarn/sass-loader-10.1.1
dependabot/npm_and_yarn/eslint-import-resolver-webpack-0.13.0
dependabot/npm_and_yarn/webpack-merge-5.7.3
dependabot/npm_and_yarn/p-queue-6.6.2
dependabot/npm_and_yarn/throttle-debounce-3.0.1
fix/lww-move-test
fix/overwrite-strategy
fix/root-folder-sync
enh/local-hash-cash
test/ci
ui/vue
cookie-hack
fix/travis
rollup
refactor/ui
webdav
refactor/modularize
v5.9.1
v5.9.0
v5.8.6
v5.8.5
v5.8.4
v5.8.3
v5.8.2
v5.8.1
v5.8.0
v5.7.0
v5.6.0
v5.5.6
v5.5.5
v5.5.4
v5.5.3
v5.5.2
v5.5.1
v5.5.0
v5.4.5
v5.4.4
v5.4.3
v5.4.2
v5.4.2-alpha.1
v5.4.1
v5.4.0
v5.3.4
v5.3.3
v5.3.1
v5.3.0
v5.3.0-beta.1
v5.2.7
v5.2.6
v5.2.5
v5.2.4
v5.2.3
v5.2.2
v5.2.1
v5.2.0
v5.2.0-beta.3
v5.2.0-beta.2
v5.2.0-beta.1
v5.1.7
v5.1.6
v5.1.5
v5.1.4
v5.1.3
5.1.3-beta.1
v5.1.2
v5.1.1
v5.1.0
v5.0.12
v5.0.12-beta.1
v5.0.11
v5.0.10
v5.0.9
v5.0.8
v5.0.7
v5.0.6
v5.0.5
v5.0.4
v5.0.3
v5.0.2
v5.0.1
v5.0.0
v4.19.1
v4.19.0
v4.18.1
v4.18.0
v4.17.1
v4.17.0
v4.16.0
v4.15.0
v4.14.0
v4.13.1
v4.13.0
v4.12.0
v4.11.0
v4.11.0-alpha.0
v4.10.1
v4.10.0
v4.9.0
v4.8.7
v4.8.6
v4.8.4
v4.8.3
v4.8.2
v4.8.1
v4.8.0
v4.7.0
v4.6.4
v4.6.3
v4.6.2
v4.6.1
v4.6.0
v4.5.0
v4.4.10
v4.4.9
v4.4.8
v4.4.7
v4.4.6
v4.4.5
v4.4.4
v4.4.3
v4.4.2
v4.4.1
v4.4.0
v4.4.0-rc1
v4.3.0
v4.2.6
v4.2.5
v4.2.4
v4.2.3
v4.2.2
v4.2.1
v4.2.0
v4.2.0-beta.4
v4.2.0-beta.3
v4.2.0-beta.2
v4.2.0-beta.1
v4.1.0
v4.0.4
v4.0.3
v4.0.2
v4.0.1
v4.0.0
v4
v4.0.0-alpha.3
v4.0.0-alpha.2
v4.0.0-alpha.1
v3.5.3
v3.5.2
v3.5.1
v3.5.0
v3.4.2
v3.4.1
v3.4.0
v3.4.0-beta.3
v3.4.0-beta.2
v3.4.0-beta.1
v3.3.2
v3.3.1
v3.3.0
v3.3.0-beta.5
v3.3.0-beta.4
v3.3.0-beta.3
v3.3.0-beta.2
v3.3.0-beta.1
v3.2.16
v3.2.15
v3.2.14
v3.2.13
v3.2.12
v3.2.11
v3.2.10
v3.2.9
v3.2.8
v3.2.7
v3.2.6
v3.2.5
v3.2.4
v3.2.3
v3.2.2
v3.2.1
v3.2.0
v3.1.15
v3.1.14
v3.1.13
v3.1.12
v3.1.11
v3.1.10
v3.1.9
v3.1.8
v3.1.7
v3.1.6
v3.1.5
v3.1.4
v3.1.3
v3.1.2
v3.1.1
v3.1.0
v3.0.10
v3.0.9
v3.0.8
v3.0.7
v3.0.6
v3.0.5
v3.0.4
v3.0.3
v3.0.2
v3.0.1
v3.0.0
v3.0.0-beta.9
v3.0.0-beta.8
v3.0.0-beta.7
v2.2.9
v3.0.0-beta.6
v3.0.0-beta.5
v3.0.0-beta.4
v3.0.0-beta.3
v3.0.0-beta.2
v3.0.0-beta-1
v3.0.0-alpha-1
v2.2.8
v2.2.7
v2.2.6
v2.2.5
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.0
v2.0.6
v2.0.5
v2.0.4
v2.0.3
v2.0.2
v2.0.1
v2.0.0
v2.0.0-beta.2
v1.3.4
v2.0.0-beta.1
v1.3.3
v1.3.2
v1.3.1
v1.3.0
v1.3.0-beta.5
v1.3.0-beta.4
v1.3.0-beta.3
v1.3.0-beta.2
v1.3.0-beta1
v1.2.0
v1.1.2
v1.1.1
v1.1.0
v1.0.1
v1.0.0
Labels
Clear 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

Mirrored from GitHub Pull Request

  
question

   
question

   
stale

   
upstream

   
waiting for more information

   
wontfix

   
🙁 Not following issue template
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#410
No description provided.