Inline not displaying as inline




CSS Parsing and Computation
9 years ago
9 years ago


(Reporter: public, Unassigned)


1.9.1 Branch
Windows XP

Firefox Tracking Flags

(Not tracked)




(2 attachments)



9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5 (.NET CLR 3.5.30729)

Cheesy example, but here's where I noticed first: CSS is 

.tagcloud .tag {
    display: inline;
    margin-right: 5px;

But the list of tags on the left doesn't display inline at all. Compare in FF 3.5 vs. 3.0.11.

Reproducible: Always

Steps to Reproduce:
1. Go to page in FF 3.0.11. Tags are inline and appear as a cloud.
2. Go to page in FF 3.5. They are in a list without the inline.

Sort of looks like this bug,, but the last reports on that are a few years old, so I'm not sure it's the same thing.
Component: General → Layout
Product: Firefox → Core
QA Contact: general → layout
Version: unspecified → 1.9.1 Branch
Regression range:
Seems due to Bug 238072.
Blocks: 238072
Component: Layout → Style System (CSS)
QA Contact: layout → style-system
A simplified testcase would be useful.

Comment 3

9 years ago
The 'clear-float' solution (using generated content) at the end of the stylesheet is causing this

.widget-list li.item:after {
    content: " ";
    display: block; /* <---- this one */
    visibility: hidden;
    clear: both;
    height: 0.1px;
    font-size: 0.1em;
    line-height: 0;

Comment 4

9 years ago
Created attachment 388639 [details]
minimised test case

Both 'camino' and 'firefox' should be displayed on one line (each).

Comment 5

9 years ago
Created attachment 388645 [details]

From left to right:
IE 8, Minefield (windows), and in the foreground Safari (OS X) and Camino 2b (gecko 1.9.0.x).

IE 8 and Minefield display the same (and Opera 10b), 
Safari has the same display as Gecko 1.9.0.x.

Comment 6

9 years ago
very similar bug: bug 496053.
This is because we now fully implement 'display' on the :before and :after pseudo elements (bug 238072), and is correct behavior.  It used to be that (per CSS 2.0, rather than CSS 2.1) we ignored 'display:block' on :before and :after of inlines.
Last Resolved: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.