Reset compositorDrivenAcceleratedScrollingEnabled between layout tests.

BUG=

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157178 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Disable scrollbar hit-test on Android.

We noticed today that slow-path gestures such as taps can still be
forwarded to scrollbars on Android. The Android platform convention is
that scrollbars should not be interactable with directly in any way.
Add a new overlay scrollbar theme parameter to disable hit-testing and
set it on Android.

NOTRY=true
BUG=282704

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157179 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Unassociated form controls should be removed from form.elements even if controls are accessed by names.

Import WebKit r154761 [1] and r154765 [2].
> Remove elements from the past names map of a form element when they are
> disassociated with the form to match the behaviors of Firefox 24 and Internet
> Explorer 10. The specification feedback has been submitted to WHATWG in
> http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2013-August/040586.html

A function to unregister associated elements also removes them from the
past names map. The new code uses toHTMLElement(FormAssociatedElement*),
which can't be used in FormAssociatedElement destructor. We need to
move setForm(0) calls from ~FormAssociatedElement to subclass destructors.


Note that this CL dropped the RefPtr->raw pointer change in [1]. We'll address
it later.

[1] http://trac.webkit.org/changeset/154761
[2] http://trac.webkit.org/changeset/154765

BUG=190026
TEST=automated.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157180 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Fast increment to the next inline renderer when the current renderer is isolated.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@157181 bbb929c8-8fbe-4397-9dbb-9b2b20218538
renderStyleOfEnclosingTextNode should update style before using a renderer

When accessing a renderer editing should always make sure that the style
has been updated for the node. Editing calls splitTextNode in a number of
places and then accesses the renderer later. This patch is the first of
many to make sure editing always updates the style before attempting to
access the renderer (or style) of a node after calling a mutation method.

BUG=276689

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

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