Skeleton of the Safe Browsing Subresource Filter.

third_party/WebKit/LayoutTests/TestExpectations

Index: third_party/WebKit/LayoutTests/TestExpectations
diff --git a/third_party/WebKit/LayoutTests/TestExpectations b/third_party/WebKit/LayoutTests/TestExpectations
index d7806f972c29d9c4f1b40c977c0218fe17943844..da9535909e79458fb9cbf99af6a5f426e5ed6088 100644
--- a/third_party/WebKit/LayoutTests/TestExpectations
+++ b/third_party/WebKit/LayoutTests/TestExpectations
@@ -1388,3 +1388,5 @@ crbug.com/609067 [ Mac ] bluetooth/writeValue/write-succeeds.html [ Skip ]
 crbug.com/609067 [ Mac ] bluetooth/writeValue/write-updates-value.html [ Skip ]
 
 crbug.com/610567 usb/usbDevice-iframe.html [ Failure Pass Timeout ]
+
+crbug.com/609747 http/tests/subresource_filter [ NeedsRebaseline ]

[Mike West, 2016/06/01 13:43:18]

This is not a great way to land tests: if the tests are broken, this will just
mindless write new expectation files. You should generate those expectations
locally, verify that they are correct, and commit them along with the CL.

Or just use testharness-style assertions, and forget about expectation files
entirely.

[engedy, 2016/06/02 23:07:19]

Done.  Out of curiosity, what's the preferred way to create platform-dependent
pixel test expectations?