Publish DEPS for Chromium 44.0.2403.156
Incrementing VERSION to 44.0.2403.156
Cr-Commit-Position: refs/branch-heads/2403@{#609}
Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
[Merge to M44] Restore potentially missing Active Setup keys following an OS upgrade.
Without this change the latest changes to trigger Active Setup on
update to system-level Chromes fail.
Also cleanup some documentation to be more accurate.
BUG=488247
TEST=
1) Install setup.exe --chrome --multi-install --system-level
2) Delete HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Active Setup\Installed Components\{8A69D345-D564-463c-AFF1-A69D9E530F96}
3) As admin, run the command @ HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Google\Update\Clients\{8A69D345-D564-463c-AFF1-A69D9E530F96}\Commands\on-os-upgrade
4) Verify that it restored the key in (2.) and bumped the OS upgrade component (i.e. 43.0.1.0).
Review URL: https://codereview.chromium.org/1274043002
Cr-Commit-Position: refs/heads/master@{#343191}
(cherry picked from commit 7e0b5ad5fce6f7bd9ad7aef65f4b2e3f19001463)
[email protected]
Review URL: https://codereview.chromium.org/1289053002 .
Cr-Commit-Position: refs/branch-heads/2403@{#608}
Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
[Merge to M44] Do not force restore shortcuts on OS upgrades.
And update some documentation.
Related helper method to be cleaned in a follow-up CL.
BUG=502363
Review URL: https://codereview.chromium.org/1275023005
Cr-Commit-Position: refs/heads/master@{#343179}
(cherry picked from commit 5da23b096ded2291158b232abe238150af623a9c)
[email protected]
Review URL: https://codereview.chromium.org/1287403002 .
Cr-Commit-Position: refs/branch-heads/2403@{#607}
Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
Remove captive portal check from oauth2 token fetcher.
BUG=501179
Review URL: https://codereview.chromium.org/1290943002
Cr-Commit-Position: refs/heads/master@{#343157}
(cherry picked from commit fc1ed9cd427a42d17a3fc91d6ccf9a5cd8321a31)
Review URL: https://codereview.chromium.org/1293503003 .
Cr-Commit-Position: refs/branch-heads/2403@{#606}
Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
Only reset stored certificate exceptions on schemes that are cryptographic.
If the user had previously accepted a certificate error for a given host, and then encounters a good certificate on that host, the exception will be reset (revoked), so that the user will be prompted the next time a bad certificate is encountered. However, because this SSLPolicy method is called for all loads (including non-SSL loads), loading an HTTP resource w/o error would be treated as if a good certificate was encountered, and (incorrectly) reset the exceptions. Instead, only reset the exceptions when the scheme for the good load is cryptographic (e.g. https, wss), since those are the only schemes that can deliver good certificates.
BUG=473390
[email protected],[email protected]
Review URL: https://codereview.chromium.org/1249703004
Cr-Commit-Position: refs/heads/master@{#339985}
(cherry picked from commit 597c8d6d5fdb0b93506a41715c8744783cfd5ba8)
Review URL: https://codereview.chromium.org/1295493003 .
Cr-Commit-Position: refs/branch-heads/2403@{#605}
Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
Revert broken Linux hidpi changes.
This reverts the following:
commit 5cb0c01e4233ff3eb1e7f6f677b4cf9dae9ffaf2
Author: oshima <[email protected]>
Date: Fri May 15 15:16:07 2015 -0700
Compute the base dpi from X
[email protected], [email protected]
[email protected], [email protected]
BUG=485183
NOTRY=true
NOPRESUBMIT=true
Review URL: https://codereview.chromium.org/1276553007
Cr-Commit-Position: refs/heads/master@{#342381}
(cherry picked from commit 6b72d5275f43b0fdcaa6029859e5e506f005c7bb)
Review URL: https://codereview.chromium.org/1284343004
Cr-Commit-Position: refs/branch-heads/2403@{#604}
Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
Merge to M44: "Fix WASAPI restriction to be based on period size; fixes Win10."
The code was forcing the output buffer size to be an even divisor
of endpoint buffer size; in seemingly 90%+ of cases this worked
prior to Windows 10. With Windows 10, the device period is no
longer an even divisor of the endpoint buffer size; e.g. my
local machine has a period of 512 and a endpoint buffer of 1126.
In retrospect this restriction seems incorrect; instead it seems
like we just want to ensure that the buffer size is an even divisor
of the device period (which ultimately determines the callback
schedule). I've changed the code to log a warning when this is not
the case, as things will still work, we'll just get glitches. The
log will help us identify users who file bug reports.
The code was also looping over the available end point buffer size,
which seems incorrect, we should fulfill only one period at a time to
avoid shared-memory induced glitches; this was added to fix
http://crbug.com/170498
BUG=516196
TEST=Windows 10 audio works on two devices, Windows 7 works fine,
traces show that callbacks are regular in all cases. Confirmed that
http://crbug.com/170498 is not regressed on X-Fi.
TBR=tommi
Review URL: https://codereview.chromium.org/1276523004
Cr-Commit-Position: refs/heads/master@{#342334}
(cherry picked from commit a7be0758c5f97679d0aed6b7f8c1f395d0d62d5c)
Review URL: https://codereview.chromium.org/1289433003 .
Cr-Commit-Position: refs/branch-heads/2403@{#603}
Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
Send 2 words of feedback on each side of misspelling.
[email protected]
BUG=517616
Review URL: https://codereview.chromium.org/1277003005
Cr-Commit-Position: refs/heads/master@{#342258}
(cherry picked from commit 8c3ba77d2f3e3a802f9c3e00bc17fb0cfa9e2a41)
Review URL: https://codereview.chromium.org/1282333005 .
Cr-Commit-Position: refs/branch-heads/2403@{#602}
Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
