Closed Bug 810187 Opened 12 years ago Closed 12 years ago

Importing a calendar with a slow network connection and clicking save multiple times can sometimes result in multiple of the same account being added

Categories

(Firefox OS Graveyard :: Gaia::Calendar, defect, P2)

ARM
Gonk (Firefox OS)
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 810153
B2G C2 (20nov-10dec)

People

(Reporter: jsmith, Assigned: jlal)

References

Details

(Whiteboard: [interaction])

Build

Device - Unagi

Hashes

  <project name="gaia" path="gaia" remote="b2g" revision="7ffd1c81db16bf0c6c3285a46259411d603109ca"/>
  <project name="releases-mozilla-aurora" path="gecko" remote="mozilla" revision="f059d3668a1acdeca0fac3c489205edcbe3c8779"/>

Steps

1. Import a calendar on a slow network connection and click save a few times
2. Check the calendar listing

Expected

There should be one set of calendars imported for that account. No duplicates should appear from one import.

Actual

If I get frustrated by the perceived performance issue seen in bug 810153 and hit save a few times, I've a case twice where a bunch of duplicate calendar entries get created. If I try to delete the dups, I end up finding out that I can only delete one instance, not the others.
Actually, I'll change my comment I made in bug 810153 - I'm noming this bug as well, although it's possible fixing bug 810153 may fix this bug as well.
blocking-basecamp: --- → ?
blocking-basecamp: ? → +
Priority: -- → P2
Milestoning for C2 (deadline of 12/10), as this meets the criteria of "known P2 bugs found before or during C1".
Target Milestone: --- → B2G C2 (20nov-10dec)
Assignee: nobody → jlal
Whiteboard: [interaction]
The fix for 810153 is to implement a semi-blocking account setup which will resolve this issue as well. I am going to make this as duplicate ( feel free to correct me here ) because the fix is identical to that other issue.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
blocking-basecamp: + → ---
You need to log in before you can comment on or make changes to this bug.