As per: https://developer.chrome.com/extensions/bookmarks
removeTree() (remove also removes non-empty folders)
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?
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).
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.
Dropping priority down to match the dependents.