Publish DEPS for Chromium 56.0.2924.87
Incrementing VERSION to 56.0.2924.87
Cr-Commit-Position: refs/branch-heads/2924@{#895}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
DevTools: Fix SuggestBox not showing without a maximum height
BUG=670581
Review-Url: https://codereview.chromium.org/2554173002
Cr-Commit-Position: refs/heads/master@{#436775}
(cherry picked from commit 60923e44a7116db275bf8c74b1cd52ba2335b1af)
Review-Url: https://codereview.chromium.org/2668503006 .
Cr-Commit-Position: refs/branch-heads/2924@{#894}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
DevTools: Add more Mac shortcuts into CodeMirrorTextEditor
MacOS has a lot of Emacs-style keyboard shortcuts that we lost when
moving the console from contenteditable to CodeMirror.
BUG=671269
Review-Url: https://codereview.chromium.org/2559603002
Cr-Commit-Position: refs/heads/master@{#437457}
(cherry picked from commit 247b2e4c45b9e2504c54a0725f39df52d8c071b2)
Review-Url: https://codereview.chromium.org/2664233003 .
Cr-Commit-Position: refs/branch-heads/2924@{#893}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
[Merge M-56] Display "Not secure" verbose state for data: URLs
data: URLs don't define a secure context, and are a vector for spoofing.
Display a "Not secure" badge for all data URLs, regardless of whether
they show a password or credit card field.
BUG=684811
TBR=estark
NOTRY=true
NOPRESUBMIT=true
Review-Url: https://codereview.chromium.org/2648353005
Cr-Commit-Position: refs/heads/master@{#446536}
(cherry picked from commit effd1d519ff74fb1eb998e844f19d5079222b0fd)
Review-Url: https://codereview.chromium.org/2666783006
Cr-Commit-Position: refs/branch-heads/2924@{#892}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
Incrementing VERSION to 56.0.2924.86
Cr-Commit-Position: refs/branch-heads/2924@{#891}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
Incrementing VERSION to 56.0.2924.85
Cr-Commit-Position: refs/branch-heads/2924@{#890}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
Fix -full fallback for diff updates (M56).
mini_installer will now report state properly regardless of whether
updates are being delivered via Chrome's or the binaries' app guid:
- "-full" is added to Chrome's "ap" value and, in case an existing
multi-install Chrome is being updated, the binaries' "ap" value.
- Installer results are written to Chrome's ClientState key and, as
above, the binaries'.
This is a partial merge of r438644.
BUG=686645
NOTRY=true
NOPRESUBMIT=true
Review-Url: https://codereview.chromium.org/2663003003
Cr-Commit-Position: refs/branch-heads/2924@{#889}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
Partial merge of https://crrev.com/b8e1ac73c904f3134c4be5fd978ef46de1b95279.
Remove the enable/disable links for the about:plugins page.
The partial merge only removes the links without touching the underlying
code to avoid merge conflicts due to dependency on another CL. Effectively
the result is the same.
BUG=615738,673199
TEST=manual
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
[email protected]
TBR=bauerb
Review-Url: https://codereview.chromium.org/2659373002 .
Cr-Commit-Position: refs/branch-heads/2924@{#888}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
Incrementing VERSION to 56.0.2924.84
Cr-Commit-Position: refs/branch-heads/2924@{#887}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
ozone: Fix how we determine framebuffer formats.
crrev.com/2533163002 changed the way framebuffer fourcc formats are
determined. This caused some drm framebuffer to be added with a format
that has an alpha component, resulting in a black screen when using
those fbs for scanout.
This CL restores the behavior we had before crrev.com/2533163002,
using GetFourCCFormatForFramebuffer to determe the fourcc format
for the framebuffer. In this way formats with an alpha component
will be mapped to their non-alpha version.
BUG=b/34776743,b/33363543
Review-Url: https://codereview.chromium.org/2553813004
Cr-Commit-Position: refs/heads/master@{#436811}
(cherry picked from commit 701c5c613569fc4872184f2311a378c18c117482)
Review-Url: https://codereview.chromium.org/2661063002 .
Cr-Commit-Position: refs/branch-heads/2924@{#886}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
Reland cros: Fix crash from bad ModelViewChannel reference.
Reland https://codereview.chromium.org/2655533002/ after fixing linker error.
BUG=471648
Review-Url: https://codereview.chromium.org/2650403003
Cr-Commit-Position: refs/heads/master@{#446201}
(cherry picked from commit 46abf90a37b72bebf38a005a5349adf799b040be)
Review-Url: https://codereview.chromium.org/2667633002 .
Cr-Commit-Position: refs/branch-heads/2924@{#885}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
Incrementing VERSION to 56.0.2924.83
Cr-Commit-Position: refs/branch-heads/2924@{#884}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
Incrementing VERSION to 56.0.2924.82
Cr-Commit-Position: refs/branch-heads/2924@{#883}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
Incrementing VERSION to 56.0.2924.81
Cr-Commit-Position: refs/branch-heads/2924@{#882}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
Merge 56: Use implicit method of QueryInterface for ICodecAPI
This CL tries to address reported crashes coming from the line where
QueryInterface() is used to check if ICodecAPI interface is supported.
- Add paranoia checks to make sure that |encoder_| is still initialized.
- Use templated/implicit method of QueryInterface to check ICodecAPI.
BUG=682813
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Review-Url: https://codereview.chromium.org/2644393003
Cr-Commit-Position: refs/heads/master@{#445950}
(cherry picked from commit cd9754daf31d0b352130ba49e9ab463d42370297)
NOTRY=true
NOPRESUBMIT=true
[email protected],[email protected]
Review-Url: https://codereview.chromium.org/2658723008
Cr-Commit-Position: refs/branch-heads/2924@{#881}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
Fix a build failure caused by an earlier cherry pick
Cherry-pick: https://codereview.chromium.org/2658573011
BUG=675372,686244
[email protected]
Review-Url: https://codereview.chromium.org/2663553002 .
Cr-Commit-Position: refs/branch-heads/2924@{#880}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
scheduler: Make DOM window event tasks unthrottled
This patch avoids throttling events that are routed via
DOMWindowEventQueue. This affects a handful of window-related events,
the most important ones being IndexedDB events. It turns out many web
pages (e.g., Google Docs) rely on IndexedDB transactions to be
relatively fast and start encountering errors if they are throttled too
aggressively while a tab is in the background.
BUG=675372
Review-Url: https://codereview.chromium.org/2651933002
Cr-Commit-Position: refs/heads/master@{#446000}
(cherry picked from commit 05a13309259dd16f38eef41adc7cce55e3d15a05)
Review-Url: https://codereview.chromium.org/2658573011 .
Cr-Commit-Position: refs/branch-heads/2924@{#879}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
Include build/build_config.h in all component updater files.
All files using conditional compilation must include the build_config,
otherwise the platform symbols are not defined.
Merged to M56.
BUG=684950
Review-Url: https://codereview.chromium.org/2655813002
Cr-Commit-Position: refs/heads/master@{#446050}
(cherry picked from commit 96d71e0c6c152a39ee9b452c96428af7cc4520bc)
Review-Url: https://codereview.chromium.org/2658133003 .
Cr-Commit-Position: refs/branch-heads/2924@{#878}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
Revert of [NTP] Update UiConfig when NewTabPageView is made visible. (patchset #1 id:1 of https://codereview.chromium.org/2658093005/ )
Reason for revert:
Was merged to 56 instead of 57 by mistake.
Original issue's description:
> [NTP] Update UiConfig when NewTabPageView is made visible.
>
> On first run, the NewTabPageView is initialized behind the First Run
> Experience, meaning the UiConfig will pickup the screen layout then.
> However onConfigurationChanged is not called on orientation changes
> until the FRE is completed. This means that if a user starts the FRE in
> one orientation, changes an orientation and then leaves the FRE the
> UiConfig will have the wrong orientation.
>
> Updating the UiConfig in onWindowsVisibilityChanged solves this.
>
> BUG=683886
> [email protected]
> NOTRY=true
> NOPRESUBMIT=true
>
> Review-Url: https://codereview.chromium.org/2657443004
> Cr-Original-Commit-Position: refs/heads/master@{#446048}
> Review-Url: https://codereview.chromium.org/2658093005
> Cr-Commit-Position: refs/branch-heads/2924@{#876}
> Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
> Committed: https://chromium.googlesource.com/chromium/src/+/d30bbd241c8233992be1296515e2abea042bcb06
[email protected]
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=683886
Review-Url: https://codereview.chromium.org/2662593002
Cr-Commit-Position: refs/branch-heads/2924@{#877}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
[NTP] Update UiConfig when NewTabPageView is made visible.
On first run, the NewTabPageView is initialized behind the First Run
Experience, meaning the UiConfig will pickup the screen layout then.
However onConfigurationChanged is not called on orientation changes
until the FRE is completed. This means that if a user starts the FRE in
one orientation, changes an orientation and then leaves the FRE the
UiConfig will have the wrong orientation.
Updating the UiConfig in onWindowsVisibilityChanged solves this.
BUG=683886
[email protected]
NOTRY=true
NOPRESUBMIT=true
Review-Url: https://codereview.chromium.org/2657443004
Cr-Original-Commit-Position: refs/heads/master@{#446048}
Review-Url: https://codereview.chromium.org/2658093005
Cr-Commit-Position: refs/branch-heads/2924@{#876}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
Incrementing VERSION to 56.0.2924.80
Cr-Commit-Position: refs/branch-heads/2924@{#875}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
[Merge M56] Revert "Revert of Don't offer to translate between Simplified and Traditional Chinese (patchset #5 id:80001 of https://codereview.chromium.org/2650003004/ )"
This reverts commit fc1f65c1189b644cd27c8a5fa47861dd4f68859d.
And removes offending <iostream> header from translate_manager.cc.
BUG=683164
NOTRY=true
TBR=groby
patch from issue 2655173003 at patchset 1 (http://crrev.com/2655173003#ps1)
Review-Url: https://codereview.chromium.org/2660573002 .
Cr-Commit-Position: refs/branch-heads/2924@{#874}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
[Merge M56] Fix import legacy, pref based pins.
This CL contains 2 fixes for importing legacy pref based pins.
1. Import may happen at the moment when profile is not synced yet and
in last case it does not actually contain information from previous
bulds.
2. Importing ignores apps that currently are not installed. This
leads to situation that we loose pin information for such apps
and in case apps are installed later they do not appear pinned.
Solution is to import all existings apps in prefs.
BUG=680821
TEST=Clearn app sync server data. Login on M52 and do some pinning.
Next login on M55 and pin additional app. Next login to ToT
and observe that pin is restored for existing apps and
pins appear automatically once apps are installed later.
[email protected]
NOTRY=true
NOPRESUBMIT=true
Review-Url: https://codereview.chromium.org/2646973003
Cr-Commit-Position: refs/heads/master@{#445398}
(cherry picked from commit d8cc9d23b26dc31e050fdc1e2042f639d8a608fa)
Review-Url: https://codereview.chromium.org/2655563002
Cr-Commit-Position: refs/branch-heads/2924@{#873}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}
