119565 - Bold text comes back after hitting enter

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[sujay]

using 1/11 build of netscape



1) launch netscape
2) jump to above URL
3) bring that page into editor
4) scroll down to "Employee Comments" under Valued Work Behaviors
5) add a line underneath "Employee Comments" so you can start typing something

at this point Employee Comments is still not showing as bold

6) now click above next to Employee Comments
7) hit enter

Poof! Now everything is bold!

I can reproduce this..Lisa can also...

Comment 1

[kinmoz]

Sujay, we should probably attatch a *minimal* test case, that doesn't refer to 
any internal aol document or content. I believe in this specific case it's a 
<b><p>foo</p></b> problem right?

Comment 2

[sujay]

yes that is the problem...we can remove the URL now..

Comment 3

[TucsonTester1]

I tested this problem out earlier today and everything worked as was previously
stated.  I couldn't even unbold the text after I selected it and then tried to
select the  bold button on the toolbar with the text selected.  It was pretty
consistent.  But before I filed a report, I went to lunch, and when I came back
and tried it again, I can now select the text and unbold it, which I was not
able to do earlier today.  Now it is consistent is seems now I can unbold it.

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420