Closed Bug 119381 Opened 24 years ago Closed 21 years ago

javascript strict warnings and error in abMailListDialog.js, moving list dialog

Categories

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

x86
Windows ME
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: nbaca, Assigned: Morten)

Details

Trunk build 2002-01-10-03:WinMe Overview: JavaScript Console reports: "Error: rowGroup.setAttribute is not a function Source File: chrome://messenger/content/addressbook/abMailListDialog.js Line: 608" after creating a new list and moving the list away from the address book window. Steps to reproduce: 1. Open the address book 2. Resize the address book smaller and move it to the right of the screen. 3. Create a new list 4. Move the list dialog to the left so it does not touch the address book window Actual Results: It reports the javascript error. Expected Results: No javascript error should appear.
There are both errors and warnings in this file. Using build 20020111: Warning: reference to undefined property rowGroup.setAttribute Source File: chrome://messenger/content/addressbook/abMailListDialog.js Line: 608 Error: rowGroup.setAttribute is not a function Source File: chrome://messenger/content/addressbook/abMailListDialog.js Line: 608
Summary: javascript strict warnings in abMailListDialog.js, moving list dialog → javascript strict warnings and error in abMailListDialog.js, moving list dialog
I'll take a look at this
Assignee: racham → Morten
Status: NEW → ASSIGNED
hmm, unable to reproduce this right now, but I'll take a closer look at this later...
unable to reproduce now, marking as fixed
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
No patch / bug identified that might have fixed this. ->WORKSFORME
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → WORKSFORME
v
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.