5 ms·

I really hope they improve also tab sync - for some reason it usually doesn't work (or better yet it works but I see tabs from months ago, which is quite useles

I really hope they improve also tab sync - for some reason it usually doesn't work (or better yet it works but I see tabs from months ago, which is quite useless)

yoklov 8y ago
It shouldn’t unless your device is unable to sync for some reason. You may have error logs in one of your firefoxes at about:sync-log. Either way it’s probably worth either filing a bug or asking in #sync in mozilla IRC.
- gilrain 8y ago
  I'd just like to say, as kindly as possible, that this is another thing that drove me away from Firefox. There is so much community support! ...but it's always of the "works here, have you tried rebooting" school of thought. The classic is deleting your profile, that unique Firefox troubleshooting standby. As if regularly nuking all of your browser personalizations to fix inconsistent bugs is at all acceptable even if it did work.
  - yoklov 8y ago
    Yeah, sorry. I worked on tab sync and the debugging process would be involved enough that it’s not practical to do over HN comments. In practice there are a couple concrete things that can cause this, and but all should be reported in about:sync-log. Not sure how to help more specifically than that.
- ktosobcy 8y ago
  Yeah, there is an error there, but it's quite... uninformative: ``` 1525534353618 Sync.Resource WARN GET request to https://sync-591-us-west-2.sync.services.mozilla.com/1.5/90483772/info/collections https://sync-591-us-west-2.sync.services.mozilla.com/1.5/904... failed: [Exception... "Abort" nsresult: "0x80004004 (NS_ERROR_ABORT)" location: "<unknown>" data: no] No traceback available 1525534353620 Sync.ErrorHandler ERROR Sync encountered an error: [Exception... "Abort" nsresult: "0x80004004 (NS_ERROR_ABORT)" location: "<unknown>" data: no] No traceback available 1525534353622 Sync.SyncScheduler DEBUG Next sync in 3600000 ms. (why=reschedule) 1525534353628 Sync.Service DEBUG Exception calling anonymous function: [Exception... "Abort" nsresult: "0x80004004 (NS_ERROR_ABORT)" location: "<unknown>" data: no] No traceback available ``` Probably bugtrack route will be the best
gilrain 8y ago
This is literally what switched me back to Chrome on Android. When I want to continue browsing from another device, Chrome is always up to date. With Firefox, they were always at least a few hours out of date, and often up to days. And either there was no way to manually refresh, or it didn't work... can't remember. This is a feature I use mainly when I've just left my computer but need to continue reading, so the list being up to date is paramount. In a few hours, I'll have moved on or gone back to my desktop.
- yoklov 8y ago
  We sync tabs and history more aggressively than we used to now. Among other times, se do a quick tab sync when you put your laptop to sleep or etc. Still not as aggressive as chrome though, which uses a push-based system, but much improved from the past.

I really hope they improve also tab sync - for some reason it usually doesn't work (or better yet it works but I see tabs from months ago, which is quite useless)

yoklov 8y ago

It shouldn’t unless your device is unable to sync for some reason. You may have error logs in one of your firefoxes at about:sync-log. Either way it’s probably worth either filing a bug or asking in #sync in mozilla IRC.

gilrain 8y ago
I'd just like to say, as kindly as possible, that this is another thing that drove me away from Firefox. There is so much community support! ...but it's always of the "works here, have you tried rebooting" school of thought. The classic is deleting your profile, that unique Firefox troubleshooting standby. As if regularly nuking all of your browser personalizations to fix inconsistent bugs is at all acceptable even if it did work.
- yoklov 8y ago
  Yeah, sorry. I worked on tab sync and the debugging process would be involved enough that it’s not practical to do over HN comments. In practice there are a couple concrete things that can cause this, and but all should be reported in about:sync-log. Not sure how to help more specifically than that.
ktosobcy 8y ago
Yeah, there is an error there, but it's quite... uninformative: ``` 1525534353618 Sync.Resource WARN GET request to https://sync-591-us-west-2.sync.services.mozilla.com/1.5/90483772/info/collections https://sync-591-us-west-2.sync.services.mozilla.com/1.5/904... failed: [Exception... "Abort" nsresult: "0x80004004 (NS_ERROR_ABORT)" location: "<unknown>" data: no] No traceback available 1525534353620 Sync.ErrorHandler ERROR Sync encountered an error: [Exception... "Abort" nsresult: "0x80004004 (NS_ERROR_ABORT)" location: "<unknown>" data: no] No traceback available 1525534353622 Sync.SyncScheduler DEBUG Next sync in 3600000 ms. (why=reschedule) 1525534353628 Sync.Service DEBUG Exception calling anonymous function: [Exception... "Abort" nsresult: "0x80004004 (NS_ERROR_ABORT)" location: "<unknown>" data: no] No traceback available ``` Probably bugtrack route will be the best

gilrain 8y ago

This is literally what switched me back to Chrome on Android. When I want to continue browsing from another device, Chrome is always up to date. With Firefox, they were always at least a few hours out of date, and often up to days. And either there was no way to manually refresh, or it didn't work... can't remember. This is a feature I use mainly when I've just left my computer but need to continue reading, so the list being up to date is paramount. In a few hours, I'll have moved on or gone back to my desktop.

yoklov 8y ago
We sync tabs and history more aggressively than we used to now. Among other times, se do a quick tab sync when you put your laptop to sleep or etc. Still not as aggressive as chrome though, which uses a push-based system, but much improved from the past.