399704 - Italicized text on Wikipedia rendered as regular text

Status: RESOLVED DUPLICATE of bug 364713

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

Description

[Fred Wenzel [:wenzel]]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.9a9pre) Gecko/2007101214 Minefield/3.0a9pre
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.9a9pre) Gecko/2007101214 Minefield/3.0a9pre

On Wikipedia, the follwing ''wikitext'' is rendered as <i>wikitext</i>. (If the tags are stripped by bugzilla: it's being enclosed in "i" tags).

On the current Minefield nightly on OSX, the italicized text is not rendered any differently than regular text.

So far I have only been able to reproduce this on Wikipedia, so it may be a bug in their CSS-or-so, but I want to make sure it's not Minefield's fault.

Unfortunately I have trouble debugging the issue because Firebug doesn't play flawlessly with Minefield yet.

See the attached image to see what I mean.

Reproducible: Always

Comment 1

[Fred Wenzel [:wenzel]]

Attachment: Actual result: Wikipedia italics rendered on Minefield

This is a piece of the first paragraph of the bug's URL, rendered in Minefield on OSX.

Comment 2

[Fred Wenzel [:wenzel]]

Attachment: Expected results: Something like this

This is the same piece of the page as displayed by Firefox 2.0.0.7 on OSX.

Comment 3

[philippe (part-time)]

Depending on which font is in use when you view Wikipedia, yes, italics can fail in Minefield OS X. That fails for fonts that do not contain italic glyphs (like Lucida Grande).

Comment 4

[Fred Wenzel [:wenzel]]

If I am reading the right part of the CSS, it is sans-serif, which defaults to Helvetica in Minefield, which *does* come with an oblique variant on OSX.

Is this still a dupe, then? Maybe.

Comment 5

[Fred Wenzel [:wenzel]]

(Maybe it does not render it right because italics != oblique?)

Comment 6

[philippe (part-time)]

Er, yeah, depending on your settings (or if you kept the defaults for Minefield), then Helvetica. Which is equally problematic, handled in bug 396002.