Import csswg-test/css-writing-modes-3/

Import csswg-test/css-writing-modes-3/.

* Following failures are added to TestExpectations:
  - Tests we should fix, or at least investigate
  - Tests that are 1px differences only on some platforms
  - Tests that timeout only on Mac
* Following failures are to skip in W3CImportExpectations
  - Have known issues and the submitters are working on.
  - Have known issues and notified to the submitters, no responses yet.
  - Pass the test criteria but images do not match, notified to the submitters.
  - "combo" flag, idnicating a combo-test that covers multiple other tests in
    one test.
  - Tests that use features we do not have plans to support.  
  - Pass on the CSS WG harness but fail for us. I will investigate these
    further in separate CL.

> update-w3c-deps import using blink f1b79a7eca987970a09ff0c573c341fdc15b7aa9:
>
> imported csswg-test@f1b79a7eca987970a09ff0c573c341fdc15b7aa9
> imported web-platform-tests@f1b79a7eca987970a09ff0c573c341fdc15b7aa9

BUG=492664
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=196284

[kojii, 2015-06-01 02:19:45]

kojii@chromium.org changed reviewers:
+ dpranke@chromium.org, joelo@chromium.org, jsbell@chromium.org

[kojii, 2015-06-01 02:19:50]

PTAL. Some investigation remains to reduce [ Skip ] further, but I think it's
better to land and improve in following CLs.

[Dirk Pranke, 2015-06-01 21:54:40]

rubber-stamp lgtm for the import.

Can we delete any of the existing writing-mode tests (like fast/writing-mode, or
some of the others scattered around the tree) now?

[jsbell, 2015-06-02 00:14:13]

lgtm for landing, knowing we'll be iterating further on this

https://codereview.chromium.org/1161223002/diff/30001/LayoutTests/W3CImportEx...
File LayoutTests/W3CImportExpectations (right):

https://codereview.chromium.org/1161223002/diff/30001/LayoutTests/W3CImportEx...
LayoutTests/W3CImportExpectations:248: # CSS Writing Modes Level 3: Following
tests have known issues and the submitters are working on.
Do we have github issues for these that could be linked? (if not, don't worry)

https://codereview.chromium.org/1161223002/diff/30001/LayoutTests/W3CImportEx...
LayoutTests/W3CImportExpectations:420: # CSS Writing Modes Level 3: Following
tests are "combo", import ony one from each combo group (or improve the script
to handle automatically).
Typo: ony -> only

https://codereview.chromium.org/1161223002/diff/30001/LayoutTests/W3CImportEx...
LayoutTests/W3CImportExpectations:437: # CSS Writing Modes Level 3: Following
tests require applying writing-mode to table-cell, which we do not support
today.
crbug? (or do we never plan to support it?)

[kojii, 2015-06-02 00:22:42]

On 2015/06/01 21:54:40, Dirk Pranke wrote:
> rubber-stamp lgtm for the import.
> 
> Can we delete any of the existing writing-mode tests (like fast/writing-mode,
or
> some of the others scattered around the tree) now?

Ah, didn't have that view. There are a couple I created from these tests, so
they're no longer necessary. I'll see a bit more, but don't please expect
much...

[kojii, 2015-06-02 00:46:42]

Thank you for prompt reviews, Dirk and jsbell.

> knowing we'll be iterating further on this

Yes!

https://codereview.chromium.org/1161223002/diff/30001/LayoutTests/W3CImportEx...
File LayoutTests/W3CImportExpectations (right):

https://codereview.chromium.org/1161223002/diff/30001/LayoutTests/W3CImportEx...
LayoutTests/W3CImportExpectations:248: # CSS Writing Modes Level 3: Following
tests have known issues and the submitters are working on.
On 2015/06/02 00:14:13, jsbell wrote:
> Do we have github issues for these that could be linked? (if not, don't worry)

Unfortunately, the submitter, Gérard Talbot, is working on Mercurial mater, and
does not use github. I communicate to him on Shepherd
http://test.csswg.org/shepherd/ and by e-mail.

https://codereview.chromium.org/1161223002/diff/30001/LayoutTests/W3CImportEx...
LayoutTests/W3CImportExpectations:420: # CSS Writing Modes Level 3: Following
tests are "combo", import ony one from each combo group (or improve the script
to handle automatically).
On 2015/06/02 00:14:13, jsbell wrote:
> Typo: ony -> only

Done, thanks.

https://codereview.chromium.org/1161223002/diff/30001/LayoutTests/W3CImportEx...
LayoutTests/W3CImportExpectations:437: # CSS Writing Modes Level 3: Following
tests require applying writing-mode to table-cell, which we do not support
today.
On 2015/06/02 00:14:13, jsbell wrote:
> crbug? (or do we never plan to support it?)

Yes, http://crbug.com/409155. Comment added.

I wanted to mark at risk and discussed at CSS WG last week:
https://lists.w3.org/Archives/Public/www-style/2015May/0313.html

IE has basic support, but fails these test cases too. Gecko says "may be
deferred to a later milestone than the initial release".
https://bugzilla.mozilla.org/show_bug.cgi?id=1077521

WG wanted to keep, assuming there should not be much special thing to enable. My
thinking is that, it doesn't make sense for only Blink to support this, since
then authors would not use it. So I'll see, how serious other major browsers are
going to implement, and how much troubles we'll see by just enabling.

[kojii, 2015-06-02 04:38:06]

The CQ bit was checked by kojii@chromium.org

[kojii, 2015-06-02 04:38:09]

The patchset sent to the CQ was uploaded after l-g-t-m from jsbell@chromium.org,
dpranke@chromium.org
Link to the patchset: https://codereview.chromium.org/1161223002/#ps40001
(title: "Comments updated")

[commit-bot: I haz the power, 2015-06-02 04:38:23]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1161223002/40001

[commit-bot: I haz the power, 2015-06-02 04:51:44]

Committed patchset #5 (id:40001) as
https://src.chromium.org/viewvc/blink?view=rev&revision=196284