Stop using the needsSiteSpecificQuirks setting

It does nothing as of Blink r178756:
https://codereview.chromium.org/414443006

BUG=401887

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

Cr-Commit-Position: refs/heads/master@{#289294}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289294 0039d316-1c4b-4281-b951-d872f2087c98
Roll CLD2 to r166 to address Windows compilation failures.

BUG=403222
TBR=toyoshim@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#289295}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289295 0039d316-1c4b-4281-b951-d872f2087c98
Update .DEPS.git

Cr-Commit-Position: refs/heads/master@{#289296}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289296 0039d316-1c4b-4281-b951-d872f2087c98
Update CSS for supervised user block interstitial to be more friendly to narrow screens.

BUG=394309

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

Cr-Commit-Position: refs/heads/master@{#289297}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289297 0039d316-1c4b-4281-b951-d872f2087c98
Disable SyncSchedulerTest.ReceiveNewRetryDelay on Windows as its timing out.

See http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/1240
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/1233

BUG=402212
TBR=rlarocque@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#289298}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289298 0039d316-1c4b-4281-b951-d872f2087c98
Skia roll b62508b:b2721f7

https://skia.googlesource.com/skia/+log/b62508be81839be96f3d935d1e568e2ff3663670..b2721f7372652496e1b1ec722883904caa8134a8

CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:linux_layout_rel
TBR=bsalomon@google.com
BUG=

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

Cr-Commit-Position: refs/heads/master@{#289299}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289299 0039d316-1c4b-4281-b951-d872f2087c98
Update .DEPS.git

Cr-Commit-Position: refs/heads/master@{#289300}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289300 0039d316-1c4b-4281-b951-d872f2087c98
Whitelist Qualcomm GPUs for GPU rasterization on Android 4.4

This expands the GPU rasterization device whitelist to include all
Android 4.4 devices with Qualcomm GPUs.

BUG=None

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

Cr-Commit-Position: refs/heads/master@{#289301}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289301 0039d316-1c4b-4281-b951-d872f2087c98
Enable TCP preconnect and DNS preresolve on cellular.

Previously the default setting was to perform TCP preconnect and DNS
preresolution on all networks, and do prefetch and prerender on non cellular
network only.  Changing to kNetworkPredictionOptions has modified this default
behavior, disabling preconnect and preresolve on cellular networks by default
(the default setting is NETWORK_PREDICTION_WIFI_ONLY).  This CL reverts this
change, allowing preconnect and preresolve (but not prefetch and prerender) on
any network if kNetworkPredicitonOptions == NETWORK_PREDICTION_WIFI_ONLY.  In
order to do so, the helper functions CanPredictNetworkActions*() are split up
into new helper functions, one set for preconnect and preresolve, the other
for prefetch and prerender.

BUG=334602

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

Cr-Commit-Position: refs/heads/master@{#289302}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289302 0039d316-1c4b-4281-b951-d872f2087c98
Added usecounter histograms for <picture><source src></picture>

BUG=403260

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

Cr-Commit-Position: refs/heads/master@{#289303}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289303 0039d316-1c4b-4281-b951-d872f2087c98
Providing more information on why certain users can't be added to multi-profile
session

BUG=388279

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

Cr-Commit-Position: refs/heads/master@{#289304}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289304 0039d316-1c4b-4281-b951-d872f2087c98
Add another suppression for 252641

BUG=252641
TBR=zmo@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#289305}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289305 0039d316-1c4b-4281-b951-d872f2087c98
DevTools: Removed refcounting from AndroidWebSocket

Issue 387067 can be resolved by having port forwarding socket dependent on all other references to AndroidDeviceManager::Device.

This requires for lifetime of AWS to be manageable in the first place.

BUG=387067

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

Cr-Commit-Position: refs/heads/master@{#289306}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289306 0039d316-1c4b-4281-b951-d872f2087c98
Implement scroll handler latency tracking

Since scroll handlers do not block composited scrolling, the existing
input latency metric will only report the response time for the
compositor when scrolling a page with a handler. This is not accurate
for pages that implement scroll-synchronized effects, because the
scroll handler needs to be invoked so that the page contents are
updated with the new scroll offset.

This patch fixes the problem by forwarding latency information from the
impl to the main thread when we are scrolling a layer that has an active
scroll event handler.

In the case the scroll handler is no-op, the latency information will be
terminated as a failed commit.

Sample trace:
https://drive.google.com/file/d/0ByyxMXB38gLDRE40bkU5TVd0U00/edit?usp=sharing

BUG=347366

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

Cr-Commit-Position: refs/heads/master@{#289307}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289307 0039d316-1c4b-4281-b951-d872f2087c98
Revert 289154 "Revert 289067 "Use RE string pattern matching for..."

> Revert 289067 "Use RE string pattern matching for blacklist stri..."
> 
> Reason for revert: uninitialize memory access
> 
> http://build.chromium.org/p/chromium.memory.fyi/builders/Chromium%20Mac%20%28valgrind%29%282%29/builds/29469/steps/memory%20test%3A%20content/logs/stdio
> 
> > Use RE string pattern matching for blacklist strings.
> > 
> > Including cpu_brand, gl_vendor, gl_renderer, gl_extension, driver_vendor,
> > and machine_model_name.
> > 
> > BUG=396578
> > TBR=piman@chromium.org
> > TEST=gpu_unittests
> > 
> > Review URL: https://codereview.chromium.org/452293002
> 
> TBR=zmo@chromium.org
> 
> Review URL: https://codereview.chromium.org/465163002

TBR=oshima@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#289308}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289308 0039d316-1c4b-4281-b951-d872f2087c98
Disable BookmarkBarViewTest5.DND as it's flaky.

I see it sometimes failing on try jobs even with reruns.

BUG=128961
TBR=sky@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#289309}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289309 0039d316-1c4b-4281-b951-d872f2087c98
Mojo: Properly cancel further read on all read failures in RawChannelPosix.

(We weren't do so properly in the "too many handles" case.)

R=yzshen@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#289310}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289310 0039d316-1c4b-4281-b951-d872f2087c98
Add button to page info to revoke user certificate decisions

Currently, if a user clicks 'proceed' through an SSL interstitial, their only
way to revoke this decision is to restart their browser session. This commit
provides an explicit button in the page info to revoke this decision if the
user is using the remember certificate error decisions experiment. Since
decisions are remembered across browser restarts for these users, it's
important to provide them with a mechanism to revoke their decision later.

BUG=262615
NOTRY=true

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

Cr-Commit-Position: refs/heads/master@{#289311}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289311 0039d316-1c4b-4281-b951-d872f2087c98
Move StringToUpperASCII and LowerCaseEqualsASCII to the base namespace

Convert LowerCaseEqualsASCII to take StringPiece. In the current patch this is
generally a NOP but will allow me to delete the other 4 variants in a followup
(wanted to do that separately since that will require more review, since
callsites will be changed in nontrivial ways).

In some cases, LowerCaseEqualsASCII is called with a WebString, which no
longer is implicitly converted. I added base::string16(...) around such
calls to force the right conversion. It happened in these files:
  window_container_type.cc
  savable_resources.cc
  render_view_impl.cc
  blink_ax_tree_source.cc
  password_form_conversion_utils.cc
  translate_helper.cc
  chrome_render_view_observer.cc
  dom_serializer_browsertest.cc

R=jamesr@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#289312}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289312 0039d316-1c4b-4281-b951-d872f2087c98
+jbudorick, -craigdh for build/android/pylib/OWNERS.

BUG=

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

Cr-Commit-Position: refs/heads/master@{#289313}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289313 0039d316-1c4b-4281-b951-d872f2087c98