Closed Bug 686366 Opened 14 years ago Closed 14 years ago

Canceling Sign In wizard page triggers "Weave is not defined" error

Categories

(Firefox :: Sync, defect)

defect
Not set
minor

Tracking

()

VERIFIED FIXED
mozilla9

People

(Reporter: InvisibleSmiley, Assigned: InvisibleSmiley)

References

Details

(Whiteboard: [verified in services])

Attachments

(1 file)

Found this in SM and FF. If we find a better solution together I'll back-port that one to SM instead. :-) Error: Weave is not defined Source File: chrome://browser/content/syncSetup.js Line: 621 STR: 1. Set Up Sync 2. Connect 3. I don't have the device with me 4. Cancel Reasons: 1. Weave object not available in the context anymore 2. Wrong condition checked for dialog cancel You know the code better than me, maybe you'll find a reason to keep the old !error check.
Attachment #559898 - Flags: review?(philipp)
Comment on attachment 559898 [details] [diff] [review] patch [Checkin: comment 2] Thanks for tracking this down! const'ing JPAKE_ERROR_USERABORT outside the onAbort callback makes sense because onAbort might be called if the window context (and hence the 'Weave' object) is already gone, but I think it's a good idea to document in a small comment. r=me with that. If you have commit privs, please land this on services-central.
Attachment #559898 - Flags: review?(philipp) → review+
Attachment #559898 - Attachment description: patch → patch [Checkin: comment 2]
(In reply to Philipp von Weitershausen [:philikon] from comment #1) > I think it's a good idea to document in a small comment. FTR, the comment I added reads "When onAbort is called, Weave may already be gone". > If you have commit privs, please land this on services-central. Done. If anything else needs to be done to drive this into mozilla-central, please go ahead since I'm not too involved in that.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
(In reply to Jens Hatlak (:InvisibleSmiley) from comment #3) > Done. If anything else needs to be done to drive this into mozilla-central, > please go ahead since I'm not too involved in that. Thanks for landing! We merge s-c weekly to m-c. RESOLVED FIXED means that it's in m-c, so I'm reopening the bug until that happens.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Whiteboard: [fixed in services]
Status: REOPENED → ASSIGNED
Blocks: 686740
following the STR's from the initial report I am not able to reproduce this bug on m-c. Is the reported error in the error console? Is it platform specific?
(In reply to Tracy Walker [:tracy] from comment #5) > Is the reported error in the error console? Yes. > Is it platform specific? Maybe. It may also occur in other cases when manually aborting the setup wizard in the "I already have a Firefox Sync account" branch.
explored around this and could not turn up the bug on Mac nor Win 7 verified s-c I hope reporter can verify on nightly tomorrow.
Whiteboard: [fixed in services] → [verified in services]
Status: ASSIGNED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla9
(In reply to Tracy Walker [:tracy] from comment #7) > I hope reporter can verify on nightly tomorrow. Verified with 2011-09-22 nightly.
Status: RESOLVED → VERIFIED
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: