Closed Bug 26482 Opened 26 years ago Closed 26 years ago

Import Utility, not testable for Address book, mail or setting import

Categories

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

PowerPC
Mac System 8.5
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: esther, Assigned: tonyr)

References

Details

Using build 20000102603m13 on mac I crash when OK'ing the Field mapping window of the Import Utility while importing .txt, .tab or .tab address book files. Using build 2000020414m14 nothing displays in the list area for formats. I'll write up steps after I investigate more.
Adding "crash" keyword.
Keywords: crash
Reassign to tonyr
Assignee: phil → tonyr
Summary: Import Utility, importing .cvs, .txt, .tab abook files crash → Import Utility, importing .cvs, .txt, .tab abook files crash
QA Contact: lchiang → esther
With the latest builds there is a general problem with string bundles being accessed from JS. This is keeping the import UI from working at all on Mac. See bug #26291
Status: NEW → ASSIGNED
Depends on: 26291
Crash is not happening on m14 builds, but utility still isn't testable per comments by tonyr on 2-4. Removing Crash from keywords and summary and changing summary to include Mail and settings.
Keywords: crash
Summary: Import Utility, importing .cvs, .txt, .tab abook files crash → Import Utility, not testable for Address book, mail or setting import
Added a work-around for the string bundle problem. The UI will now operate and will indicate when strings are not obtainable from the string bundle.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Using build 2000-04-01-08 on mac this is working. However, I crash after OK'in the alert that tells me the import was a success (and it really was successfully imported). I think there is a separate bug for crashing on Mac, when closing alert's. I will look for one, if I don't find one I will log a new bug. Verified
Status: RESOLVED → VERIFIED
Depends on: 88583
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.