Last Comment Bug 1213674 - Complete the implementation of chrome.bookmarks
: Complete the implementation of chrome.bookmarks
Status: NEW
[bookmarks]triaged
: dev-doc-needed
Product: Toolkit
Classification: Components
Component: WebExtensions: General (show other bugs)
: unspecified
: Unspecified Unspecified
P3 normal with 6 votes (vote)
: ---
Assigned To: Bob Silverberg [:bsilverberg]
:
: Andy McKay [:andym]
Mentors:
Depends on: 1251657 1316297 1319530 1208907 1213675 1221764 1225743 1251244 1251269 1252250 1253652 1254608 1296401
Blocks: webextensions-chrome-gaps
  Show dependency treegraph
 
Reported: 2015-10-11 08:24 PDT by Tom Schuster [:evilpie]
Modified: 2017-02-09 17:31 PST (History)
7 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: 48.1 - Mar 21
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description User image Tom Schuster [:evilpie] 2015-10-11 08:24:28 PDT

    
Comment 1 User image Andy McKay [:andym] 2015-10-13 13:46:53 PDT
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
Comment 2 User image Jerry Krinock 2016-05-30 11:04:06 PDT
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
Comment 3 User image Andy McKay [:andym] 2016-05-30 11:42:10 PDT
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 User image Jerry Krinock 2016-05-30 13:27:24 PDT
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.
Comment 5 User image Andy McKay [:andym] 2017-02-09 17:31:43 PST
Dropping priority down to match the dependents.

Note You need to log in before you can comment on or make changes to this bug.