Closed Bug 60633 Opened 25 years ago Closed 24 years ago

javascript strict warnings in fieldMapImport.js

Categories

(SeaMonkey :: MailNews: Address Book & Contacts, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: bugzilla, Assigned: racham)

Details

Attachments

(1 file)

JavaScript strict warning: chrome://messenger/content/fieldMapImport.js line 79: assignment to undeclared variable body JavaScript strict warning: chrome://messenger/content/fieldMapImport.js line 80: assignment to undeclared variable count
reassigning to chuang.
Assignee: putterman → chuang
QA Contact: esther → nbaca
Attached patch proposed patch — — Splinter Review
Keywords: patch
Keywords: review
r=timeless
Keywords: review → approval
mscott, can you sr=?
sr=mscott
Fix checked in.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
verified with build 20010126 on win2k
Status: RESOLVED → VERIFIED
JavaScript strict warning: chrome://messenger/content/fieldMapImport.js line 500: reference to undefined property body.childNodes[i].firstChild.firstChild.firstChild.checked BTW: Is the correct procedure to reopen or to open a brand new bug. I heard a lot of people saying both...?
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
I think some people don't like having bugs that are assigned to them reopened when someone else breaks the code and/or the reason for reopening differs from the original bug report. In the case of these javascript warnings reopening them seems the correct approach to me.
Keywords: approval, patch
over to racham, chuang is gone.
Assignee: chuang → racham
Status: REOPENED → NEW
Reporter: Can you please reconfirm the strict warning in comment #8 above? I just looked at http://lxr.mozilla.org/seamonkey/source/mailnews/import/resources/content/fieldMapImport.js and there aren't 500 lines in that file anymore... If this strict warning is reproducible, it should show up as line 479. I'd like to see a testcase, please. :)
Closing for lack of activity and a reproducible testcase. If you can see these strict warnings, please feel free to REOPEN and provide the testcase, please. :)
Status: NEW → RESOLVED
Closed: 25 years ago → 24 years ago
Resolution: --- → INVALID
Verified Invalid.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: