Closed Bug 158352 Opened 23 years ago Closed 23 years ago

Editor functionality crashes MfcEmbed

Categories

(Core :: DOM: Editor, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

VERIFIED INVALID

People

(Reporter: chak, Assigned: mjudge)

Details

(Keywords: crash)

Attachments

(1 file)

1. Run MfcEmbed and choose "New Editor Window". 2. Type in a few characters into the editor 3. Click on the "B" toolbar button 4. Crashes This used to work fine and seems to have been broken as part of the checkins for #125146.
Possible fix. Should'nt we be passing in a valid nsICommandParams instead of a zero like it's being done now?
No. Passing a null nsICommandParams should be legal for some commands.
Just realized that the prev. patch will not cover all the cases. Looking at the code we may have other potential crashes. For ex, in: CEditorFrame::ExecuteNoParam(const char *aCommand) { return DoCommand(aCommand,0); //<---Passing in 0 here is bad. It will crash. }
Hi Simon : Let me see if i can get a stack trace....thanks
Keywords: crash
Interesting. I've neved been able to get the editor component to work in MFCEmbed.
Trying this on WindowsXP with the 7/19/2002 nightly of MFCEmbed and I can't type anything into the editor window. This has been a fairly consistent behavior of the nightly builds for sometime. Does the nightly not include the necessary files to actually use the editor component?
> Does the nightly not include the necessary files to actually use the editor component? That's possible. I believe that the emebedding manifest fails to include the composer DLL.
crashes.. this parameter that isnt necessary should definately not be crashing. for no parameters now you are supposed to pass in null for the commandparams. if you get a stack trace please let me know
Status: NEW → ASSIGNED
i tested with my latest trunk builds and it does NOT crash anymore. Wonder if something was horked with my (old) source tree. I recently pulled a fresh copy from CVS when i switched to gmake builds. Marking INVALID
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: