Remove dead code from Dictionary

Remove getEventListener() method from the Dictionary class as it does not
appear to be used and it always returns 0.

R=haraken
BUG=

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157523 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Get rid of fastMallocGoodSize() and replace it with something generic.

- fastMallocGoodSize() was Mac-specific and it looks relatively slow and
non-inlineable. The replacement is based around a single lookup into a small
table.
- We now have allocation quantization on all platforms for Vector. I've
verified that many Vector instantiations are able to recover previously-wasted
memory as real element capacity. See bug for details.
- The quantization is also immediately suitable for use with the Partition
allocator, to avoid fragmentation due to excessive numbers of buckets. To be
followed up in a future patch series.


BUG=286477

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157524 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Revert 157524 "Get rid of fastMallocGoodSize() and replace it wi..."

> Get rid of fastMallocGoodSize() and replace it with something generic.
> 
> - fastMallocGoodSize() was Mac-specific and it looks relatively slow and
> non-inlineable. The replacement is based around a single lookup into a small
> table.
> - We now have allocation quantization on all platforms for Vector. I've
> verified that many Vector instantiations are able to recover previously-wasted
> memory as real element capacity. See bug for details.
> - The quantization is also immediately suitable for use with the Partition
> allocator, to avoid fragmentation due to excessive numbers of buckets. To be
> followed up in a future patch series.
> 
> 
> BUG=286477
> 
> Review URL: https://chromiumcodereview.appspot.com/23604048

TBR=cevans@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157525 bbb929c8-8fbe-4397-9dbb-9b2b20218538
DevTools: slight tweaking of step-into-selection feature

This patch does a slight CSS tweaking related to step-into-selection
feature.

BUG=275661

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157527 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Implement filter primitive subregion on accelerated reference filters for FEColorMatrix, FEGaussianBlur and FE*Lighting. This patch also adds crop tests for all the filters, both software and hardware versions. The software results are correct; bringing the remainder of the hardware results into alignment with software results will be the work of future patches (Skia and Blink-side).

The patch adds a crop offset to the SkiaImageFilterBuilder, which is used to communicate the offset computed by the Blink filter chain when inflating its results for filter bounds. This code may be removed in the future once Skia takes on this responsibility and knows how much each filter inflates its result.

BUG=229910

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157529 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Use COMPILE_ASSERT instead of ASSERT in PartitionAlloc.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157530 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Use Vector as SSV's Writer buffer, to avoid mysterious realloc issue

A Blink@155225 changed SSV to serialize using StringBuffer instead of
Vector, but this seems to hit an issue with fastRealloc calls. Revert
back to Vector while we try and track down the root cause.

BUG=266837
R=abarth@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157531 bbb929c8-8fbe-4397-9dbb-9b2b20218538
WebCrypto: [refactor] Use "unsigned" rather than "size_t" for buffer sizes in the public API.

Justification:

I have noticed some instances where the Chromium-side implementation is directly passing this "size_t" as the buffer length to NSS.

NSS however expects buffer lengths as "unsigned int", and the C++ compiler implicitly converts the "size_t" to an "unsigned int". This conversion is dangerous, since theoretically it could result in truncation of the buffer length given to NSS. (Under LP64 datamodel for instance).

Chromium's compilation settings don't warn about such issues.

In practice this isn't a problem, and likely never will be, since in Blink ArrayBuffers are limited to lengths of 2^32-1.

It is therefore a good idea to pass a narrower datatype in the API to make this obvious. Embedder shouldn't have to worry about dealing with buffer sizes in the full range of size_t.

BUG=245025

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157532 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Cleanup, added a helper to FrameView, isMainFrame(). No behavior change

BUG=

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157533 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Use a set instead of a map to keep track of scrollbars.

When keeping track of scrollbars on mac, use a set since
we're not mapping any data.

BUG=None

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157534 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Drag'n drop Autoscroll does not work properly on inner frames

RenderBox::calculateAutoscrollDirection does not properly translate
inner frames' coordinates in order to determine its auto-scrollability.
By coincidence, if the inner frame box it placed near to page's 0, 0 position
(upper left corner), it might work.

Patch fixes it by changing ::calculateAutoscrollDirection algorithm to operate
with window coordinates, taking inner frames offset and scroll position into account.
The behavior of auto-scrollable non-frame overflow boxes, including divs, still works
as it is used to.

Test: fast/events/drag-and-drop-autoscroll-inner-frame.html

BUG=chromium:286325

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157535 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove unnecessary work from Node finalizer

By the time we run the Node destructor, we should have already destroyed the
renderer for the node. This CL changes the Node finalizer from handling the
error case gracefully to crashing. Crashing in this case will let us get
feedback from fuzzers and the field as to whether this invariant actually
holds.

The code was introduced in http://src.chromium.org/viewvc/blink?view=revision&revision=798
in a merge from KDE.

R=esprehn@chromium.org

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

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

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

BUG=299910,229910
TBR=senorblanco@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157537 bbb929c8-8fbe-4397-9dbb-9b2b20218538
[Android WebView] Separate TargetDensityDPI processing from other settings

Currently turning off SupportTargetDensityDPI also turns off the code path
that processes LoadWithOverviewMode and UseWideViewport settings. This
change makes the processing independent.

BUG=288037

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157538 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove V8TRYCATCH_WITH_TYPECHECK macro in V8BindingMacros.h

V8TRYCATCH_WITH_TYPECHECK is not used.

BUG=N/A

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

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

GraphicsLayerTransform is unused, so this CL removes it.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157540 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Have Dictionary use V8TRYCATCH_FOR_V8STRINGRESOURCE() macro

Have Dictionary use V8TRYCATCH_FOR_V8STRINGRESOURCE() macro instead of
the deprecated toWebCoreString().

R=haraken
BUG=

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157541 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Clear TemplateContentDocumentFragment::m_host when HTMLTemplateElement is destroyed

Note that the included test only crashes reliably in an asan build.

R=inferno@chromium.org
BUG=286975

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157543 bbb929c8-8fbe-4397-9dbb-9b2b20218538
[SVG] Incorrect large filter clamping transformation.

RenderSVGResourceFilter::applyResource() performs ImageBuffer size 
clamping before calling createImageBuffer (by adjusting its 
scale/effective transform). This clashes with the existing
createImageBuffer() clamping logic and results in an incorrect
ImageBuffer context CTM.

Since RenderSVGResourceFilter is the only createImageBuffer client, we
can relocate the method and remove the extra clamping.

Test: svg/filters/filter-huge-clamping.svg

BUG=161624
R=pdr@chromium.org,schenney@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157544 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Always pass v8::Isolate to v8::Number::New()

Always pass v8::Isolate to v8::Number::New() as this is now the preferred way
of constructing a Number:
https://code.google.com/p/v8/issues/detail?id=2487

R=haraken
BUG=

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

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