mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #838] Bookmark of "chrome://flags/" cannot be synced #537
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#537
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 @gjf on GitHub (Feb 23, 2021).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/838
Describe the bug
I have a bookmark for opening settings of Chromium browser:
chrome://flags/
It does not syncronize.
To Reproduce
Steps to reproduce the behavior:
chrome://flags/Expected behavior
A bookmark should appear on all devices.
Screenshots
N/A
Desktop
(please complete the following information)
Server
(please complete the following information)
Note: Please write down the actual version numbers instead of writing 'latest'.
Debug log
There is no any mention of "chrome://flags/" in neither PC log (which should upload it) nor Android one (which should download it).
Additional context
N/A
@marcelklehr commented on GitHub (Feb 26, 2021):
This is currently by design, as not all browsers support the
chrome://URL scheme@gjf commented on GitHub (Feb 26, 2021):
But Chromium-based does!
Is it possible to remove this "design" in Chromium version of addon?
@marcelklehr commented on GitHub (Mar 10, 2021):
Yes, it's possible. I'll look into this, but I can't promise anything.
@marcelklehr commented on GitHub (Mar 16, 2022):
Fixed
@github-actions[bot] commented on GitHub (Mar 20, 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.