[Webkit-unassigned] [Bug 124527] New: Spaces between inline elements with parent with `display: table-row` get ignored (unlike Gecko, Trident)

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Nov 18 11:14:45 PST 2013


https://bugs.webkit.org/show_bug.cgi?id=124527

           Summary: Spaces between inline elements with parent with
                    `display: table-row` get ignored (unlike Gecko,
                    Trident)
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
               URL: http://codepen.io/alanhogan/pen/JsBuj
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: New Bugs
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: webkit-bugzilla at alanhogan.com


Webkit Version       : 7.0 (9537.71, 538+)
Other browsers tested: 
     Chrome 31: FAIL
     Firefox stable: OK
     IE 9: OK

What steps will reproduce the problem?
1. Give an element (e.g. <span>) display: table-row;
2. Give that span some content including some plain text and some sequential, but space-separated, inline elements that retain their display: inline; default (not display: table-cell). (Can be confirmed with the inspector)

What is the expected result?
The entire table-row acts as one table-cell with regards to layout (which it does), and with regards to how its content is displayed.


What happens instead?
While the table-row does not create a table-cell for each child, the whitespace is parsed in a fashion such that spaces separating child elements is lost, although spaces between child elements and text nodes is not.

Additional info:
Only Webkit and Blink have this bug. Gecko and Trident do not.

It doesn’t make sense, to me, that `display: table-row` would have the effect observed. The contents of the element are not rendered like table-cells; there’s no alignment of “cells” between “rows” (double-up the spans and change content to observe); each inline element (`del`, `ins`) has `display: inline` when inspected; text nodes are rendered in order without being awkwardly added to a table. So it “shouldn’t” affect HTML parsing like this. 

Am attaching a Firefox screen shot and a Webkit Nightly screen shot. Note the lack of space after “two,” in the buggy screen shot.

Test case at http://codepen.io/alanhogan/pen/JsBuj

Filed against Blink at https://code.google.com/p/chromium/issues/detail?id=320751

Observed in stable builds.
Confirmed in Webkit Nightly, Version 7.0 (9537.71, 538+)

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the webkit-unassigned mailing list