Add-ons devs heads-up: History API removals in Places

This is a re-post from mozilla.dev.extensions to try to reach a broader add-ons developers public.

Dear add-ons developers,
as part of our goal to make history and bookmarks asynchronous, we are starting removing some APIs, that in the last years have been replaced by new asynchronous ones. We are currently removing the last uses in the tests harness, but we are not too far from the target. Current goal is Firefox21.

The work is tracked in https://bugzilla.mozilla.org/show_bug.cgi?id=834457

The following APIs will be removed:

(replaced by mozIAsyncFavicons)
nsIFaviconService::setFaviconUrlForPage
nsIFaviconService::setFaviconData
nsIFaviconService::getFaviconData
nsIFaviconService::getFaviconForPage
nsIFaviconService::setAndLoadFaviconForPage
nsIFaviconService::getFaviconImageForPage
nsIFaviconService::getFaviconDataAsDataURL

(replaced by mozIAsyncLivemarks)
nsILivemarkService::*
PlacesUtils.itemIsLivemark
PlacesUtils.nodeIsLivemarkContainer
PlacesUtils.nodeIsLivemarkItem

(remove only third argument)
PlacesUIUtils.showBookmarkDialog

(no more implemented by Places, use mozIAsyncHistory)
nsIGlobalHistory2::addURI
nsIGlobalHistory2::isVisited
nsIGlobalHistory2::setPageTitle

(no more needed, use onDeleteURI or onItemRemoved)
nsINavHistoryObserver::OnBeforeDeleteURI
nsINavBookmarkObserver::OnBeforeItemRemoved

In addition to this (I will follow-up to the newsgroup asap), the following APIs are also being removed:

(Never implemented properly)
nsINavHistoryFullVisitResultNode

(use mozIAsyncHistory::updatePlaces instead)
nsINavHistoryService::AddVisit

Please let me know (either in the newsgroup or in the bug) if you have doubts, or part of these changes should be blocked for major problems, or there's some use-case you need that is not well-covered by the new APIs.

MaK Martedì 29 Gennaio 2013 at 5:05 pm | | Mozilla-EN