Remove baselines for ref tests.

Three layout tests had PNGs checked in for them, even though they are reftests.

TBR=eseidel@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177243 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Auto-rebaseline for r177233

http://src.chromium.org/viewvc/blink?view=revision&revision=177233

TBR=eae@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177244 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Enables Activity Logger to log extension adding the following elements to the DOM:
- script
- link
- anchor
- iframe
- form
- input
- button

BUG=388287

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

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177245 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Fix shadow repaint issue in vertical-rl mode

The original code erroneously flipped the shadow edges when the box is
in vertical-rl writing mode, causing incorrect visual overflow and
repaint rects.

Our actual painting code for shadow is correct. The bug is just about
incorrect invalidation rects.

Note because of other bugs about shadow invalidation, the expected
result of the new tests are not correct yet. Will rebaseline them
when the bugs are fixed in later changes.

References:
[1] http://dev.w3.org/csswg/css-writing-modes-3/#physical-only

BUG=388343
TEST=fast/box-shadow/shadow-box-resize-writing-mode.html
TEST=fast/box-shadow/shadow-box-resize.html

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177246 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Fix some nits as a follow-up for issue 355193003.

BUG=381876
TBR=haraken

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177247 bbb929c8-8fbe-4397-9dbb-9b2b20218538
MSE: Complete removal of Blink-side support for LegacyFrameProcessor

This is the last of a three-sided change to remove LegacyFrameProcessor
from Blink and Chromium now that the new FrameProcessor is stabilized.

R=acolwell@chromium.org,abarth@chromium.org
BUG=249422
TEST=No MSE layout test regression locally on Linux

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177248 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Adding a UseCounter for DOMWindow.open with and without the feature string.

R=abarth
BUG=82522

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177249 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Initialize value since calculateFinalValues may fail to do so.

Fix threading issue where updateCoefficientsIfNecessary was not always
called from the audio thread. This causes the value not to be
initialized.

Thus,

o Initialize the variable to some value, just in case.
o Split updateCoefficientsIfNecessary into two functions with the code
  that sets the coefficients pulled out in to the new function
  updateCoefficients.
o Simplify updateCoefficientsIfNecessary since useSmoothing was always
  true, and forceUpdate is not longer needed.
o Add process lock to prevent the audio thread from updating the
  coefficients while they are being read in the main thread. The audio
  thread will update them the next time around.
o Make getFrequencyResponse set the lock while reading the
  coefficients of the biquad in preparation for computing the
  frequency response.

BUG=389219

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177250 bbb929c8-8fbe-4397-9dbb-9b2b20218538
[DirectWrite] Disable subpixel font positioning if AA is disabled

DirectWrite with subpixel font positioning renders really badly when
font smoothing has been completely disabled.

Change FontPlatformData::setupPaint to gate subpixel positioning on the
precense of some type of font smoothing, be it standard or ClearType.

BUG=383372
R=cpu@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177251 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Use MediaValuesDynamic in HTMLImageElement rather than MediaValuesCached

This is a speculative fix to performance issues introduced by the sizes impl.
Since there's no reason to use MediaValuesCached in HTMLImageElement,
and since it may have an overhead of caching all the media values,
I've switched HTMLImageElement to use MediaValuesDynamic.

In order to avoid problems when the LocalFrame doesn't exist or doesn't have a view,
I've added a MediaValuesDynamic::create() method that return an empty MediaValuesCached
n these cases.

BUG=389616

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177252 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Naming of boxDecorations

We used the term "boxDecorations" for the following two different
things at different places of rendering code:

- Box decorations that are painted as background (at
  PaintPhaseBlockBackground or PaintPhaseChildBlockBackground):
  This includes borders, shadows, background-colors, background-images
  and any background drawn for any appearence;

- Box decorations drawn around the edges of the box:
  This includes borders, shadows, outlines, any other box decorations
  drawn for appearance, etc. (from RenderLayer.cpp and
  CompositingLayerMapping.cpp)

To make it clear, the term used in the former case is renamed to
'boxDecorationBackground', and the latter case is kept unchanged.

By the way, added RenderStyle::hasBoxDecorations() to avoid
duplicate/inconsistent code, and I'd also like to use the function
in another change that requires the same concept.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177253 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Assert the SVG paint invalidation container didn't change in invaliadateTreeAfterLayout

We don't support accelerated layers in SVG yet, so assert that the paint
invalidation container didn't change and avoid doing extra work to prove
that point in SVG's invalidateTreeAfterLayout method.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177254 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Test adding a <source> element after removing a failed candidate

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

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