Closed
Bug 398286
Opened 18 years ago
Closed 12 years ago
Title on irc.mozilla.org wraps to next line and obscures text
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: dholbert, Unassigned)
References
()
Details
Attachments
(3 files)
If you make the http://irc.mozilla.org webpage skinny, the white "Network" text (from the "Mozilla IRC Network" title) wraps to the next line and obscures some of the content.
This is less of an issue on Firefox 2.0, because the only thing obscured is bits of a horizontal line.
But in Trunk, it obscures actual text, and it looks pretty wacky.
(see screenshots)
| Reporter | ||
Comment 1•18 years ago
|
||
| Reporter | ||
Comment 2•18 years ago
|
||
Posting a reduced testcase.
It looks like it's at least partly due to a difference in handling "display: block." If we remove that attribute, then both Trunk and Branch align "Mozilla" and the wrapped "Network" along the left edge of the page.
| Reporter | ||
Updated•18 years ago
|
Component: Other → Layout
Product: Websites → Core
QA Contact: other → layout
| Reporter | ||
Updated•18 years ago
|
Version: unspecified → Trunk
| Reporter | ||
Comment 3•12 years ago
|
||
[atoll just pinged me about this bug, when triaging old bugs with "irc" in the title]
It actually looks like the "trunk" behavior (which remains in current Nightly) is the correct behavior. (i.e. this was a bug in Firefox 2.0)
At large browser-widths, no visible centering will happen inside of #bar, because it's in an abspos block which is exactly sized to its contents' preferred width. But if you shrink the browser to make the text wrap, then there's some horizontal space available, which means centering can (and should) happen, due to text-align:center.
Chrome matches our behavior here, too, as a sanity-check.
(The discrepancy between "display:block" & implicit "display:inline" in comment 2 was just happening because text-align:center has no effect on inline-level elements, AFAICT)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•