Have RenderBlockFlow sub-classes' methods call their super-class method properly.

RenderBlockFlowSubclass::foo() should typically call
RenderBlockFlow::foo(), not RenderBlock::foo(), unless there are
special reasons for bypassing RenderBlockFlow in particular cases.

I failed to come up with a test case that illustrates this problem,
but RenderListItem::styleDidChange() not calling
RenderBlockFlow::styleDidChange() sure looks bad. If it has floats and
becomes a BFC, parents, siblings, cousins etc. are not properly told
to remove the floats that are now fully contained by the list item. I
suppose there would be dangling pointers lying around because of this.

BUG=302024

Review URL: https://codereview.chromium.org/163513002

git-svn-id: svn://svn.chromium.org/blink/trunk@167161 bbb929c8-8fbe-4397-9dbb-9b2b20218538
DevTools: group tests by default opened panel.

Test shell will be updated to open devtools on the panel matching the test folder by default.
This saves time on loading Elements panel's module for tests that don't need that.

BUG=335790
R=vsevik@chromium.org

Review URL: https://codereview.chromium.org/163583002

git-svn-id: svn://svn.chromium.org/blink/trunk@167162 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Timeline: plumb RequestMainThreadFrame and DrawFrame to front-end

- add plumbing dor RequestMainThreadReame & DrawFrame from trace events
    to front-end;
- flush all pending background events before emitting a top-level main
    thread event.

R=pfeldman@chromium.org

Review URL: https://codereview.chromium.org/160323002

git-svn-id: svn://svn.chromium.org/blink/trunk@167163 bbb929c8-8fbe-4397-9dbb-9b2b20218538