User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:22.214.171.124) Gecko/20090715 Firefox/3.5.1 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:126.96.36.199) Gecko/20090715 Firefox/3.5.1 I am currently using the latest beta of Mac OS X 10.6 Snow Leopard and Firefox 3.5.1 for Mac. When I try to open a website in Traditional Chinese, for example, Yahoo! Taiwan, I found that some Chinese characters became weird blocks and people cannot recognize and read them. It seems that only characters in some specific size would be so, if I try to resize the content of a web page by pressing on the command key and plus key or minus key, the characters come back and they are rendered perfectly. By the way, it also happened on Roman characters. The Roman characters would be check marks but not blocks. I know Snow Leopard is still in beta, and I am not sure if it is Apple's bug or yours. However, Apple ever mentioned about they will build the final release very soon in several months, what I wish is that the Mac users can still have a good web browser as Firefox on the day that Apple releases Snow Leopard. I think you can contact with Apple to solve the problem together. Reproducible: Always Steps to Reproduce: 1. Install Mac OS X Snow Leopard 10A421 2. Launch Firefox 3. Open web sites such as Yahoo! Taiwan, http://tw.yahoo.com Actual Results: Some Chinese characters become blocks. Expected Results: The characters should be rendered perfectly. You can find a screen shot in the attached URL,
Does this still happen in the latest seed?
Component: General → Graphics
Product: Firefox → Core
QA Contact: general → thebes
Summary: Characters look weird on Mac OS X 10.610A421 → [10.6] Characters look weird on Mac OS X 10.610A421
After using the final release, the characters seem so far so good. I guess that Apple fixes the bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
From the comments this was not a browser code bug.
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.