647542 - No linebreak on space between empty inline elements with padding

Status: NEW

(Core :: Layout: Block and Inline, defect)

Description

[B V Raghav]

User-Agent:       Mozilla/5.0 (X11; Linux i686; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0) Gecko/20100101 Firefox/4.0

I am not sure if it is a bug at all... But the above url renders fine with FF3 (stable release) and not with FF4. 

It is a simple ul>li[style="display:inline"]*4>a implementation of a list of links.Where prior to FF4, the list items "wrapped" automatically after the specified width of the first parent block element. But since I upgraded to FF4, The "auto-wrap" is not fulfilled.

Hopefully I am not failing a compliance.

Reproducible: Always

Steps to Reproduce:
1.Open the URL http://bvraghav.com/debug/ff4-inline-test.html in FF4
2.
3.
Actual Results:  
The auto-wrap for inline list element fails

Expected Results:  
the inline list of links should auto-wrap

Comment 1

[Tim (fmdeveloper)]

Confirmed on Mozilla/5.0 (Windows NT 5.1; rv:2.2a1pre) Gecko/20110402 Firefox/4.2a1pre ID:20110402030439

Works on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.16) Gecko/20110319 Firefox/3.6.16 ID:20110319135224

Comment 2

[Mats Palmgren (inactive)]

Regression range:  2010-02-01-03 -- 2010-02-02-03
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=f57b95afb57e&tochange=f557921b88a7
Possibly bug 538935?

Comment 3

[j.j.]

Attachment: testcase

Looks like a general problem, not related to lists

Comment 4

[j.j.]

BTW, IE8 and Opera 11.10 (build from yesterday) has the same behaviour

Comment 5

[Mats Palmgren (inactive)]

Google Chrome 12.0.712.0, breaks the line after the third box (same as FF3).

Comment 6

[Mats Palmgren (inactive)]

CSS3 Text, 4.2. The White Space Processing Rules, says:
"Any space (U+0020) following another collapsible space (U+0020)—even a space before the inline—is removed. However, if removing this space would eliminate a line breaking opportunity in the text, that opportunity is still considered to exist."
http://www.w3.org/TR/css3-text/#white-space-rules

Does the last sentence about the line-breaking opportunity cover this case?
(ie, there's a line-breaking opportunity between each inline)

Comment 7

[j.j.]

> BTW, IE8 and Opera 11.10 have the same behaviour
also IE9

Comment 8

[Boris Zbarsky [:bzbarsky]]

> (ie, there's a line-breaking opportunity between each inline)

There should be, yes.

Comment 9

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

(In reply to comment #8)
> > (ie, there's a line-breaking opportunity between each inline)
> 
> There should be, yes.

Some web pages may use:

> <span style="color: red;">A</span><span style="color: blue;">b</span><span style="color: yellow;">C</span>

such authors probably don't want breaking between the inline elements.

Of course, the markup isn't good thing and web page authors should use white-space: nowrap; for preventing line break. I just worry about the compatibility with older browsers.

Comment 10

[Boris Zbarsky [:bzbarsky]]

> Some web pages may use:

The difference between that markup and the markup in the attached testcase is that the attached testcase has spaces between the <span> tags, no?

Comment 11

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Okay, let me sure for the situations.

* When there is no white-spaces between inline elements (comment 9), shouldn't be a break opportunity.
* When there is one or more white-spaces between inline elements (testcaase), should be a break opportunity.
* When there is only one or more line-feeds between inline elements, should be a break opportunity? E.g., no indented source code like:

<span>foo</span>
<span>bar</span>

Comment 12

[Boris Zbarsky [:bzbarsky]]

Agree on the first two items in the list in comment 11.

Personally, I would put a line-break opportunity at the line-feeds in item 3.

Comment 13

[Robert O'Callahan (:roc) (email my personal email if necessary)]

The line-feeds get converted to spaces per the CSS spec.

This is definitely a bug here. It's a bad regression.

Comment 14

[Michelle Funches - QA]

This bug has been tagged for regression and or closure.
The issues can still be seen in latest Release
Version 	46.0.1
Build ID 	20160502172042

Comment 15

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee is inactive on Bugzilla, so the assignee is being reset.