[10.5] For Arial · isn't recognized on MacOS X 10.5 Leopard

RESOLVED WORKSFORME

Status

()

Firefox
General
RESOLVED WORKSFORME
11 years ago
6 years ago

People

(Reporter: dex_sf, Unassigned)

Tracking

2.0 Branch
PowerPC
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.10) Gecko/20071115 Firefox/2.0.0.10
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.10) Gecko/20071115 Firefox/2.0.0.10

On MacOS X 10.5 Leopard · isn't recognized if the chosen font is Arial, just a square is rendered. The current releases of SeaMonkey and Camino are having the same problem. It works properly for all three products on 10.4 Tiger. Non-Gecko browsers like Safari or Opera don't have the problem. 

Reproducible: Always

Steps to Reproduce:
1. load e.g. http://www.warriorentertainment.com/site.php?se=feature&con=salv_cast

Actual Results:  
For · (Arial) a square is rendered.

Expected Results:  
· should be rendered as middle dot.
confirming, I see this using Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.11pre) Gecko/2007120303 BonEcho/2.0.0.11pre. It renders fine on the latest trunk.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: For Arial · isn't recognized on MacOS X 10.5 Leopard → [10.5] For Arial · isn't recognized on MacOS X 10.5 Leopard
Version: unspecified → 2.0 Branch
Created attachment 291321 [details]
Screenshot of issue on latest branch nightly
This bug is part of a query for Firefox bugs that have Status set to NEW, but have version field set to 2.0 or older and have not changed in over 800 days.

http://tiny.cc/forgottennewbugs

If you still see this bug, or if it is still valid with Firefox 3.6.10 or a firefox 4 nightly build, please update the version field and steps to reproduce.
no response and marcia confirmed that it worked in the trunk
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.