bugzilla.mozilla.org will be intermittently unavailable on Saturday, March 24th, from 16:00 until 20:00 UTC.

mail.quoted_graphical regression



MailNews: Message Display
15 years ago
13 years ago


(Reporter: R.L. Olive, Unassigned)


Windows 2000

Firefox Tracking Flags

(Not tracked)



(1 attachment)



15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030827
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030827

In version 1.4 I went to about:config and set mail.quoted_graphical = false so I
would see the message text "as is" instead of it converting '>' to '|'.  Now
(after upgrading to 1.5b) it seems to ignore that field and the greater than
sign is now being shown as both "| >" when the message source only has ">". 
This is a problem because I have diffs emailed to me and, as you may know, diff
uses '>' char to show where lines were inserted.

At first, this may seem like a trivial problem, but consider that I have to read
diffs for my job, and Mozilla Mail is modifying the content of my email against
my wishes.

Reproducible: Always

Steps to Reproduce:
1. Put an email in your inbox with '>' char(s) at the beginning of some lines.
2. Pull up the about:config page and changed mail.quoted_graphical from true to
3. Load the email in question.
4. Observe what happens to the '>' characters.

Actual Results:  
> becomes | >

Expected Results:  
> should be left unchanged

example email:

The text diff is also shown below:

<<< file 1:
>>> file 2:
-----[after 10 inserted 11]-----
> import com.cisco.mwg.sgm.commonUI.DialogUtils;
-----[deleted 107-109 after 107]-----
<         Set interestedMessages = new HashSet();
<         interestedMessages.add(new Integer(ObserverMessage.KEEPALIVE));
-----[111 changed to 109-110]-----
<                             interestedMessages, _svrRspHandler, true, 
>                             ObserverMessage.BASIC_MESSAGES, _svrRspHandler, 
>                             true, // give me updates now


15 years ago
Summary: mail.quoted_graphical → mail.quoted_graphical regression

Comment 1

15 years ago
Unable to duplicate this symptom with this morning's build:
  Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6a) Gecko/20030923

Comment 2

15 years ago
I removed all traces of Mozilla and my profile and installed last night's build
and this seems to be working now.  It must've been related to the overlay
install of 1.5b on top of 1.4.  I'm now running:

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6a) Gecko/20030924
Last Resolved: 15 years ago
Resolution: --- → WORKSFORME

Comment 3

15 years ago
Rats.  Now it's doing it again.  I don't know what changed.  I may have changed
a couple of preferences that are conflicting...?  I'll try to get more details.
Resolution: WORKSFORME → ---

Comment 4

15 years ago
Created attachment 132065 [details]
My prefs.js file now that it's not displaying correctly.

Comment 5

15 years ago
I think I found out something.  I was using the Walnut 1.5 theme and that
triggers this bug.  Using Classic or Modern works fine.  I don't know if this is
a bug in Mozilla that is triggered by this theme or if this is bug in the them.

What's the next step for this bug?  Maybe sspitzer knows.

Comment 6

15 years ago
Contact the Walnut developers and have them check into this.
I don't have the answer to your problem, but I would like to make a remark:
this theme contains syndrome of a similar bug 76126.  The syndrome is that even
if I specify variable-width font for plain-text emails, fixed-width is
nevertheless used.
So, it seems that this theme doesn't respect all Preferences.
Product: Browser → Seamonkey


13 years ago
Assignee: sspitzer → mail
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 15 years ago13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.