ayg wrote:

This is because of standards vs. almost standards mode, triggered by the doctype difference. It's why we need to switch to HTML5 across the board and tweak everything to work right in standards mode, then kill XHTML 1.0 Transitional support. Supporting both modes will be too much of a hassle. There will be a number of minor rendering differences like this, but nothing should be a big deal and they can be dealt with as they're reported during the transition phase, IMO.

• Bug 32025 has been marked as a duplicate of this bug. ***

(mass change)

• 1.18.0 and 1.19.0 have been released already.
• Moving open bugs targeted for 1.18.0 or 1.19.0 to Mysterious future.
• Please re-target them to 1.19.x or 1.20.0 if needed.

I think i might have found the possible root cause of why it differs in the two modes.

Apparently in HTML5: "an inline element, that appears in HTML5 inline elements defer to its parent 'block' element's line-height"

ayg wrote:

I think this is the relevant spec text:

http://dvcs.w3.org/hg/quirks-mode/raw-file/tip/Overview.html#the-line-height-calculation-quirk

(FWIW, this is not due to HTML5 per se -- using an HTML 4.01 Strict doctype would also have triggered it, for instance.)

Jason_quinn wrote:

shows the problem under Firefox 19.0.2 on a Linux system, alongside with 3 other working browsers

Attached:

Is this fixed? It looks fixed for me.