Bug 1678607 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Instead of using onItemChanged("tags") we should have a dedicated notification for tags.

Ideally it could be a simple "tags-changed" notification, passing an up-to-date list of tags, but some analysis should be done to check if the list of tags is something we get for free (or cheap), if it's something the consumer would fetch regardless, or if we'd have to fetch them.
We could also go with tags-added and tags-removed, but it seems more work for consumers if at the same time some is removed and some is added.

The notification should probably derive from the PlacesBookmark event
Instead of using onItemChanged("tags") we should have a dedicated notification for tags.

Ideally it could be a simple "bookmark-tags-changed" notification, passing an up-to-date list of tags, but some analysis should be done to check if the list of tags is something we get for free (or cheap), if it's something the consumer would fetch regardless, or if we'd have to fetch them.
We could also go with tags-added and tags-removed, but it seems more work for consumers if at the same time some is removed and some is added.

The notification should probably derive from the PlacesBookmark event
Instead of using onItemChanged("tags") we should have a dedicated notification for tags.

Ideally it could be a simple `bookmark-tags-changed` notification, passing an up-to-date list of tags, but some analysis should be done to check if the list of tags is something we get for free (or cheap), if it's something the consumer would fetch regardless, or if we'd have to fetch them.
We could also go with tags-added and tags-removed, but it seems more work for consumers if at the same time some is removed and some is added.

The notification should probably derive from the PlacesBookmark event

Back to Bug 1678607 Comment 0