Closed
Bug 74147
Opened 24 years ago
Closed 24 years ago
Style button does not stay active after carriage return
Categories
(Core :: DOM: Editor, defect, P3)
Tracking
()
mozilla1.0
People
(Reporter: nbaca, Assigned: mozeditor)
References
Details
(Whiteboard: [behavior])
Build 2001-03-29-04: NT4, Mac 9.04
Build 2001-03-29-08: Linux RH 6.2
Overview: Apply a style to some text (i.e. underline) and press the carriage
return. Notice that the Underline button does not appear enabled.
Steps to reproduce:
1. Open Composer
2. Select the Underline button in the formatting toolbar
3. Type text and notice that the text is underlined and the Underline button
appears enabled.
4. Press Enter (carriage return)
Actual Results: It's difficult to know what will happen when typing begins
because the Underline button appears normal and not selected/highlighted.
- Start typing and the text appears underlined
- Backspace to remove all the text from the second line
- Now try to type new text without the underline by selecting the Underline
button before typing. No matter what I try it always underlines the text.
Expected Results:
- After pressing Enter the formatting toolbar should indicate what type of style
will be applied when typing begins. In this case the Underline button should
appear selected/highlighted.
- If the Underline is not wanted then selecting the Underline button should turn
this style off so when typing begins, only normal text appears.
Comment 1•24 years ago
|
||
testing on build 2001040204, you must hit the underline button twice to turn the
underline off, I also noticed that the style buttons 'lose' the enabled visual
effect until you start typing again, once typing begins the 'enabled' visual
look appears.
Assignee: beppe → jfrancis
Priority: -- → P3
Whiteboard: [behavior]
Target Milestone: --- → mozilla1.0
Comment 3•24 years ago
|
||
*** This bug has been marked as a duplicate of 57053 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•