GNOME Bugzilla – Bug 665633
Synchronize bookmarks with Firefox Sync
Last modified: 2017-08-07 10:32:42 UTC
It's cool to see all the work going on with Epiphany for GNOME 3 recently, and I'd like to give it a shot if it all turns out well. However, there's one big stumbling block: I am now utterly and completely dependent on Firefox's Awesomebar to find *anything at all*, and that's heavily dependent on my browsing history. Fortunately, Mozilla have kindly created the whole Firefox Sync / Weave system: https://developer.mozilla.org/en/Firefox_Sync which in typical Mozilla fashion is completely F/OSS and documented from both ends. It ought to be relatively easy to give Epiphany the ability to synchronize with Firefox Sync and hence share my bookmarks and browsing history (and even tabs) between Epiphany and Firefox, across multiple systems. That would make me significantly more likely to test and potentially regularly use Epiphany. It also provides extremely useful functionality to Epiphany: having your browser history 'magically' update across multiple devices is great. Filing under 'General' as I'm not sure what component is correct. (reference https://bugzilla.gnome.org/show_bug.cgi?id=658789 , a similar feature request for gnome-keyring to support the password sync bit of Firefox Sync).
also filed against epiphany-extensions as bug 658831... not sure where it belongs
Huh. I searched for "firefox sync" site:bugzilla.gnome.org and it didn't turn up that bug at all.
Hi, the bookmarks code has been rewritten from scratch. When you have a convenient opportunity to test the new version of the code (which will be present in Epiphany 3.23.1) please check to see if your issue is still a problem, and reply here. Thanks!
Welp, AFAICS it still doesn't have this feature, right?
Actually bookmarks sync via Firefox Sync should be landing very soon, certainly before the next release and possibly even today. Hence I'm going to (slightly-optimistically) mark this as fixed. History is a totally separate issue and really needs to be a separate bug (but you don't really need to file one, it's coming regardless).