[tracking] Complete the implementation of chrome.bookmarks

NEW
Unassigned

Status

()

Toolkit
WebExtensions: General
P3
normal
2 years ago
a month ago

People

(Reporter: evilpie, Unassigned)

Tracking

(Depends on: 3 bugs, Blocks: 1 bug, {dev-doc-needed})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [bookmarks]triaged)

Comment hidden (empty)
(Reporter)

Updated

2 years ago
Depends on: 1213675

Comment 1

2 years ago
As per: https://developer.chrome.com/extensions/bookmarks

Not implemented:


    getRecent()
    search()
    removeTree() (remove also removes non-empty folders)
    onCreated
    onRemoved
    onChanged
    onMoved
    onChildrenReordered
    onImportBegan
    onImportEnded
    BookmarkTreeNodeUnmodifiable

Updated

2 years ago
Whiteboard: [bookmarks]

Updated

2 years ago
Flags: blocking-webextensions-
(Reporter)

Updated

2 years ago
Depends on: 1221764
Depends on: 1225743

Updated

a year ago
Whiteboard: [bookmarks] → [bookmarks]triaged
Assignee: nobody → bob.silverberg
Iteration: --- → 47.3 - Mar 7
Depends on: 1251244
Blocks: 1251269
No longer blocks: 1251269
Depends on: 1251269
Depends on: 1252250
Depends on: 1251657
Depends on: 1253652
Iteration: 47.3 - Mar 7 → 48.1 - Mar 21
Depends on: 1254608

Comment 2

a year ago
That's wonderful that support for chrome.bookmarks is coming along.  However, Firefox bookmarks contain additional features which are not supported by chrome.bookmarks, for example Tags, so-called "annotations" Keyword and Description, and then there are Smart bookmarks and Live bookmarks (livemarks).

I think that, in order for me to someday write a WebExtension to replace my current Firefox extension, chrome.bookmarks will need additional functions to support these Firefox-only bookmarks features, because the old API which I and others use (nsINavBookmarksService, nsIAnnotationService, nsITaggingService, nsINavHistoryService, mozIAsyncLivemarks, etc.) are not going to be available in a WebExtension.

Is that correct, and if so should I file another bug or is this already a known issue?

Thanks!

Jerry
Please see bug 1225916 for an example. If there's more you'd like to see implemented please file bugs (and or give us some patches).

Comment 4

a year ago
Thank you, Andy.

Because it is reasonable that Mozilla may prefer to obsolete the Firefox-only bookmarks features instead of supporting them, I'd like the need for the additional functions to be accepted before I work on a patch :)  Therefore, I have just now submitted Bug 1276731 and shall wait to see its discussion.
Keywords: dev-doc-needed
Depends on: 1296401

Updated

8 months ago
Component: WebExtensions: Untriaged → WebExtensions: General
Flags: blocking-webextensions-
Priority: -- → P2
Depends on: 1316297
Depends on: 1319530

Comment 5

4 months ago
Dropping priority down to match the dependents.
Priority: P2 → P3
Unassigning myself as this is a tracking bug.
Assignee: bob.silverberg → nobody
Summary: Complete the implementation of chrome.bookmarks → [tracking] Complete the implementation of chrome.bookmarks
You need to log in before you can comment on or make changes to this bug.