Closed Bug 568363 Opened 14 years ago Closed 14 years ago

Form data removed on one client isn't removed on others, after syncing

Categories

(Firefox :: Sync, defect)

x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 564296

People

(Reporter: jgriffin, Unassigned)

Details

When form data is removed on client1, using either nsIFormHistory2.removeEntry(), or via "Clear form history for X hours" in the UI, and then Weave is synced to client1 and client2, the deleted form history is not removed from client2.

I don't fully understand all the Weave code, but I did a little debugging.  When nsIFormHistory2.removeEntry() is called, Weave's FormTracker.observe() is called with the appropriate notification, e.g. the data parameter is something like:

 {"args":["testing","failure"],"func":"removeEntry","type":"after"}

However, on client2, in FormStore.applyIncoming(), there are no incoming records with a 'deleted' field.  So it looks like something is not hooked up somewhere, but I'm not sure where.
This is known, and related to trunk API revs.
Target Milestone: --- → 2.0
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.