Closed Bug 225068 Opened 22 years ago Closed 22 years ago

Freezes on webmail site's compose/send mail page when I type/tab in "to:", "subject:" fields

Categories

(Core :: DOM: Core & HTML, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: goldtech, Unassigned)

References

()

Details

(Keywords: hang, regression)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6a) Gecko/20031030 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6a) Gecko/20031030 On fastmail.fm webmail web site. I login, then select compose (ie. compose and send an email), page loads, just at the point were I am enetering address to send- to field and email subject fields keying and tabbing in those fields presented by the webmail page; the Moz. window and all other open Moz. windows freeze. An "end program- not responding" box pops-up after attemps to close/end moz. it may freeze also. cntl-alt-del via task manager then I can close Moz. Happens on home and work pc's w/Moz. 1.6a- very HW different configs too. Never happened w/Moz. 1.5, IE, Opera. Reproducible: Always Steps to Reproduce: 1. Get free account at fastmail.fm 2. Hit "Compose" button - brings you to editor to compose/send an email message 3. Start entering email address, and subject line in fields Actual Results: Mozilla freezes. Expected Results: No freeze. Expected smooth fast operation. As noted above, never happened w/Moz. previous versions. Started w/1.6a Thanks
Severity: normal → critical
Keywords: hang, regression
-> DOM Level 0 Confirmed. This only happens on trunk builds, 1.5 is unaffected. In SeaMonkey I get a dialog stating that a script is taking a long time to execute, so perhaps the script is going into an infinite loop somewhere? Still, it's odd that the loop didn't happen in earlier builds. I attempted to debug in Venkman but for some reason the trunk build would only load part of the scripts, and not the portion that I suspected contained the bug. 1.5 loaded the entire script, but of course debugging there wasn't useful since it didn't exhibit the bug. I created a test account with the site, username and password are moz_test.
Assignee: general → general
Status: UNCONFIRMED → NEW
Component: Browser-General → DOM Level 0
Ever confirmed: true
QA Contact: general → ian
please see bug 225289.
Depends on: 225289
ditto
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.