| Summary | Forwarding/Reply Quoted HTML Composition |
| Queue | IMP |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 2. Medium |
| Owners | slusarz (at) horde (dot) org |
| Requester | engineer (at) mca (dot) k12 (dot) pa (dot) us |
| Created | 12/15/2006 (6903 days ago) |
| Due | |
| Updated | 12/21/2006 (6897 days ago) |
| Assigned | |
| Resolved | 12/18/2006 (6900 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
Assigned to Michael Slusarz
State ⇒ Resolved
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Forwarding/Reply Quoted HTML Composition
Queue ⇒ IMP
State ⇒ Unconfirmed
default (if browser supports the feature)? " is enabled
When replying or forwarding to an existing message in the message
composition windows, the original message appears as one big paragraph
-- all carriage returns are missing. Prior to the HTML GUI displaying
the message shows correctly in it's plain text but once the HTML GUI
displays, all of the carriage returns are lost.
If "Compose messages with an HTML GUI by default (if browser supports
the feature)? " is disabled and then reply or forward is chosen, the
reply message displays the original message correctly. If switch to
html composition is selected the HTML GUI displays the message with
the carriage returns in tact.
I noticed that when starting with plain text and selecting switch to
HTML on the message composition window, prior to the HTML GUI loading,
all of the lines display a <br />. When the default is set to
compose with HTML, the <br /> do not appear before the HTML GUI is
loaded
In the test messages that I was replying or forwarding, the message
contains both html and plaintext versions of the message. When
selecting Reply To Sender or Froward Entire Message the message is
currently showing html as the primary and plaintext as an alternative
version.