Open Bug 1685014 Opened 4 years ago Updated 1 year ago

If sync is enabled it should be explicitly loaded before making a change that should be synced

Categories

(Firefox :: about:logins, defect, P3)

defect

Tracking

()

People

(Reporter: markh, Unassigned)

Details

(Whiteboard: SACI)

Because sync delays initializing itself for ~ 10 seconds after startup, there's a chance it will miss new passwords or changes made in this time - and worse, it's unlikely to ever sync the change. The simplest solution is probably to just explicitly check if sync is initialized, and if not, initialize it, before sending the notification sync observes. It's probably rare that this happens, but I'm sure it does.

(See also bug 1684405; I don't think that is a dupe because the new login did make it after an explicit sync, but that prompted me to open this)

Severity: -- → S3
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.