Closed Bug 120854 Opened 24 years ago Closed 23 years ago

Strange color handling editing list

Categories

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

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED
Future

People

(Reporter: selmer, Assigned: mozeditor)

Details

(Whiteboard: EDITORBASE+)

Attachments

(1 file)

1/14/02 03 trunk build I will attach a slightly edited version of the email where this happened. Forward the email to a new recipient. Change the (1)...(13) list by highlighting and hitting the bullet list button. Edit the list by positioning at the end of each item, hitting return, hitting the indent button, entering text, hitting return, enter more text. Notice that the new lines keep the foreground color of the top-level list. Continue doing this through the list from top to bottom. About 1/3 to 1/2 of the way through the list, the foreground color switches to black for no apparent reason. After a few more lines have been edited, the color suddenly switches back to using the foreground color of the list.
Note: Save the message to a file and then open it in composer. Highlight the () list and hit the bullet list button. Notice that it creates a single list _above_ the selected text and does *not* change the selected text into a bullet list!
reassign to editor
Assignee: ducarroz → kin
Component: Composition → Editor: Core
Keywords: mailtrack
Product: MailNews → Browser
QA Contact: sheelar → sujay
Using 2002022003 build on WinXP is see the following behavior: I select highlight "Demonstrates Functional Competence" then hit the bullet list item and it doesn't make "Demonstrates Functional Competence" a list item, Instead it makes all of the other items in the list bullet items. Nominating for EDITORBASE.
Whiteboard: EDITORBASE
Target Milestone: --- → mozilla1.0.1
If I remove the font tags, works fine. If I use our composer to create this content, i.e., I use composer to style the UL or OL, it applies the style to each li. So, Kevin and I believe the this is a case where it won't be encountered by users *creating* such content with composer, only if working with externally generated content will they see this. Hence, EDITORBASE- since our primary customer is editing content that he or she created with composer.
Whiteboard: EDITORBASE → EDITORBASE-
Priority: -- → P3
Target Milestone: mozilla1.0.1 → Future
We think this may be fixed now, please retest
Assignee: kin → jfrancis
Keywords: qawanted
QA Contact: sujay → beppe
Whiteboard: EDITORBASE- → EDITORBASE+
using a current trunk build, I cannot reproduce this bug. Marking verified
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
really marking verified
Status: RESOLVED → VERIFIED
Keywords: qawanted
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: