9361 - [PP] Assertion when replying to a message

Status: VERIFIED FIXED

(Core :: DOM: Editor, defect, P3)

Description

[scottputterman]

When I try to reply to a message in Messenger I get the following assertion
which continues to happen over and over again.

          NS_ASSERTION(nodeAsText, "Should have a text node here");


nsDebug::Assertion(const char * 0x01b7d5f4, const char * 0x01b7d5e8, const char
* 0x01b7d5b8, int 441) line 167 + 13 bytes
nsCaret::SetupDrawingFrameAndOffset() line 441 + 38 bytes
nsCaret::RefreshDrawCaret(nsIView * 0x07456f20, nsIRenderingContext & {...},
const nsRect & {x=0 y=0 width=11100 height=75}) line 610 + 8 bytes
nsCaret::Refresh(nsCaret * const 0x07452270, nsIView * 0x07456f20,
nsIRenderingContext & {...}, const nsRect & {x=0 y=0 width=11100 height=75})
line 169
PresShell::RefreshCaret(nsIView * 0x07456f20, nsIRenderingContext & {...}, const
nsRect & {x=0 y=0 width=11100 height=75}) line 1075
PresShell::Paint(PresShell * const 0x07452444, nsIView * 0x07456f20,
nsIRenderingContext & {...}, const nsRect & {x=0 y=0 width=11100 height=75})
line 2049
nsView::Paint(nsView * const 0x07456f20, nsIRenderingContext & {...}, const
nsRect & {x=0 y=0 width=11100 height=75}, unsigned int 128, int & 0) line 286
nsViewManager::RenderView(nsIView * 0x07456f20, nsIRenderingContext & {...},
const nsRect & {x=0 y=0 width=11100 height=75}, nsRect & {x=0 y=0 width=11100
height=9270}, int & 0) line 1279
nsViewManager::RenderViews(nsIView * 0x07455a70, nsIRenderingContext & {...},
const nsRect & {x=0 y=0 width=11100 height=75}, int & 0) line 806
nsViewManager::Refresh(nsIView * 0x07455a70, nsIRenderingContext * 0x07468980,
const nsRect * 0x0012fa80 {x=0 y=0 width=11100 height=75}, unsigned int 1) line
513
nsViewManager::DispatchEvent(nsViewManager * const 0x07452a90, nsGUIEvent *
0x0012fb08, nsEventStatus & nsEventStatus_eIgnore) line 1650
HandleEvent(nsGUIEvent * 0x0012fb08) line 67
nsWindow::DispatchEvent(nsWindow * const 0x07455944, nsGUIEvent * 0x0012fb08,
nsEventStatus & nsEventStatus_eIgnore) line 434 + 10 bytes
nsWindow::DispatchWindowEvent(nsGUIEvent * 0x0012fb08) line 455
nsWindow::OnPaint() line 3003 + 24 bytes
nsWindow::ProcessMessage(unsigned int 15, unsigned int 0, long 0, long *
0x0012fd58) line 2286 + 17 bytes
nsWindow::WindowProc(HWND__ * 0x000d0b52, unsigned int 15, unsigned int 0, long
0) line 503 + 27 bytes
USER32! 77e71ab7()
USER32! 77e71a77()
NTDLL! 77f7624f()

Comment 1

[lchiang]

We'll try this in today's release build to see what happens.  Or, is this only a
problem in the debug build?

Are you using the html compose window or the plain text compose window?  Is this
with the new quoting stuff?

Marking [PP] for now - do you know if Mac and Linux debug builds have this
problem?

Comment 2

[buster]

why is this listed as PP, is it windows only?
assigning to Simon.  M8 or M9?

Comment 3

[scottputterman]

The assertion will only be a problem in the debug build.  I have no idea what
will happen in a release build, if anything, since I can't get passed the
assertion.  I've only tried it on Windows.  As far as I know it's with html.  I
haven't done anything to turn quoting on or off, how can I tell?  The window is
too small when it comes up for me to tell if it's being quoted.

Comment 4

[Simon Fraser [no longer active]]

You should be able to comment out the assertion with no ill effects. I'll figure
out why it happens.

Comment 5

[Simon Fraser [no longer active]]

M8

Comment 6

[Simon Fraser [no longer active]]

I need help getting mail set up to be able to reply to a message. Someone?

Comment 7

[Simon Fraser [no longer active]]

OK, I have a simple, safe fix for this. It's just to comment out the assert
and the line above it.

Comment 8

[Simon Fraser [no longer active]]

Checked in the fix, which was to comment out the assert (which served its
function nicely). As well as a text node, the caret can be in a break node in
that situation.

Comment 9

[sujay]

Can mailqa verify this one please? I'm not set up to do mail.

Comment 10

[lchiang]

suresh or par, can you guys try to reply to a message in the next debug build
you have on Win32 and see if you get this assertion?

Thanks

Comment 11

[ppandit]

VERIFIED using debug build 9/20/1999