Remove some more stale baselines.

TBR=pdr

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

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

TBR=pdr

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

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

TBR=pdr,pfeldman

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

git-svn-id: svn://svn.chromium.org/blink/trunk@152394 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Focus events on another frame don't work correctly

For bug details, look at https://code.google.com/p/chromium/issues/detail?id=246738
I verified that this is a regression caused by WebKit r143299.
This CL is a clear revert of the r143299.

BUG=246738
TBR=abarth,ojan

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

git-svn-id: svn://svn.chromium.org/blink/trunk@152395 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Support performance.now() in workers, behind a runtime flag.

performance.now() provides a high resolution monotonic clock. The time values start at an "origin time" instead of the typical UNIX epoch. For shared workers, the origin time is the time when the shared worker was created. For dedicated workers, the origin time is its document's navigationStart. That means performance.now() in the document and the dedicated worker should return values in the same range.

BUG=169318

Review URL: https://chromiumcodereview.appspot.com/16434011

git-svn-id: svn://svn.chromium.org/blink/trunk@152396 bbb929c8-8fbe-4397-9dbb-9b2b20218538
HTMLDialogElement doesn't need to reattach manually

HTMLDialogElement::positionAndReattaach previously called reattach manually
which was not needed since we only need a style recalc to update the style of
the renderer and trigger a layout to put the dialog in the center.

This patch instead marks the dialog for an inline style change, since that's
really all that changed.

Review URL: https://chromiumcodereview.appspot.com/16997005

git-svn-id: svn://svn.chromium.org/blink/trunk@152397 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Refactoring: Use specific element types in RenderTextControl*.

- RenderTextControl constructor should take HTMLTextFormControlElement
  as an argument.
- RenderTextControlSingleLine constructor should take HTMLInputElement
  as an argument.
- RenderSearchField constructor should take HTMLInputElement as an
   argument.
- RenderTextControlMultiLine constructor should take HTMLTextAreaElement
  as an argument.

Also, simplify updateUserModifyProperty by changing an argument from
Node* to HTMLTextFormControlElement*.

BUG=none
TEST=none; no behavior changes.

Review URL: https://chromiumcodereview.appspot.com/16875004

git-svn-id: svn://svn.chromium.org/blink/trunk@152398 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Initial CL using JSON export/import in bindings generation.

Roundtrips to/from JSON in usual compile so code used;
does not write intermediate files (that's a build change, next CL).

Roundtrip makes no semantic difference to generated code.
(Changes comments in 3 files, changing order of extended attributes.)

BUG=242795

Review URL: https://chromiumcodereview.appspot.com/16296004

git-svn-id: svn://svn.chromium.org/blink/trunk@152399 bbb929c8-8fbe-4397-9dbb-9b2b20218538
[css3-text] Property text-decoration-line accepts "blink" as valid value
    
As of November 13th 2012, the W3C specification has been updated to accept "blink" as a valid property value in text-decoration-line. Though accepting the value as valid, it is ignored as CSS Level 1 text-decoration property currently does. Though now "@supports" accepts the value as valid, the implementation is void - as acceptable by the specification: Conforming user agents may simply not blink the text.
    
This implementation has already landed in WebKit in changeset 150136.
    
BUG=239810
    
TBR=jchaffraix@chromium.org

Review URL: https://chromiumcodereview.appspot.com/16104010

git-svn-id: svn://svn.chromium.org/blink/trunk@152400 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove passing types-basicDOM-01-b.svg from TestExpectations

Due to my not understanding how garden-o-matic works, this expectation
stayed in for months! This test passes on all platforms.

BUG=
TBR=senorblanco@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@152401 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Update expectation for svg/text/font-size-below-point-five.svg

This test was only flaky on Linux but has been marked flaky for all
platforms. This patch updates the expectations and marks it as flaky
only on Linux.

BUG=
TBR=senorblanco@chromium.org

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

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