CSS Transforms: Implement transform

Implements transform as defined in CSS Transforms[1]. Behavior is similar
to -webkit-transform, but the perspective() function is not allowed to
contain numbers without units. Like -webkit-transform and other user
agents, the resolved value of transform is not the computed value as 
currently defined by css-transitions[2]. 

The animation system is modified to avoid running animations and 
transitions on both the prefixed and unprefixed variants at the same 
time. Internally, animations are mapped to the unprefixed variant. 
As animations operate directly on the RenderStyle storage the result 
of specifying an animation/transition on either property is the same. 

Note, this property is guarded by the CSSTransformsUnprefixed runtime 
feature (enabled only for testing). 

[1] http://www.w3.org/TR/css3-transforms/
[2] http://lists.w3.org/Archives/Public/www-style/2013Dec/0317.html 

BUG=154772

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

git-svn-id: svn://svn.chromium.org/blink/trunk@170527 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Copy stack until safepoint *before* notifying other threads at safepoints.

R=vegorov@chromium.org
BUG=356118

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

git-svn-id: svn://svn.chromium.org/blink/trunk@170528 bbb929c8-8fbe-4397-9dbb-9b2b20218538
[WebSocket] Add close-before-open layout test for workers

BUG=none

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

git-svn-id: svn://svn.chromium.org/blink/trunk@170529 bbb929c8-8fbe-4397-9dbb-9b2b20218538
RFC: Make BisonCSSParser purely stack allocated.

I was looking at how to port the BisonCSSParser and CSSParserObserver to the oilpan (GC) heap and noticed that we had a pointer from the BisonCSSParser back to the stack allocated CSSParserObserver/StyleSheetHandler. While it worked correctly making the BisonCSSParser stack allocated will IMO simplify the lifetime reasoning and make it less likely that we introduce errors.
This comes at the "expense" of always allocating a comment parser in the StyleSheetHandler. It is only used in the Inspector code so I am hoping that is okay.

R=ager@chromium.org, erik.corry@gmail.com, eseidel@chromium.org, haraken@chromium.org, oilpan-reviews@chromium.org, tkent@chromium.org, vegorov@chromium.org, zerny@chromium.org
BUG=

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

git-svn-id: svn://svn.chromium.org/blink/trunk@170530 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Copy DatabaseTask.{h,cpp} to TaskSynchronizer.{h,cpp}

This CL just copies a file just to make the diff of
https://codereview.chromium.org/198673002/ saner.

TBR=tkent
NOTRY=true

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

git-svn-id: svn://svn.chromium.org/blink/trunk@170531 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Rename DatabaseTaskSynchronizer to TaskSynchronizer and move it to platform/

- We want to use DatabaseTaskSynchronizer in the HTML parser thread in a follow-up CL. In preparation for that, this CL renames DatabaseTaskSynchronizer to TaskSynchronizer and moves it to platform/.

BUG=340522
R=ager@chromium.org, tkent@chromium.org, wibling@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@170532 bbb929c8-8fbe-4397-9dbb-9b2b20218538
DevTools: Makes script URL correct for imported documents that have nested imports.
BUG=354445

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

git-svn-id: svn://svn.chromium.org/blink/trunk@170533 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Revert 170532 "Rename DatabaseTaskSynchronizer to TaskSynchroniz..."

I miscommitted r170532 with unnecessary changes.
(r170532 was a sum of https://codereview.chromium.org/198673002 and https://codereview.chromium.org/216203006/,
but I should land only https://codereview.chromium.org/198673002.)
I'll reland those CLs separately.

> Rename DatabaseTaskSynchronizer to TaskSynchronizer and move it to platform/
> 
> - We want to use DatabaseTaskSynchronizer in the HTML parser thread in a follow-up CL. In preparation for that, this CL renames DatabaseTaskSynchronizer to TaskSynchronizer and moves it to platform/.
> 
> BUG=340522
> R=ager@chromium.org, tkent@chromium.org, wibling@chromium.org
> 
> Review URL: https://codereview.chromium.org/198673002

TBR=haraken@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@170534 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Removed unnecessary parameter from didActivateCompositor()

The parameter to didActivateCompositor() is meaningless. Hence, removed it. The other chromium side changes are here
https://codereview.chromium.org/137893025/

BUG=None

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

git-svn-id: svn://svn.chromium.org/blink/trunk@170535 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Rename DatabaseTaskSynchronizer to TaskSynchronizer and move it to platform/

- We want to use DatabaseTaskSynchronizer in the HTML parser thread in a follow-up CL. In preparation for that, this CL renames DatabaseTaskSynchronizer to TaskSynchronizer and moves it to platform/.

BUG=340522
R=ager@chromium.org, tkent@chromium.org, wibling@chromium.org

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

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

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