Open
Bug 1213674
Opened 9 years ago
Updated 1 year ago
[tracking] Complete the implementation of chrome.bookmarks
Categories
(WebExtensions :: General, defect, P3)
WebExtensions
General
Tracking
(Not tracked)
NEW
Iteration:
48.1 - Mar 21
People
(Reporter: evilpie, Unassigned)
References
(Depends on 3 open bugs, Blocks 1 open bug)
Details
(Keywords: dev-doc-complete, meta, Whiteboard: [bookmarks]triaged)
No description provided.
Comment 1•9 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•9 years ago
|
Whiteboard: [bookmarks]
Updated•9 years ago
|
Flags: blocking-webextensions-
Updated•9 years ago
|
Whiteboard: [bookmarks] → [bookmarks]triaged
Updated•9 years ago
|
Assignee: nobody → bob.silverberg
Iteration: --- → 47.3 - Mar 7
Updated•9 years ago
|
Updated•9 years ago
|
Iteration: 47.3 - Mar 7 → 48.1 - Mar 21
Comment 2•8 years 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
Comment 3•8 years ago
|
||
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•8 years 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.
Updated•8 years ago
|
Keywords: dev-doc-needed
Updated•8 years ago
|
Component: WebExtensions: Untriaged → WebExtensions: General
Flags: blocking-webextensions-
Priority: -- → P2
Comment 6•8 years ago
|
||
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
Updated•6 years ago
|
Product: Toolkit → WebExtensions
Comment 7•5 years ago
|
||
Docs looks fairly complete.
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/bookmarks
Keywords: dev-doc-needed → dev-doc-complete
Comment 8•4 years ago
|
||
Is it still planned to implement onImportBegan and onImportEnded? I have an extension that creates a grid of bookmarks and folders and keeps it up-to-date as changes are made to bookmarks. I'm currently using a debounce function to prevent Firefox from locking up during a Restore or Import. That works, but it would be nice to have feature parity with Chrome.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•