[Webkit-unassigned] [Bug 95568] New: -webkit-flex of 0, computing to flex-basis: 0, does not allocate space to spec

[bugzilla-daemon at webkit.org]

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

           Summary: -webkit-flex of 0, computing to flex-basis: 0, does
                    not allocate space to spec
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Layout and Rendering
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: chutten at rim.com
                CC: chutten at rim.com, kpiascik at rim.com


After SVN rev 123770 (for Bug 92143) the Remote Web Inspector's buttons are using -webkit-flex: 0. This doesn't work so well on older versions of webkit, but oh well, I'll update.

I update, and it computes out to flex-basis: 0px; flex-shrink: 1; flex-grow: 0;... That's odd. According to the spec ( http://www.w3.org/TR/css3-flexbox/ ) that would mean it gets 0px of width assigned (irrespective of the buttons' width properties), then doesn't grow (only shrinking if there's insufficient space, which is rarely a problem)

Yet, in Chrome versions > 21, it lays out properly. That's decidedly odd. It's as though WebCore suddenly (between Chromes 21 and 22) started treating flex-basis: 0px the exact same as flex-basis: auto.

I'm familiar with the CSS specs (I helped write BlackBerry's old rendering engine) but not with how WebCore implements them, so my attempts at code archaeology so far have failed. I don't know what change caused the renderer to fall from spec, but it does appear to be failing.

Note: inspector.css' -webkit-flex: 0; is incorrect (wrt spec) and, upon resolution of this bug, will need to be changed.

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