Closed Bug 724335 Opened 13 years ago Closed 13 years ago

Rendering of service-mark entity is really ugly

Categories

(Core :: Layout: Text and Fonts, defect)

11 Branch
x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 560472

People

(Reporter: getify, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0a2) Gecko/20120131 Firefox/11.0a2 Build ID: 20120131042011 Steps to reproduce: I use this entity: & #8480; on a normal html page. Actual results: it renders really horribly ugly, only in Firefox, but renders sanely as expected in Chrome and Safari. See the screenshot attached. Expected results: i expect that the rendering of a server-mark entity should be nearly identical to the quality that the & trade; trademark entity renders.
That character is not present in the default font being used (or, probably, most fonts used by typical pages), so what you'll see depends on the font we happen to find during font fallback. On my Mac, it picks DejaVu Sans, which looks pretty similar to the Chrome & Safari renderings in your screenshot, but this will depend what fonts you happen to have installed. (You can find out what font is actually being chosen by using the fontinfo add-on.) This is basically an example of the behavior described in bug 560472. It looks like we'll be addressing this in bug 705594, which should help by providing more standardized and predictable fallback behavior for most characters.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: