mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #250] Problem in Firefox when XBEL file contains chrome internal URLs #238
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#238
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 @Schteinbock on GitHub (Mar 28, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/250
Software versions
Steps to reproduce
Expected outcome
Syncing all bookmarks contained in XEBEL file
Actual outcome
Syncing failed with chrome:newtab/ is not a valid URL. Actually there was a corresponding URL contained in the XBEL file, propably (accidentally) created by a Chrome user however I would have expected that either this URL would not have been saved by floccus or skipped by firefox.
Debug log
onSyncStart: begin
https://collab.ohrner-it.com/dav/bookmarks.xbel.lock
https://collab.ohrner-it.com/dav/bookmarks.xbel.lock
Adding folder "Allgemein"
Adding folder "XDIS"
Adding folder "Buildinfrastruktur"
Adding folder "Dokumentation"
Adding folder "Issues"
Adding folder "GSEP"
Adding folder "Entwicklung allg."
Adding folder "Sysadmin"
Syncing failed with chrome:newtab/ is not a valid URL.
onSyncFail
@marcelklehr commented on GitHub (Mar 28, 2019):
Confirmed. Fixed. Bugfix release outstanding.
Thank you for the feedback 🎁 :)
@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.