The New Tab Override addon would like access to synchronized tab data so it can offer this info as part of a customized new tab. Not sure if there should be a bug about exposing all synchronized data in general, but this one is about tab data specifically.

I'd be happy to be involved with the design of how this data is exposed.

Hi Eric, this has been added to the agenda for the October 3 WebExtensions APIs triage. Would you be able to join us? Agenda: https://docs.google.com/document/d/1X5RmNq2tGC5Aw3npIKqxB2vhnVhg9uOoXh2TggduTPU/edit# Wiki: https://wiki.mozilla.org/Add-ons/Contribute/Triage#Next_Meeting

I'll try to be there to give some Sync input and broader storage context, Caitlin.

I won't attend the triage meeting, so I want to explain the use case for New Tab Override. The legacy add-on of New Tab Override supported "about:sync-tabs" as new tab page because there were some users which wanted to see the synced tabs as new tab page. Mozilla removed about:sync-tabs in Firefox 55. But with an API to access the synced tabs I could re-implement such a view as part of New Tab Override.

This all sounds good and the feedback from the meeting was overwhelming positive. The main questions were around implementation details of how we'd actually do that. So if you do want to take this bug on, please work with :rnewman or others to figure out where the back end data source is at. To work on this bug, we'd probably need to work out how authentication works as well. That could be bug 1343170 or perhaps something more complicated.

Pretty sure bug 1308059 covers this. Andy, can you confirm ?

or Eric

That API: "The list of sessions.Device objects for each synced session, sorted in order from device with most recently modified session to device with least recently modified session. tabs.Tab objects are sorted by recency in the windows.Window of the sessions.Session objects." If it was implemented the same way, yes it sounds like it would.

Well, that cuts down the required design work :D