Widen failure expectation for interrupted-all-transition test

Unreviewed gardening. Looks flaky on all platforms/build types.

BUG=248938
NOTRY=true
TBR=pfeldman@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@160239 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Update webkit.org lines to match the bots and delete cross-platform failures.

Avoided touching tests that look like they may pass if we just unskip them.

BUG=308779

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

git-svn-id: svn://svn.chromium.org/blink/trunk@160240 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Add myself to Source/web/OWNERS

This will make me a more effective reviewer of API cleanups in Source/core.

R=abarth@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@160241 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Rebaseline listbox bidi images

Unreviewed gardening - auto-rebaseline in 160220 may have done the
wrong thing.

BUG=85833
TBR=sanjoy.pal@samsung.com,ojan@chromium.org
NOTRY=true

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

git-svn-id: svn://svn.chromium.org/blink/trunk@160242 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Unstick background position origins

In the FillLayer class, reset the {x,y} origins each time {x,y}
position is set and require the caller to later call
setBackground{X,Y}Origin to override the default value. This fits
better with the way 'initial' values are set from the StyleBuilder and
avoids the problem of origins lingering in the FillLayer when setting
the 2-value versions of background-position.

Furthermore, split the flag m_backgroundOriginSet into one for each
property so that something like 'background-position-x:initial' won't
reset the position origin for both properties.

Also, remove code for handling 'initial' for {x,y} position, 'initial'
is already handled in the StyleBuilder further up the call chain.

BUG=304721

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

git-svn-id: svn://svn.chromium.org/blink/trunk@160243 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove pthread_getspecific_direct code.

We were never using and half-removed it already. It also relies on internal
APIs and an internal header where OS X's libc effectively special-cases their
WebKit.

BUG=none

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

git-svn-id: svn://svn.chromium.org/blink/trunk@160244 bbb929c8-8fbe-4397-9dbb-9b2b20218538
cloneNode: Change the default value back to false

This reverts the revert done in
commit 45c50f19df78c69e26ca3c98854bbf35ebc51004.

We used to use false as the default value for cloneNode. It was
recently changed to default to true to match the DOM spec. However, the
DOM spec was changed back to use false as the default value.

This should be safe because until recently Firefox threw exceptions
if no argument was passed. IE11, WebKit, Presto and Chrome
(before r153733, July) uses false as the default.

BUG=309628
TBR=lushnikov@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@160245 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove support for the '-khtml-' and '-apple-' CSS prefixes.

The majority of Blink's support for '-khtml-' and '-apple-' prefixes was removed
in [1] and [2]. Looks like we missed a spot or two.

This CL removes the remaining occurrences from CSSParser-in.cpp and drops the
disabled test that would have tested this behavior.

[1]: https://bugs.webkit.org/show_bug.cgi?id=111890
[2]: https://codereview.chromium.org/13685003

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

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