{"push_id":1339418417,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"002fa39796783da2fbf183a36cb89ba7dcd601bb","before":"9358866a937bc8cb9facb7feb9d087fab355e459","commits":[{"sha":"002fa39796783da2fbf183a36cb89ba7dcd601bb","author":{"name":"cbiesinger","email":"66470a863925c1be158c7d97de2265a41133e556@chromium.org"},"message":"[css-flexbox] Some refactoring of flex item creation\n\nPart of my quest to make this code easier to understand. This moves some code\nout of computeNextFlexLine to constructFlexItem and layoutFlexItems.\n\nThe idea is to make the algorithm work like this:\n- First, we create all our flex item objects\n- Based on that list, we compute our flex line\n- For each line, we resolve the flexed sizes and lay out the children\n- At the end, we fix up the alignment (we need to know the container size for\n  this)\n- After all that, we lay out and position abspos children\n\nNot all of the above is implemented yet.\n\nIdeally, we can make this work with minimal direct access to flexItem.box (I\nwant to add a style() accessor on FlexItem at some point, and also move that\nclass to its own file). Then we can share the class and related layout functions\nwith LayoutNG.\n\n(Note, I also removed an unused typedef from the header)\n\nR=eae@chromium.org,dgrogan@chromium.org\n\nReview-Url: https://codereview.chromium.org/2407533002\nCr-Commit-Position: refs/heads/master@{#424102}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/002fa39796783da2fbf183a36cb89ba7dcd601bb"}]}
{"actor":{"display_login":"dstockwell"}}