User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9) Gecko/2008061004 Firefox/3.0 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9) Gecko/2008061004 Firefox/3.0 Writing this: <a href="#""><img src="nav_about.gif" border="0" /></a> on two lines like this: <a href="#""><img src="nav_about.gif" border="0" /> </a> causes images to display in the wrong position. Reproducible: Always Steps to Reproduce: 1.See below - view the good file and the bad file with Mac Firefox 3.0. 2.View the source code. 3.The only difference is the </a> is on a separate line. Actual Results: See: http://www.arrowheadsps.org/firefox-bug/bad.html nav-left.gif and nav-right.gif are displayed a couple of pixels too low. Expected Results: See: http://www.arrowheadsps.org/firefox-bug/good.html the three gifs are properly aligned vertically. Only happens with Mac Firefox, Camino, and Sea Monkey. Does not happen with Mac Safari or Opera. Does not happen with anything on the Windows PC (tried Firefox, Opera, and IE). If, in this source code, you remove the table, something different happens. Try it if you're interested. But mainly the question is, why does bad.html do what it's doing?
I see this problem with Firefox 3.0.1 on OS X, Windows (XP) and Linux. I also see it with a current Minefield Trunk nightly (what will become Firefox 3.1) on OS X, and I'm reasonably confident I'd also see it on Windows and Linux. I don't see the problem with Firefox 2.0.0.X on any of these platforms. The OS X version I tested with is 10.5.4, but I assume this also happens on OS X 10.4.X. Though this problem probably doesn't happen very often, and has an easy workaround, it _is_ more than a bit embarrassing :-( So I'm upping the severity to "major".
Severity: normal → major
Status: UNCONFIRMED → NEW
Component: General → Layout
Ever confirmed: true
OS: Mac OS X → All
Product: Firefox → Core
Hardware: Macintosh → All
Version: unspecified → Trunk
> it _is_ more than a bit embarrassing I also suspect the underlying problem (whatever it is) is responsible for other, more subtle, bugs.
I think this is a duplicate; I recall another bug about whitespace trimming not interacting correctly with VerticalAlignFrames or VerticalAlignLine.
Component: Layout → Layout: Block and Inline
QA Contact: layout → layout.block-and-inline
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 434174
You need to log in before you can comment on or make changes to this bug.