1408364 - Consider using PlacesUtils.history.fetch to implement history.getVisits

Status: NEW

(WebExtensions :: General, enhancement, P3)

Description

[Masatoshi Kimura [:emk]]

Quoting from bug 1406594 comment #11:
> A separate question though, could getVisits use PlacesUtils.history.fetch
> instead, with the includeVisits option? That API is async and thus better,
> though it may be missing some of the properties you are looking for. In
> particular visitId and referringVisitId. We could expose that info, even if
> I was honestly trying to stop exposing visit ids. An API should never expose
> raw database details. And I don't see where these ids are used by the
> chrome.history API, I cannot find any method that takes a VisitItem or a
> visit id. A visit can be completely identified by url, transition and time.
> Btw, it's a possibility we can evaluate.