Closed
Bug 183836
Opened 23 years ago
Closed 23 years ago
New list item resets the font and the font size.
Categories
(Core :: DOM: Editor, defect)
Core
DOM: Editor
Tracking
()
VERIFIED
FIXED
People
(Reporter: saari, Assigned: mozeditor)
Details
(Keywords: topembed+, Whiteboard: EDITORBASE+, fixinhand)
Attachments
(1 file)
|
2.98 KB,
patch
|
Brade
:
review+
kinmoz
:
superreview+
|
Details | Diff | Splinter Review |
To reproduce:
- Start a new mail
- Start a bulletted list.
- Change the font to Arial and increase the size. Start typing. The changes are
reflected.
- Type a new line which creates a new list item.
- Type something. The font and size have reverted to the original size.
Another flavor of the same bug:
Change the type and size of the font. Click on the bulleted list icon.
Expected: the type and size is maintained.
Observed: the type and size reverts to the default.
| Assignee | ||
Comment 1•23 years ago
|
||
This fixes a couple of related issues. The first is that new empty <li>'s
weren't picking up the styles from the prior <li> when you typed return. The
second is that when you split a list item (ie, the new <li> isn't empty) the
selection in the new <li> was not being placed inside the leading styles, so if
you typed you would not get any of the styles.
| Assignee | ||
Updated•23 years ago
|
Whiteboard: EDITORBASE+ → EDITORBASE+, fixinhand
Updated•23 years ago
|
Attachment #109149 -
Flags: superreview?(kin)
Attachment #109149 -
Flags: review+
Comment on attachment 109149 [details] [diff] [review]
patch to libeditor
sr=kin@netscape.com
==== Do we want remove one space from the start of the 2nd line in the |if|?
+ if ( (wsType==nsWSRunObject::eSpecial) ||
+ (wsType==nsWSRunObject::eBreak) ||
+ nsHTMLEditUtils::IsHR(visNode) )
Attachment #109149 -
Flags: superreview?(kin) → superreview+
| Assignee | ||
Comment 3•23 years ago
|
||
fix landed on trunk
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
I contacted BT Yahoo to ask them to resolve this problem. They said that the
colour and graphics was only available for IE 4.0 and above (which we know) and
that they had not had this kind of request from any other Firefox users. If
this is the case and not the usual corporate BS, then let's flood them with
requests until they see the error of their ways?
Also, I did try the Harry Patsis fix (see #36) but it did not do the trick. His
auto response said that he will get back to me.
You need to log in
before you can comment on or make changes to this bug.
Description
•