Moved flags to WebTextInputType header so can be included from browser process code

Chromium's //content/browser is not allowed to import header files that are more
than simple definitions and so cannot include WebTextInfo to get flags from it.
Move them to another, existing, "simple" header so they can be used.

BUG=303883

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

git-svn-id: svn://svn.chromium.org/blink/trunk@179855 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Add NativeValueTraits for ScriptValue to V8Bindings.

Argument conversion, particularly variadic argument conversion, goes
through toNativeArray<>(), which means that this is needed to support
idl for arguments of type "any...".

R=haraken@chromium.org
BUG=None

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

git-svn-id: svn://svn.chromium.org/blink/trunk@179856 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Unified invalidation for repaint-only style changes (non-layers)

Use setShouldDoFullPaintInvalidation() for repaint-only style change
to avoid paintInvalidationForWholeRenderer() on repaint-only style
change.

BUG=394004
TEST=existing layout tests. Some previous duplicated repaints combined.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@179857 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Re-land of: Allow paint invalidation containers to cross frame boundaries.

The previous version had an infinite loop bug in RenderObject when there are two nested frames.

Previously, the *actual* paint invalidation container, meaning the enclosing
compositing layer / root RenderView, could already have been across a frame boundary. The logic to do this correctly was done via special code in RenderView.

Instead, generalize the existing mechanisms to find a paint invalidation container
and map rects to repaint container coordinate space to cross frame boundaries.
This simplifies the code, and also causes paint invalidation rects to always be stored
in the coordinate space of their graphics layer backing. The latter is important if we want
to use these rects for determining which parts of a graphics layer need to be painted.

BUG=401156

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

git-svn-id: svn://svn.chromium.org/blink/trunk@179858 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove unnecessary pixel expectations (platform/win)

The pixel expectations existed when the tests were pixel tests but now the
tests are text-only tests.

TBR=dpranke@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@179859 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Fix shutdown assertions in WebViewImpl

It's possible for some calls (e.g. WebViewImpl::layout) to try to
initialize compositing after shutdown.

This just moves an early out earlier so that it does not assert when
this happens.

This is a small band-aid fix to stop this assert from happening, rather
than the larger fix of trying to stop all the cases where this happen or
refactoring WebViewImpl to not have this awkwardness int he first place.

R=chrishtr@chromium.org
BUG=none

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

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