Move old multicol tests to a separate directory.

Move old multicol tests to a separate directory.

The plan is to make a virtual/stable test for this directory once the
new multicol implementation is used by default in layout tests. This way
the tests here can be run with both the old and new multicol
implementations.

Multicol test outside this directory will be run with the new
flowthread-based implementation. They all currently enable the new
implementation via settings
internals.settings.setRegionBasedColumnsEnabled(true). That flag is
going away once the new implementation is good enough to be enabled by
--enable-experimental-web-platform-features.

[rune, 2014-06-18 14:06:55]

I've had a long discussion with andersr today. I don't understand why the "old"
tests are moved into a separate directory. We can have a virtual test suite for
fast/multicol where we pass a command line flag that turns on the new
implementation and use the expected files from the test-suite, or add new
expected results to the virtual directory when appropriate (I gather render tree
dumps will differ, at least).

Then, when the new implementation becomes experimental, we can have a virtual
suite for the stable implementation and swap expected results and command line
flags.

Finally, when the new implementation goes stable, remove the stable virtual test
suite.

[ojan, 2014-06-19 20:41:59]

On 2014/06/18 14:06:55, rune wrote:
> I've had a long discussion with andersr today. I don't understand why the
"old"
> tests are moved into a separate directory. We can have a virtual test suite
for
> fast/multicol where we pass a command line flag that turns on the new
> implementation and use the expected files from the test-suite, or add new
> expected results to the virtual directory when appropriate (I gather render
tree
> dumps will differ, at least).
> 
> Then, when the new implementation becomes experimental, we can have a virtual
> suite for the stable implementation and swap expected results and command line
> flags.
> 
> Finally, when the new implementation goes stable, remove the stable virtual
test
> suite.

+1

[rune, 2014-07-04 12:49:28]

This CL is superseeded by these three CLs which have now landed:

https://codereview.chromium.org/343963002/
https://codereview.chromium.org/343973002/
https://codereview.chromium.org/341103002/

This CL may be closed.

[Julien - ping for review, 2014-07-04 22:12:15]

On 2014/07/04 at 12:49:28, rune wrote:
> This CL is superseeded by these three CLs which have now landed:
> 
> https://codereview.chromium.org/343963002/
> https://codereview.chromium.org/343973002/
> https://codereview.chromium.org/341103002/
> 
> This CL may be closed.

Closed. Thanks for pointing this out.