Closed Bug 558268 Opened 14 years ago Closed 14 years ago

Able to Reset Sync during Private Browsing mode

Categories

(Firefox :: Sync, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: tchung, Assigned: mconnor)

Details

(Whiteboard: [weave1.2b5])

Attachments

(4 files, 1 obsolete file)

Attached image Reset Sync screenshot 1
The reset sync option still works in private browsing mode, and will delete all your entries, despite indicating its disabled. 

See screenshots and logfile.

Repro:
1) install weave 1.2b5
2) log into your weave account
3) enter private browsing mode
4) notice it says weave disabled
5) click Weave > Preferences
6) when weave prefpane opens, click Manage Account > Reset sync
7) replace all data option
8) verify it deletes all your bookmarks, but unable to sync all your existing bookmarks.  Should never have reached this step in the first place due to private browsing

Expected:
- Reset Sync features should be disabled in private browsing 

Actual:
- reset sync works, and never recovers my data
nom blocking-1.2?
Severity: normal → major
Flags: blocking-weave1.3?
Flags: blocking-weave1.2?
Whiteboard: [weave1.2b5]
Attached image Reset Sync screenshot 2
Attached file activity log file
i'll add that after existing private browsing in this horked mode already, my normal browsing also all my missing bookmarks and history.
Changes made in private browsing (i.e. to bookmarks, prefs, etc) do persist, so that's expected, at least.  bug 551572 will prevent this case (wipe before we check for PB) already, but we should just disable the manage account expander when PB is active.
Attached patch v1 (obsolete) — Splinter Review
* disable expander, collapse if expanded
Assignee: nobody → mconnor
Status: NEW → ASSIGNED
Attachment #438069 - Flags: review?(edilee)
As a note, this was not as much of an issue before 1.2 because you could only Start Over, and the login fields would be disabled.  Short=circuiting that could lead to this bad UX.

As a note, there is no unexpected dataloss here, the user has explicitly chosen to nuke local data, we just fail to retrieve server data until the first post-PB sync.  It's a pretty bad/confusing user experience though, so we'll fix this for 1.2 (and harden the API against this in 1.3).
Whiteboard: [weave1.2b5] → [weave1.2b5][has patch][needs review Mardak]
Attached patch v1.1Splinter Review
this is belt and suspenders already, but hey, why not add an extra belt!

* if we're in the middle of resetting sync, clear that state and update the prefpane.
Attachment #438069 - Attachment is obsolete: true
Attachment #438071 - Flags: review?(edilee)
Attachment #438069 - Flags: review?(edilee)
Flags: blocking-weave1.3?
Flags: blocking-weave1.2?
Flags: blocking-weave1.2+
Attachment #438071 - Flags: review?(edilee) → review+
Whiteboard: [weave1.2b5][has patch][needs review Mardak] → [weave1.2b5][has patch][has review]
http://hg.mozilla.org/labs/weave/rev/9d75fd9ae6df
Able to Reset Sync during Private Browsing mode, r=Mardak
Severity: major → normal
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Component: Sync → Firefox UI
OS: Mac OS X → All
QA Contact: sync → firefox
Hardware: x86 → All
Resolution: --- → FIXED
Summary: Able to Reset Sync during Private Browsing mode and deletes all data → Able to Reset Sync during Private Browsing mode
Whiteboard: [weave1.2b5][has patch][has review] → [weave1.2b5]
Component: Firefox Sync: UI → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: