Closed Bug 1316297 Opened 8 years ago Closed 7 years ago

Implement remaining bookmarks.onImportBegan and onImportEnded WebExtensions API events

Categories

(WebExtensions :: Compatibility, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED INACTIVE

People

(Reporter: bsilverberg, Assigned: mstriemer)

References

(Blocks 1 open bug)

Details

(Whiteboard: [bookmarks]triaged)

Bug #1221764 implements onCreated, onChanged, onMoved and onRemoved, which are the most commonly used events. Based on the Chrome spec [1], there are still a few missing: - onChildrenReordered - onImportBegan - onImportEnded [1] https://developer.chrome.com/extensions/bookmarks
I looked into Chrome's onChildrenReordered event, and I don't think it would ever fire from Firefox. As per the docs [1], and my testing, it never fires as the result of manually executing a move, even if you are using the UI to reorder child bookmarks in a folder. The only time it fires is if you use the "Reorder by Title" menu item that appears in a submenu under "Organize" from the Bookmark Manager. I do not think Firefox has an equivalent function, and therefore the case that would cause onChildrenReordered to fire could never happen in Firefox. Do you agree, Kris? [1] https://developer.chrome.com/extensions/bookmarks#event-onChildrenReordered
Flags: needinfo?(kmaglione+bmo)
Yeah. Maybe we should just implement it as a stub.
Flags: needinfo?(kmaglione+bmo)
Updating this to only be about implementing onImportBegan and onImportEnded.
No longer depends on: 1221764
Priority: -- → P3
Summary: Implement remaining chrome.bookmarks events → Implement remaining bookmarks.onImportBegan and onImportEnded WebExtensions API events
Whiteboard: [bookmarks] → [bookmarks]triaged
Presumably this would mean implementing bookmarks.import and export
Assignee: nobody → mstriemer
Not really. Even without those API methods, import and export functions can be invoked by a user, which would then result in these events firing. In fact, Chrome doesn't even have import or export methods in their bookmarks API [1], so this would not be a matter of Chrome parity, but rather would be new APIs if we were to implement them. [1] https://developer.chrome.com/extensions/bookmarks
Fair enough then, let's skip those methods and focus on the events.
(In reply to Bob Silverberg [:bsilverberg] from comment #1) > I looked into Chrome's onChildrenReordered event, and I don't think it would > ever fire from Firefox. As per the docs [1], and my testing, it never fires > as the result of manually executing a move, even if you are using the UI to > reorder child bookmarks in a folder. The only time it fires is if you use > the "Reorder by Title" menu item that appears in a submenu under "Organize" > from the Bookmark Manager. I do not think Firefox has an equivalent > function, and therefore the case that would cause onChildrenReordered to > fire could never happen in Firefox. Do you agree, Kris? > > [1] > https://developer.chrome.com/extensions/bookmarks#event-onChildrenReordered Hello, in the bookmarks manager (library) I can right click on a bookmarks folder and choose "order by name" (in italian it's "ordina per nome"). Isn't this exactly the same function as "Reorder by Title" in Chrome?
(In reply to Tortino from comment #7) > > Hello, > in the bookmarks manager (library) I can right click on a bookmarks folder > and > choose "order by name" (in italian it's "ordina per nome"). > Isn't this exactly the same function as "Reorder by Title" in Chrome? Thanks Tortino, you are correct. I was actually corrected about this by Marco several months ago in bug 1319530 which I opened to track the implementation of bookmarks.onChildrenReordered.
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INACTIVE
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.