Test the media element activation behavior in fullscreen

BUG=358675

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

git-svn-id: svn://svn.chromium.org/blink/trunk@171372 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Disable x-webkit-speech

This does not remove the code yet, only makes x-webkit-speech
test-only (only exposed during LayoutTests) which makes
this patch only a one-line change. We should follow up this
change with a full removal of this feature including
all tests.

x-webkit-speech is a Chrome-only feature which was
announced as deprecated Feb 2014:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/jlPdpx6jErE
Current usage is at about 0.487% of reported Chrome page views
which is (well) above our normal 0.06% removal threshold:
http://www.chromestatus.com/metrics/feature/popularity#PrefixedSpeechAttribute

However, hours ago we recieved report of cases where *requiring
user interaction* speech can be captured for up to 8 seconds
or until the user stops un-interrupted speaking without proper
appearance of the "Allow this site to use your microphone"
infobar.

Although this is only a medium-security issue (requires
user interaction and very limited duration), this is still
severe enough that we no longer believe we can support
this deprecated, webkit-only feature.

Removing this feature will not affect mobile users
which already have access to speech-input via various
speech-enabled keyboards on Android.  Desktop sites which
were using this feature can use the modern Web Speech APIs
instead, which are standardized and supported accross many
browsers: http://caniuse.com/web-speech

Without this feature pages will continue to work, they just
will not be able to get speech input via <input> controls
via these APIs and will either have to use the standard
Web Speech APIs or depend on the operating system to expose
speech input via other methods.

I've verified that disabling this does not affect the new
JS Web Speech API by testing with:
https://www.google.com/intl/en/chrome/demos/speech.html

BUG=360448

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

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

git-svn-id: svn://svn.chromium.org/blink/trunk@171373 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Reland 171036i "Hook up gin platform to blink, and explicitly manage the main ..."

> We'll soon get rid of the v8 default isolate, so we'll need to manage
> our own.
>
> To test the platform implementation, run with
>   --js-flags="--noparallel_sweeping --concurrent-sweeping --job-based-sweeping"
>
> BUG=359977
> R=dcarney@chromium.org,haraken@chromium.org
>
> Original review https://codereview.chromium.org/227653002/

BUG=359977
TBR=dcarney@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@171374 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Reland "Allow cache reuse of some requests with Cache-Control headers"

Traditionally, we have carefully handled Cache-Control headers that were set on a ResourceResponse, but have pretended Cache-Control doesn't exist on ResourceRequests. As of http://src.chromium.org/viewvc/blink?view=rev&rev=165603, we do the smarter naive thing, and never allow resources to be reused from MemoryCache if the ResourceRequest includes a Cache-Control header.

This patch moves ResourceResponse's Cache-Control parsing to HTTPParsers and handles Cache-Control headers consistently, whether the header appears on a ResourceRequest or a ResourceResponse.

BUG=

This relands r171178.

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

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

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

BUG=302005
TBR=skobes@google.com

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

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