GitLab

net: add (www.)honeybadger.io to HSTS preload.
Cr-Commit-Position: refs/heads/master@{#293025}

TBR=jam@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#293024}

There are more work needs to be finished, but this should at least allow us to implement login UI

* Added chrome version of ExtensionsDelegate and AppActivity
* introduce use_athena gyp flag
* disabled features/code path that does not work yet on athena. Filed bugs to keep track of them.

BUG=397167
R=mukai@chromium.org, yoz@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#293023}

R=zmo@chromium.org,ajuma@chromium.org
BUG=407144

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

Cr-Commit-Position: refs/heads/master@{#293022}

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

Cr-Commit-Position: refs/heads/master@{#293021}

This permission allows an application to access any connected U2F device
(as identified by its HID Usage Page) through the chrome.hid API.

BUG=374307

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

Cr-Commit-Position: refs/heads/master@{#293020}

This CL also centralizes setting the activity's bounds and transform while in
split view to SplitViewController::UpdateLayout(). In particular, the bounds of
an activity are now correct even if it is opened while some other activity is
animating into split view

BUG=405964
TEST=WindowManagerTest.NewWindowBounds

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

Cr-Commit-Position: refs/heads/master@{#293019}

This makes extensions aware of the platforms for which
they have platform-specific resources installed, if any.

This also hooks up the extension update code with some
additional logic to place an extension in forced-update
mode if it has platform-specific resources which don't
match the current NaCl architecture.

BUG=409948
TEST=install an extension which uses NaCl (QuickOffice for example). Rename the _platform-specific/<your-nacl-arch> directory some something else and force an update (e.g. via chrome://extensions button). Observe that a new CRX is downloaded and installed.

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

Cr-Commit-Position: refs/heads/master@{#293018}

BUG=409919

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

Cr-Commit-Position: refs/heads/master@{#293017}

BUG=352293

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

Cr-Commit-Position: refs/heads/master@{#293016}

BUG=409104
b/17294369

NOTRY=true

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

Cr-Commit-Position: refs/heads/master@{#293015}

Calling begin() const and end() const function in ScopedPtrVector has
compiler error with const_iterator. Change back from const T* to T*.

Also since cpplint complains has to change a reference to pointer.

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

Cr-Commit-Position: refs/heads/master@{#293014}

https://chromium.googlesource.com/chromium/blink/+log/07cfde2700209d53893a4f7be2b52a3a25355740..5d185994db600614dae243adfb09a7e191208e2a
TBR=hclam@chromium.org,tkent@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#293013}

It was inadvertently disabled in r287058.

BUG=313751
TBR=glider@chromium.org
NOTRY=true

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

Cr-Commit-Position: refs/heads/master@{#293012}

This is better than the existing pair of histograms
UMA.ProtoCompressionRatio and UMA.ProtoGzippedKBSaved
which require manual calculation to get at the approx.
value.

BUG=409179

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

Cr-Commit-Position: refs/heads/master@{#293011}

BUG=

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

Cr-Commit-Position: refs/heads/master@{#293010}

Proguard strips these methods if they are not annotated because they
are only used in tests.

TBR=brettw
BUG=163393

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

Cr-Commit-Position: refs/heads/master@{#293009}

The DistilledPageInfo and related structs are unnecessary, and it is possible
to pass the DomDistillerResult proto around instead. Currently they contain the
same data, and it is all just copied over.

Removing this intermediate step simplifies the code and makes it easier to add
more data to the DomDistillerResult proto and passing it through to
DistilledPageProto.

BUG=409274

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

Cr-Commit-Position: refs/heads/master@{#293008}

BUG=None
NOTRY=True

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

Cr-Commit-Position: refs/heads/master@{#293007}

This should enable the message receiver to identify a key to be used for
message decryption.

BUG=409099

(depends on https://codereview.chromium.org/513013003/)

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

Cr-Commit-Position: refs/heads/master@{#293006}

https://skia.googlesource.com/skia/+log/98d709bc8d0761df8e0ad35e92c06e500f0be50d..00f30bdc9e34b013da54b4406f36556c5be8d041

CQ_EXTRA_TRYBOTS=tryserver.blink:linux_blink_rel,linux_blink_dbg
TBR=jvanverth@google.com

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

Cr-Commit-Position: refs/heads/master@{#293005}

Add usrsctp. Make Windows version configurable for this in the build.

direct_dependent_configs for libsrtp.

R=hclam@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#293004}

Revert of Add LatencyInfo support for Surfaces. (patchset #3 id:40001 of https://codereview.chromium.org/511423004/)

Reason for revert:
Failed compile here: http://build.chromium.org/p/chromium.memory/builders/Linux%20ASan%20LSan%20Builder/builds/12959/steps/compile/logs/stdio

Original issue's description:
> Add LatencyInfo support for Surfaces.
>
> BUG=
>
> Committed: https://chromium.googlesource.com/chromium/src/+/30ea8cb30b9e0d6fcd037bc434b29bac41196e5e

TBR=jamesr@chromium.org,jbauman@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=

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

Cr-Commit-Position: refs/heads/master@{#293003}

BUG=377538
R=jgraettinger@chromium.org

TEST=SpdyNetworkTransactionTest.GoAwayOnPushStreamIdLesserOrEqualThanLastAccepted
     SpdyNetworkTransactionTest.GoAwayOnOddPushStreamId

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

Cr-Commit-Position: refs/heads/master@{#293002}

This memory limit is a lowest-common-denominator type value that should
work for more-or-less all platforms. Currently this value causes
impl-side painting to increase the size of the renderer process resident
memory, which is causing memory regressions on the perf bots.

But, having enough memory for 2 frames seems excessive as the baseline
since in the common case we need to upload resources for the next
compositor deadline that will be presented at the next vsync. So, remove
the 2x multiplier from this constant value.

R=reveman
BUG=407193

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

Cr-Commit-Position: refs/heads/master@{#293001}

BUG=

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

Cr-Commit-Position: refs/heads/master@{#293000}

R=primiano

BUG=

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

Cr-Commit-Position: refs/heads/master@{#292999}

BUG=

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

Cr-Commit-Position: refs/heads/master@{#292998}

Rather than complicating the API with proposals of key re injection, or runtime registration/deregistration (which we might want for other reasons in the future), here's a very simple change that would probably give us the same functionality. If an extension remove all chrome.commands.onCommand listeners, then they will no longer receive the onCommand event and thereafter, the browser should continue propagating the key event and not drop it. I think this is actually the correct behavior, but also allows extension authors to have a little more control over when a command should be processed.

BUG=407163

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

Cr-Commit-Position: refs/heads/master@{#292997}

BUG=none
TBR=mukai@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#292996}

They should no longer be flaky/crashing because the underlying watch manager is
new, shiny, and more stable.

BUG=390979

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

Cr-Commit-Position: refs/heads/master@{#292995}

This is the first in a series of CLs intended to reduce the amount of caching
in docserver code. The @Cache annotation is used to indicate that compiled data
should be cached in CompiledFileSystem.

NOTRY=True

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

Cr-Commit-Position: refs/heads/master@{#292994}

In https://codereview.chromium.org/473643002/ we added a button for users in the
"Remember Certificate Error Decisions" experiment to allow them to revoke their
decision to bypass an SSL error for a given host. This commit adds an UMA
histogram to count how often a hard revoke actually occurs.

BUG=262615
R=felt@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#292993}

Android's vsync listener will now only dispatch a BeginFrame message if
such was requested. This exposed a hole in our BeginFrame request
pipeline, where short-circuited touch forwarding would bypass the vsync
request. Instead, always request the BeginFrame if a touch event was
received from the platform, potentially reducing the first frame's
latency when the page lacks a touch handler.
latency.

BUG=408377

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

Cr-Commit-Position: refs/heads/master@{#292992}

Without this I get compile errors in motion_event_web.cc because M_PI
is undeclared.

BUG=409940
TEST=none
R=scottmg@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#292991}

BUG=380875
R=xiyuan@chromium.org
TEST=build succeeds

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

Cr-Commit-Position: refs/heads/master@{#292990}

Recorded additional tough_energy_cases.
Moved all test cases to codepen, so they're easy to edit and all http.

BUG= 386152

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

Cr-Commit-Position: refs/heads/master@{#292989}

In a previous attempt to prevent SadTab pages from being zoomable we
attempted to use RenderProcessHost::HasConnection, but this fails in
the case where a new tab can be started in the same RenderProcessHost
while the SadTab is still visible. This CL switches to testing to see
if the RenderView for the tab in question is live in order to avoid
this problem.

BUG=407562

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

Cr-Commit-Position: refs/heads/master@{#292988}

NOTRY=True

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

Cr-Commit-Position: refs/heads/master@{#292987}

.. and switch evil network profile for bad network profile

BUG=356842

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

Cr-Commit-Position: refs/heads/master@{#292986}