Closed Bug 365275 Opened 19 years ago Closed 19 years ago

[@ nsHTMLTextFieldAccessible::Shutdown] Pressing the Find In Page 'Cancel' after a successful 'Find in Page' crashes Seamonkey

Categories

(SeaMonkey :: UI Design, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 359924

People

(Reporter: se014a0001, Unassigned)

References

()

Details

(Keywords: crash)

Crash Data

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061209 SeaMonkey/1.5a Build Identifier: I have tried most builds later than the current one (2006120908) The summary says it all. I find it hard to believe this isn't a duplicate, since it has afflicted all the Windows builds I have tried later than 2006120908, but the Duplicate Bug Search is useless. I either get loads of irrelevant bugs, or nothing at all. The problem doesn't affect the Linux builds. Reproducible: Always Steps to Reproduce: 1. Open a page in the browser, eg. http://news.bbc.co.uk 2. Find in page 'news' 3. Cancel Find In Page Actual Results: Seamonkey crashes Expected Results: Find window disappears
Works for me, SeaMonkey 2006122708 on Windows Vista RC2. Do you have an incident ID for your crash? http://kb.mozillazine.org/Quality_Feedback_Agent
If I have the right things: TB27825090X TB27823829E TB27823604X TB27823562X TB27823464M These were all with build 2006122708. The OS was Windows XP Home SP2, the machine was a Lenovo N100. TB27824520M was slightly different; just editing the text in the Find box. This was build 2006122309.
Keywords: crash
Summary: Pressing the Find In Page 'Cancel' after a successful 'Find in Page' crashes Seamonkey → [@ nsHTMLTextFieldAccessible::Shutdown] Pressing the Find In Page 'Cancel' after a successful 'Find in Page' crashes Seamonkey
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Component: XP Apps: GUI Features → UI Design
Crash Signature: [@ nsHTMLTextFieldAccessible::Shutdown]
You need to log in before you can comment on or make changes to this bug.