OuptutText on Windows has garbage chars at the end of the output string. This is a string termination problem in the routine in nsTextEditor that converts the ostream to an nsString (it might be my bug). The issues is that aInStr.str does not appear to be null-terminated.

M3, P1

We needed to set the length of the nsString to the stream buffer length. [NOTE: This error occurred for OutputHTML as well]

Simon, how would I go about verifying this? Is is just simple text entry? thanks

Hit the 'output text' or 'output HTML' buttons in the editor testbed. Look to see if you see garbage at the end of the console output.

verified in 3/19 builds. Clicking "Get Text" button yields no garbage chars after the text. There is no Output HTML/Text button, so I'm assuming you meant Get Text.

Reassigning all bugs Assigned To kostello to buster

All these bugs were marked "New" when Jan transfered ownership of them to me. They were all resolved and need to be marked "Verified" again.

This was Verified on 03/19/99...resetting back to Verified...Bugzilla wacked out.