Using alt and down key to open datalist using keyboard

On pressing alty+down key, datalist is open and no stepDown is generated.

R=tkent@chromium.org, isherman@chromium.org, keishi1@chromium.org
BUG=229073
TEST= On down+alt key combination does not generate stepDown.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@170673 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove software path from filters: FEComponentTransfer.

BUG=357672

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

git-svn-id: svn://svn.chromium.org/blink/trunk@170674 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Fixed a variable that may be used uninitialized.
Prevents a warning with GCC 4.8 on Android.

BUG=

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

git-svn-id: svn://svn.chromium.org/blink/trunk@170675 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Add a trace event for ResourceFetcher::requestResource

This could help better understand the Blink resource-fetching overhead
seen, for example, in XMLHttpRequest.send().

R=japhet@chromium.org
BUG=348655

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

git-svn-id: svn://svn.chromium.org/blink/trunk@170676 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Apply the correct style to first-letter pseudo elements composed of different renderers

Traverse (in preorder) the whole subtree under a render block with a first-letter selector when
looking for the text renderers which would need to get the apropriate style applied, instead of
only considering the first renderer only, which might not contain all the text that should be
considered as a "first letter" (leading and trailing punctuation should be included too).

The present patch also considers leading spaces, if any, as part of the first-letter element,
to match the behaviour of other renderers such as IE and Opera (Firefox does not do that).

R=eae@chromium.org, leviw@chromium.org
BUG=354403
TEST=Add new test to check first-letter elements composed of different renderers.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@170677 bbb929c8-8fbe-4397-9dbb-9b2b20218538
MSE: Allow requesting coded frame processor: legacy or new

Updates WebMediaSource to have an addSourceBuffer() version that
allows caller to request which of LegacyFrameProcessor or a (not yet
landed in Chromium) new frame processor to use to process frames parsed
during appends to the source buffer.

The choice of which frame processor to request is based on
--enable-experimental-web-platform-features, as exposed through
RuntimeEnabledFeatures::mediaSourceExperimentalEnabled(): if enabled,
the new frame processor is requested. Otherwise, LegacyFrameProcessor is
requested.

Until the updated Chromium side WebMediaSourceImpl lands and (later)
the new Chromium frame processor lands, LegacyFrameProcessor will be
used regardless of the requested processor.

R=acolwell@chromium.org,abarth@chromium.org
BUG=249422
TEST=All MediaSource layout tests pass both before and after Chromium
side WMSI change is applied locally, and MediaSourceBase logging shows
frameProcessorChoice reflects usage (or lack) of cmdline switch
--enable-experimental-web-platform-features

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

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