the Chromium logo

The Chromium Projects

Monday, March 30, 2015

We had Rune Lillesveen (rune) and David Vest (davve) from Opera join the

meeting this week in an effort to better coordinate our work. We also had

Ian Killpatrick (ikilpatrick) from the Chrome Sydney team join us.

The massive Rendering -> Layout rename project is done, thanks to

everyone who helped out and to Dan in particular who did most of the

heavy lifting!

The new multi-column implementation was enabled for tests and exposed as

an experimental web platform feature on Friday! Congrats Morten!

Updates since last meeting (on Monday, March 23rd):

Performance Tracking (benjhayden)

exposed via trace events allowing us to see the number of layouts on a

per element type basis.

be collected on an attached phone.

Scrolling (skobes) []

virtual test suites as right now it is only running fast/scrolling.

Rename Rendering -> Layout (dsinclair) []

is gone!

First letter refactoring (dsinclair) []

List marker refactoring []

psedo element. []

Measure API (jchaffraix)

up with a good strategy. So far none of the approaches tried have

panned out. Will continue to experiment and evaluate ideas to guide

future work.

Flexbox (cbiesinger) []

Line Boxes (szager) []

landed a few patches to fix tests. All of the remaining test failures

are OK to rebaseline.

hoped. There appeared to be significant performance regressions in the

blink_perf.layout test suite.

theory that they explain at least part of the regression.

decide exactly where to draw the line between LayoutUnit and float.

Isolate core/fetch (japhet) []

Page scale handling (bokan) []

Blink componentization (pilgrim) []

Text (kojii, wjmaclean, eae, rune)

descriptive. (wjmaclean)

handles text from the part that handles traversing. (wjmaclean)


finding/reporting a problem causing unnecessary layouts.

[] (rune)

broken tables. (kojii)

issues. (kojii)

Style resolution (rune)

Content sizing (davve)

Region-based multi-column support (mstensho) []


Standards (ikilpatrick, slightlyoff)

the next meeting by prototyping. (ikilpatrick)




[ cbiesinger's work to import the w3c test suite prompted a discussion

about w3c tests. ]

<slightlyoff> Are we mostly writing blink specific layout tests or w3c

web platform tests today?

<eae> For regression and performance work we use blink specific layout

tests pretty much exclusively. For feature work we're trying to move to

a world where we use web platform tests tests but we're not there yet.

<jsbell> Dirk (dpranke) started work in tooling to support w3c web

platform tests, I have headcount for an engineer to take this over and

work on improving the tooling.

<jsbell> Once better tooling and procedures are in place we should start

"strongly encouraging" people to write web platform tests for new


<slightlyoff> Can we do that today?

<jsbell> It is too too painful to do today, tooling needs to be improved