Open Bug 1414791 Opened 8 years ago Updated 3 years ago

Consider enforcing `allowSkippedRecord` for incoming records

Categories

(Firefox :: Sync, enhancement, P3)

Product:
Firefox
Component:
Sync
Type:
enhancement

Tracking

()

People

(Reporter: lina, Unassigned)

Details

The bookmarks engine currently sets `allowSkippedRecord` to `true`, meaning we'll fail the sync if a record failed to upload. Once we have structured application, we might consider doing the same for incoming records. There's not much value in doing this now, since we operate on Places directly, and the damage is already done by the time we see a bad record. That said, even with buffering, we still don't want one bad record to block syncing forever. It's also more likely that a failed upload will succeed on the next sync, while a corrupt or invalid record that's already on the server will keep failing. But it's worth thinking about.
(In reply to Kit Cambridge (he/him) [:kitcambridge] from comment #0) > The bookmarks engine currently sets `allowSkippedRecord` to `true`... I meant "false".
Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.