Unfocused TEXTAREA element should not accept editing.

The normal unfocusing step clears selection. But unfocusing caused by
display:none style didn't clear selection because:
 - It used Document::setFocusedElement. It bypassed FocusController.
 - Even if it used it, clearSelectionIfNeeded() in FocusController didn't
    clear selection because selection.rootEditableElement() was null in
    this case.

This CL changes the code so that:
 - We use Element::blur(), which uses FocusController::setFocusedElement.
 - clearSelectionIfNeeded() uses enclosingTextFormControl() to check
    if the selection is in INPUT/TEXTAREA instead of
    rootEditableElement(), which depends on renderers.

BUG=364309
TEST=automated

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

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172318 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Removing empty function definitions and WebAXObject interfaces

There were *FIXME* in thirdparty/Webkit//Source/core/accessibility/AXObjectCache.cpp rregarding no necessity of the functions startCachingComputedObjectAttributesUntilTreeMutates() and stopCachingComputedObjectAttributes() and concerned WebAXObject interfaces. 

Already uploaded the patch with Chromium side changes.
(https://codereview.chromium.org/245053004/)

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172319 bbb929c8-8fbe-4397-9dbb-9b2b20218538
[WebSocket] Clean up stale comments about subprotocol

Also rename subprotocol related methods to include "subprotocol" in
their names.

1st comment about valid characters:
We should update "Hybi-10" to RFC6455. But instead I've made the code
self descriptive.

2nd comment about valid characters:
The disagreement has been resolved. Now the WebSocket API spec refers
to the definition of the valid characters for the Sec-WebSocket-Protocol
header in RFC6455.

Didn't replace occurrences of protocol in each method since it's clear
they mean subprotocol in those scope.

BUG=none

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172320 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Add core Blink build configuration and WTF target to GN build.

I merged Source/config.gypi and Source/build/features.gypi into one file Source/config.gni. It wasn't clear what benefit having these separate is, and why features is in build but config is in the root dir.

Removed some unneeded warning disabling from GYP build (unknown pragmas). Remove obsolete comment about goma and clang plugins from GYP build.

I set up most of the feature defines required by WTF, with the exceptions noted with TODO(GYP).

I moved WTF_USE_DYNAMIC_ANNOTATIONS into the blink build file rather than the main build features config. This is not used outside the blink build and the reasons for it being in common.gypi don't apply to GN.

This patch will require a Chrome-side change to actually hook it up. Until that hookup happens, this code is entirely unused.

BUG=

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

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

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

TBR=vollick@chromium.org

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

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

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

BUG=364946
TBR=danakj@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172323 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Don't issue CSP warnings for preloads

It turns out that only two tests actually hit this
removing this removes two redundant warnings from
those tests.

I'm considering sending all tokens through the preloader
which will increase the number of these double-logging
events, so removing this double-logging before doing that.

BUG=309862

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172324 bbb929c8-8fbe-4397-9dbb-9b2b20218538
FCMify layout tests that check for no layer trees

These all just add layer trees in the text output where previously there
was not layer trees.  It's easier to just change this subset to force
compositing mode now so that they'll continue to work when all tests
become force compositing later.

BUG=361729

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172325 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Skip XMLHttpRequest.send performance test

It crashes the Android Nexus4 bot, thus causing noise for perf sheriffs.

BUG=353299
TBR=tonyg@chromium.org
NOTRY=true

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172326 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Update LeakExpectations to include known leaks and remove fixed leaks

+ marked more SharedWorkers tests as leaking
+ marked more selection tests as leaking
+ marked more drag tests as leaking
- filesystem directory callbacks are no longer leaking
- http/tests/misc/acid3.html is no longer leaking
- Tests using leak-check.js are now working

NOTRY=true
BUG=364377, 364390, 364391, 364392, 364394, 364395, 364407, 364408, 365180, 365182

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

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