Closed Bug 255956 Opened 21 years ago Closed 20 years ago

odd inconsistencies related to character encoding

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: automaticbox, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 Changing font attributes via Edit > Preferences > General > Fonts and colors under 'Unicode' doesn't affect anything. Changing them under 'Western' does. Sort of hard to explain, I'll detail it better in the 'steps to reproduce' Reproducible: Always Steps to Reproduce: 1. Go to Edit > Preferences > General > Fonts & Colors 2. Make sure the encoding is Western 3. Change the font size for "Proportional" to 24 (arbitrary large number) - sites such as slashdot.org and gmail.com will now have size 24 font. 4. Go to View > Character Encoding and select "Unicode" 5. Notice how the font size is still 24, though if you check in "Fonts & Colors," you'll notice that the size isn't set to 24, it's set to the default (12) Another Test To See This: 1) Go to slashdot.org 2) Make sure you've set your character encoding to "Unicode" via Edit > Character Encoding 3) Go to Edit > Preferences > General > Fonts & Colors and change the font size for "Proportional" to something very large and make sure it's under "Western." 4) Notice how the font on slashdot.org changes, even though it's set to "Unicode" and the font size attribute is only for "Western" Actual Results: Attributing "Western" font sizes/faces for all the encodings. Expected Results: Attribute the font sizes/faces correctly for different encodings.
Product: Browser → Seamonkey
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.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.