mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #975] please make floccus work on the new firefox for android #634
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#634
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 @gothmog123 on GitHub (Sep 30, 2021).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/975
Is your feature request related to a problem? Please describe.
no, currently most addons are disabled on the new firefox for android rewrite. however, addons can be force enabled and a lot of them do work but not floccus. after clicking on create new account with nextcloud, nothing happens.
Describe the solution you'd like
please make it work
Describe alternatives you've considered
using the nextcloud bookmarks app
@marcelklehr commented on GitHub (Sep 30, 2021):
Hello @gothmog123
Thank you for your feedback. This is not trivial as firefox for android does not support some of the APIs that floccus needs (as well as other extensions dealing with bookmarks), which make it work on dektop browsers. If the firefox team one day decides to implement these missing APIs, floccus will work automatically.
Also see #3, #861 and #962 for context and other solutions.
@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.