Closed Bug 656594 Opened 14 years ago Closed 6 years ago

Sync Now button is active even if the Sync is in progress

Categories

(Firefox for Android Graveyard :: General, defect, P2)

ARM
Android
defect

Tracking

(fennec-)

RESOLVED WONTFIX
Tracking Status
fennec - ---

People

(Reporter: xti, Unassigned)

Details

Build id : Mozilla/5.0 (Android;Linux armv7l;rv:6.0a1)Gecko/20110511
Firefox/6.0a1 Fennec/6.0a1
Device: HTC Desire
OS: Android 2.2


Steps to reproduce:
1. Open Fennec App
2. Connect to Sync with a valid sync account/sync code
3. Tap on Details > Sync Now
4. Wait until Sync progress is done

Expected result:
Sync Now button is grayed out until the Sync progress is completed. 

Actual result:
If Sync is in progress for a long time, the Sync Now button will change its state from grayed out to active.

Note:
Even if it is tapped again, there will be no changes in the app, the Sync will be still in progress
Device: Nexus One
Build: Same as above

I was able to reproduce.  I don't understand all the lock logic in the observers in the WeaveGlue object but it looks like the issue could be with the timeout here http://mxr.mozilla.org/mozilla-central/source/mobile/chrome/content/sync.js#441, where the attribute value is flipped on the element
Priority: -- → P2
TC https://litmus.mozilla.org/single_result.cgi?id=427270 fails due to this bug.
And also http://litmus.mozilla.org/single_result.cgi?id=427187
tracking-fennec: --- → ?
Is this still an issue? I ask because the bug is old.
(In reply to comment #4)
> Is this still an issue? I ask because the bug is old.

I'm able to reproduce it on the latest Nightly build. It seems that Sync Now button becomes active and after a couple of seconds it will be automatically grayed out.
Philipp, I assume we'll want to keep this UI ("Sync Now"). Is that true?
Assignee: nobody → mbrubeck
tracking-fennec: ? → +
tracking-fennec: + → -
Assignee: mbrubeck → nobody
Closing all opened bug in a graveyard component
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.