Closed Bug 288871 Opened 19 years ago Closed 19 years ago

Problems entering addresses in new mail composition

Categories

(Thunderbird :: Message Compose Window, defect)

defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: moz-bugzilla2, Assigned: zbraniecki)

References

Details

(Keywords: regression, smoketest)

For the last couple days I've had problems entering addresses on new emails to
the point not where it's impossible. Checking the JavaScript log I see the
following:

XML Parsing Error: no element found
Location:
jar:file:///C:/PROGRA~1/MOZILL~1/chrome/mail.jar!/content/global/autocomplete.xml
Line Number 1, Column 1:

XML Parsing Error: no element found
Location:
jar:file:///C:/PROGRA~1/MOZILL~1/chrome/mail.jar!/content/global/autocomplete.xml
Line Number 1, Column 1:
---
version 1.0+ (20050403) on XP
I'm seeing the same thing with 0403, Win2K.  I'm not sure what is meant by 
reporter's "to the point not where it's impossible" -- I cannot enter address 
information at all; I can't even get the focus into the field to enter a value.
Severity: normal → critical
Flags: blocking-aviary1.1?
Keywords: regression
Not being able to address messages constitutes a blocker.
Severity: critical → blocker
*** Bug 288960 has been marked as a duplicate of this bug. ***
gandalf accidentally removed a bunch of core thunderbird files over the weekend.
Assignee: mscott → gandalf
Keywords: smoketest
yup. patch is comming
Status: NEW → ASSIGNED
just for the record, this is also present on Mac.
OS: Windows XP → All
Hardware: PC → All
*** Bug 289023 has been marked as a duplicate of this bug. ***
*** Bug 289158 has been marked as a duplicate of this bug. ***
I backed out the checkin that caused this so we can get useable trunk builds again. 

Feel free to re-adjust the back out when you've got a better fix.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Hourly builds working good again on XP. Thanks, mscott!
verified fixed with 2005040706-trunk tbird build on linux fc3.
Status: RESOLVED → VERIFIED
Flags: blocking-aviary1.1?
You need to log in before you can comment on or make changes to this bug.