Closed
Bug 129926
Opened 24 years ago
Closed 24 years ago
Trunk crash when using Spell Check in Composer
Categories
(SeaMonkey :: Composer, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: jaimejr, Unassigned)
Details
(Keywords: crash, dataloss)
Build ID: 2002030804
Reproducible: Always
Steps:
1. Launch the browser
2. Open a local File, load a URL, or Compose a new document
3. Select Edit Page (crtl+E) from the File menu
4. Edit the document
5. Click on the Spell Check button
6. Run through Spell Check choosing to Ignore, IgnoreAll, Replace, or Replace
All to idntified words
Results: Crash!
| Reporter | ||
Comment 1•24 years ago
|
||
Nominating for nsbeta1 because this is a very reproducible crash, using a
visible function of Composer. (Note: This crash requires ME to use 4.x to edit
docs, because I can not Spell Check my work).
btw - For some reason, when I search http://climate.mcom.com/main/talkback.cfm
for reports by jaimejr, I can never find the stack traces. There should be at
least 3 stack traces to help in resolving this one.
Comment 3•24 years ago
|
||
I can't reproduce this with windows commercial build 2002-03-11-05-trunk.
Spellchecker is working properly for me.
I also just installed 3/11 build and I cannot reproduce this either
Jaime, please update your build and try again...
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•