85496 - Changing font has no effect on or after preformatted text copied from browser window

Status: VERIFIED INVALID

(MailNews Core :: Composition, defect)

Description

[Ritu Raj Tiwari]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.1+) Gecko/20010612
BuildID:    2001061204

I copy text from a browser window into my mail composition . Now this text
appears in the HTML preformatted tag. The text appears in the composition window
under a different font. Writing anything beyond the copied text continues in the
font of the copied text, which is fine, but if I try to change the font, the
change does not take effect.
Also, this should probably be a separate bug report, but copying text from other
mozilla windows generally introduces an extra newline.

Reproducible: Always
Steps to Reproduce:
1.Start mail composition
2.Copy text from a mozilla window displaying preformatted (<pre></pre>) text
3.Add further text and then try changing the font of the added text

Actual Results:  Font change has no effect

Expected Results:  Font change should take effect

Comment 1

[Joe Francis]

hmm.  If I try this in a mail window, I can't even use the font menu due to a
different bug where many heirarchical menus are disabled on mac.  Trying this in
a composer window works fine for me though.  Can you change the font if you
select text and then change it?  If you are changing the font at an insertion
point, you have to make sure you don't move your selection after you request the
font change but before you type, else your requested change is voided.

Comment 2

[Sheela Ravindran]

change qa ->esther

Comment 3

[Keyser Sose]

Makring INVALID based on comments and lack of response.

Comment 4

[Kathleen :Brade]

although I can't check this bug in mail compose (see bug #92799), I tried to
reproduce it in Composer and I can change the font just fine.
verified

Comment 5

[Ritu Raj Tiwari]

Changing font works but copying  such text introduces erroneous newlines before
and after the pasted text. I would consider the current behaviour far from
acceptable. Would you guys reopen this bug or should I file a separate bug?

-Tiwari

Comment 6

[Kathleen :Brade]

Tiwari--what you are describing is completely different from the initial bug
reported.  The intial report does mention the bug you are referring to but it
says that issue should be in a separate bug report.  In fact, it is (probably
reported many times).  Sorry I don't have a bug # handy.  It may be on jfrancis'
plate.