GitLab

Bug: 843366
Change-Id: Ifa1d702a1357e4f508f708b5cf9783d0db90ad06
Reviewed-on: https://chromium-review.googlesource.com/1062009Reviewed-by: Brandon Jones <bajones@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559190}

This CL removes the sizing-tiny breakpoint from the media controls,
since there are no CSS differences between the sizing-small and
sizing-tiny classes.

This CL also avoids setting the sizing-* classes on audio controls (and
video controls acting as audio controls) in order to avoid unwanted
CSS changes for the audio controls.

Bug: 839088
Change-Id: I3c9ba1119572d0b0f8bec6d8f6c261ff192c96f3
Reviewed-on: https://chromium-review.googlesource.com/1060281Reviewed-by: Becca Hughes <beccahughes@chromium.org>
Commit-Queue: Tommy Steimel <steimel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559189}

https://chromium.googlesource.com/angle/angle.git/+log/80c32ccbbcc6..e943df226e2b

$ git log 80c32ccbb..e943df226 --date=short --no-merges --format='%ad %ae %s'
2018-05-15 geofflang Add more dEQP EGL expectations for Linux and Android.

Created with:
  roll-dep src/third_party/angle


The AutoRoll server is located here: https://angle-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=ynovikov@chromium.org

Change-Id: I7a197d7aecefe6b74636da1804603ecfad5546d8
Reviewed-on: https://chromium-review.googlesource.com/1062005Reviewed-by: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#559188}

This change removes all code related to the Physical Web.

BUG=826540

Change-Id: Ifda5d80c5cebeedf2e2fdf48142e6dd6c1ef73b6
Reviewed-on: https://chromium-review.googlesource.com/1054335Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Reviewed-by: Matt Reynolds <mattreynolds@chromium.org>
Commit-Queue: Conley Owens <cco3@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559187}

Bug: 823365
Change-Id: Ied4f19b6a565e171e8cf8cd0e16189a8c7f29752
Reviewed-on: https://chromium-review.googlesource.com/1062011
Commit-Queue: David Bokan <bokan@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559186}

The presubmit check warning for correct include guards would
trigger for generated files in third_party/win_build_output. Since
files in third_party is often not written with the Chromium style
guide in mind that is over zealous so this patch stops
checking their names (except for in blink).

The presubmit code will still check the existence of a guard since
lack of one can cause problems outside the module and there has been
no reports of false warnings.

This patch also removes the exceptions that used to be there for
blink since blink has moved and been reformatted.

Bug: 814776
Change-Id: Ic7f2bbba5b9bcafbb5bec15b79b04d5e81994b77
Reviewed-on: https://chromium-review.googlesource.com/1061698Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Daniel Bratell <bratell@opera.com>
Cr-Commit-Position: refs/heads/master@{#559185}

Those tests are all green on flakiness dashboard. It's time to give
them a chance.

TBR=junov

Change-Id: I0dfaaa9eddb3aa63bae0d4b4c78f9f5ddfef9445
Reviewed-on: https://chromium-review.googlesource.com/1062081Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Commit-Queue: Fernando Serboncini <fserb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559184}

Plumbs through enough of the app.beep() callback path so that we
can prove that JavaScript was executed in the PDF plugin. We do
not actually produce any sound, since beeps are annoying. It is
just a convenient pre-existing side-effect free hook to test.
The path is almost built-out, and the size cost to complete it
is small.

Precursor to disabling JavaScript; we first need to have an
end-to-end test that proves it runs in the PDF before introducing
a test that shows it doesn't run when disabled.

Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I7e7338f0c44ad2c4fe72b8b06efd88bd8b37ebd0
Reviewed-on: https://chromium-review.googlesource.com/1058550Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Tom Sepez <tsepez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559183}

1) Image shaders are currently first decoded at the raster scale, but
then serialized at the original size. This is because all the decoding
happens in ScopedRasterFlags, but eventually the serialization needs to
happen in PaintOpWriter. For record shaders, we would overwrite the
shader with the correct scale, that would eventually be used in raster.

Clean up all of this to not use ScopedRasterFlags for any image
decoding during serialization. The logic for getting the scales is
pulled into common methods on PaintShader used by ScopedRasterFlags
for in process raster, and PaintOpWriter for oop serialization. This
also fixes #3.

2) When decoding an image using the ImageProvider, a component of the
scale is already applied to the decoded image. This needs to be
accounted for during raster, which is missed for oop-r. Fix this by
adding this scale to DrawImage/DrawImageRect ops. Image shaders
already take care of this on their local matrix.

3) Decoding of PaintRecord backed shaders also fixes the raster scale
for them. But since this was being done in ScopedRasterFlags, we would
only do them for cases where these records have images. In order to get
the font analysis correct for oop-r, this needs to be done for records
with text also. This change ensures that we always serialize scaled
records for these shaders, ensuring that we use the same scale during
font analysis and raster.

R=enne@chromium.org

Bug: 829622
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: If567d192220450306b15b94993c86e610c7885cb
Reviewed-on: https://chromium-review.googlesource.com/1053528
Commit-Queue: Khushal <khushalsagar@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559182}

Bug: 842232
Change-Id: I9de002edb847154f19194dc910492d9bc2fcbe74
Reviewed-on: https://chromium-review.googlesource.com/1062146
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Reviewed-by: Emily Hanley <eyaich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559181}

This CL shapes the role of a KeyboardAccessoryData.Tab element:
It is an element that provides a specific benefit to the Manual UI by...
... providing data that is used by the bar to render a tab (upcoming)
... providing the content for a separate tab in the bottom sheet.

This means, that the bottom sheet provides space for tabs and manages the
general visibility and active states of tabs.
The exact content of a tab doesn't matter to the AccessorySheetComponent.
That way, it should become fairly straight forward to implement a new tab
that is rendered into bottom sheet and accessory.

The first concrete instance of a bottom sheet will follow soon: a
bottom sheet that contains password related actions and data.
(It's important to not mix this specific data into the AccessorySheet
component as other upcoming sheets are already planned, like one for
payments and one for address data.)

Bug: 811747
Change-Id: Id8bd8c389496246166d26a6c298056a142c36566
Reviewed-on: https://chromium-review.googlesource.com/1047285
Commit-Queue: Friedrich Horschig <fhorschig@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559180}

BUG=843596

Change-Id: I4846edc879c2b913ba558cbfb7884836d398aabc
Reviewed-on: https://chromium-review.googlesource.com/1062018Reviewed-by: Maria Khomenko <mariakhomenko@chromium.org>
Commit-Queue: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559179}

Changes to these externs are mechanical and already enforced by a presubmit
check, so it doesn't make sense to get owners review most of the time. We'll
use our best judgement and loop in an owner if the change is nontrivial.

NOTRY=true

Bug: none
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I8a4ab89ae7cf231cffcf313b631b3c878b693b31
Reviewed-on: https://chromium-review.googlesource.com/1062075
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559178}

Part of ongoing effort to enable ChromeVox in
chromecast.  This CL added a required message filter
to handle I18nGetMessage.

Bug: b/73383411
Test: None
Change-Id: I5d704397ae789e4ca72c15e0240a079b2ddc43ac
Reviewed-on: https://chromium-review.googlesource.com/1058082Reviewed-by: Alex Sakhartchouk <alexst@chromium.org>
Commit-Queue: Randy Rossi <rmrossi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559177}

This is needed in order to migrate the devicemotion layout tests over to
using mock generic sensor services. The old devicemotion events are backed
by 3 different generic sensor types, so the MockSensorProvider needs to be
able to mock and allow tests to get references to multiple types of
sensors at the same time in order for these tests to mock out everything
they use.

Bug: 802815
Change-Id: I254c37d67db0e9c6feb639080394305b41f6b7e6
Reviewed-on: https://chromium-review.googlesource.com/1060477Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Robbie McElrath <rmcelrath@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559176}

Previously we used the deprecated NotificationUiService::CancelAll
via BrowserCloseManager to do this. That used the MessageCenter
singleton directly, which worked with in-process Ash but not oop Ash.
By listening for profile shutdown in the NotificationPlatformBridge, we
can accomplish the same thing and it works in oop Ash as well.

This is a roundabout way of fixing the bug, which AFAICT is a race
between the Profile object shutting down and Ash asynchronously (via
mojo) notifying of a notification toast closing. I couldn't figure out
how to trigger this race, hence no direct test.

Bug: 842705
Change-Id: I5913bcb3077450433e26ba6cc7397e17211bc9a6
Reviewed-on: https://chromium-review.googlesource.com/1058491Reviewed-by: Yoshiki Iguchi <yoshiki@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559175}

Bug: 798569
Change-Id: I476672a73ba64ee28d399686d0ecfc4c26690936
Reviewed-on: https://chromium-review.googlesource.com/1060579Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559174}

The preload functionality causes more problems than it solves. Content
that wants to delay loading until the sheet is opened can do so using
events provided by the BottomSheetObserver. This fixes a race
condition in EoC that would cause the sheet to peek before being
requested.

Bug: 834923,843267
Change-Id: If5c35e22a502e42f6bc591784b4fb8343e713eff
Reviewed-on: https://chromium-review.googlesource.com/1060353
Commit-Queue: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559173}

Also servicified ClearNetworkErrorLogging as it's extremely similar
logic.

Moved the clearing on DATA_TYPE_COOKIES to BrowsingDataRemoverImpl as it
is not chrome-specific, and left the clearing on DATA_TYPE_HISTORY in
ChromeBrowsingDataRemoverDelegate. Especially good cleanup for Reporting
data as the two cases were split into two independent Clear... methods
in NetworkContext.

Bug: 824997
Change-Id: Ie13ef2277d9040f73e87b77be49ba47305462aab
Reviewed-on: https://chromium-review.googlesource.com/1045206
Commit-Queue: Eric Orth <ericorth@chromium.org>
Reviewed-by: Martin Šrámek <msramek@chromium.org>
Reviewed-by: Helen Li <xunjieli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559172}

Essentially this boils down to during min/max auto/percent/calc should be
treated the same, either being border+padding or infinity.

And during layout they should be taken into account.

I added some tests which now match FF/Edge (004,005) which LayoutNG matches, but
existing layout fails. The primary difference is change by passing kContent into
ResolveBlockLength during the ComputeBlockSizeForFragment function.

Bug: 635619
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I4e0c171a0e29ea5d85a742d85df001647813c1f3
Reviewed-on: https://chromium-review.googlesource.com/1056291
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559171}

Due to ink drop effects on the caption buttons, they're painted to
layers. This doesn't work in immersive fullscreen mode and causes
the buttons to disappear. This CL fixes them by adding them temporarily
as children of the TopContainerView which is already painting to
layer in immersive mode, and is resposible for painting its sibling
BrowserNonClientFrameViewAsh.

BUG=840242,787640

Change-Id: I8353f3d393fc5113deb7776b742da64aa386c9a0
Reviewed-on: https://chromium-review.googlesource.com/1052675
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559170}

The test times out randomly (~10%) since Build #13171:
http/tests/security/powerfulFeatureRestrictions/old-powerful-features-on-insecure-origin.html

TBR=jam@chromium.org

Bug: 729849
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: I2eec60a97836aff470894faaaebc2e3260cce996
Reviewed-on: https://chromium-review.googlesource.com/1062073
Commit-Queue: Chong Zhang <chongz@chromium.org>
Reviewed-by: Chong Zhang <chongz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559169}

GetFileSize can be used to estimate buffer size if file size is
available. So use it as a hint for buffer size for file reading.
Also avoid latest fread syscall in reading loop using feof.

Bug: 821262
Change-Id: I7dc30483a2f95d4da2c0d3cb0049941d2634a281
Reviewed-on: https://chromium-review.googlesource.com/958861
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559168}

- Add kAnswerCard result type for answer card result;
- Pass answer card preferred size via mojo;
- SearchResultAnswerCardView creates RemoteViewHost only when the
  embedding token changes because the token could be used only once;
- SearchResultWebContents re-creates RemoteViewProvider to ensure
  a valid embedding token in case existing token is invalidated
  when swapping cards but the browser is not aware of that when
  creating a new card;

Bug: 812434
Change-Id: I2a8b61974c46b779d8a61a571e95d8003b2bc123
Reviewed-on: https://chromium-review.googlesource.com/1060280Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559167}

Rather than use `third_party/android_tools/sdk` and
`third_party/android_ndk`, create and use the default `~/Android/Sdk`
directory instead for Android Studio. This allows a consistent dev
environment that does not change per-repository and also allows frequent
updates without affecting each checkout.

Necessary for native support and emulators. This will become the default
in the near future. For now, use:

build/android/gradle/generate_gradle.py --sdk AndroidStudioDefault

Bug: 840542,620034
Change-Id: Ia482cb2982472410fe9c515c5f5f9856f3eadfaf
Reviewed-on: https://chromium-review.googlesource.com/1058308
Commit-Queue: Peter Wen <wnwen@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Reviewed-by: Eric Stevenson <estevenson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559166}

Updates platform handle wrapping/unwrapping API signatures to be more
extensible for a stable ABI, and adds support to shared memory region
wrapping/unwrapping for writable regions, which may be represented by
multiple platform handles on some platforms.

TBR=bajones@chromium.org

Bug: 826213,842037
Change-Id: Ia0e5da7b7e0f4c41853eb3a8d4a12da47071dd8c
Reviewed-on: https://chromium-review.googlesource.com/1058440Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Jay Civelli <jcivelli@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Ken Rockot <rockot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559165}

Bug: 831252
Change-Id: Ib447d09769d5ea4de8079a494cfc2e6ceaad5423
Reviewed-on: https://chromium-review.googlesource.com/1061581Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Emily Hanley <eyaich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559164}

Componentisation CL for "Assessment Assistant".

PRD:
https://docs.google.com/document/d/15CNvkRKuuA6_n5TEtq4vYqb6MDQIy2lq-Ci6lSKMPac

DD:
https://docs.google.com/document/d/1x8JB5nMiCztrpnl7IseIkFRym1Ww3bRWSaXSObfsRHo

Bug: chromium:813711
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I11b62d6a4b59962065c437030085f5b2300b3e2a
Reviewed-on: https://chromium-review.googlesource.com/1030452Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: Ivan Šandrk <isandrk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559163}

Previously this was stubbed in using a background color. Now, we will
show the desired icon when using keyboard input modality.

See bug for demo.

Bug: b:79770465
Change-Id: Ib053e5aa7cb21edf8420c695710b10ed43f284a4
Reviewed-on: https://chromium-review.googlesource.com/1060429Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Evan Stade <estade@chromium.org>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: David Black <dmblack@google.com>
Cr-Commit-Position: refs/heads/master@{#559162}

This patch fixes RTL 'text-align: start|right|center' not to
shift the line by the amount of trailing spaces.

Bug: 636993
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I99165bae187f7e76f183da20ce7a1909b10d1fc5
Reviewed-on: https://chromium-review.googlesource.com/1061273
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559161}

Enterprise policy allows for blocking extension access to a set of
hosts (defined by URLPatterns). In the code, these are referred to
frequently as RuntimeBlockedHosts; however, this is confusing with
the RuntimeHostPermissions feature. Instead, name the enterprise
policy-restricted hosts PolicyBlockedHosts to avoid ambiguity.

Leave the string entry in the policy the same for backwards
compatibility.

Bug: None

Change-Id: Icfa455e2912e3c05da58f0a0b0b8e53395d4e103
Reviewed-on: https://chromium-review.googlesource.com/1060526
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559160}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/41835253..f6054012

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org

Change-Id: Ibc05c77051c21bf58f16c3faa66615a3ae0603d5
Reviewed-on: https://chromium-review.googlesource.com/1061593Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559159}

PasswordBranding was an experiment to change how Chrome's password
manager is called. It has been removed from Chrome over a year ago [1],
but the last reference in the test config was forgotten. This CL removes
it.

[1] In 57.0.2958.0, by https://codereview.chromium.org/2579823003.

Bug: 799180
Change-Id: Ic003dcb375c490e5d72be6d495962e9860e8bbb1
Reviewed-on: https://chromium-review.googlesource.com/1061694Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Commit-Queue: Vaclav Brozek <vabr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559158}

This change updates CompositorImpl and DelegatedFrameHostAndroid with
the necessary logic to create a Viz process.

TBR=piman@chromium.org

Bug: 732555
Change-Id: I9290aeec317a95cd375a8a3ba0867a3c1548c52f
Reviewed-on: https://chromium-review.googlesource.com/1055626Reviewed-by: Eric Karl <ericrk@chromium.org>
Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Reviewed-by: Khushal <khushalsagar@chromium.org>
Reviewed-by: Saman Sami <samans@chromium.org>
Commit-Queue: Eric Karl <ericrk@chromium.org>
Commit-Queue: Saman Sami <samans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559157}

https://chromium.googlesource.com/external/github.com/google/googletest.git/+log/045e7f9ee4f9..08d5b1f33af8

$ git log 045e7f9ee..08d5b1f33 --date=short --no-merges --format='%ad %ae %s'
2018-05-09 jaeheonlee Use NULL instead of nullptr, for pre-C++11 builds.
2018-05-07 jaeheonlee Fix the bug where ad_hoc_test_result() functions of UnitTest and TestCase objects would return failures registered at TestCase and UnitTest scopes, respectively.

Created with:
  roll-dep src/third_party/googletest/src

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:win_optional_gpu_tests_rel;master.tryserver.chromium.win:win_chrome_official;master.tryserver.chromium.linux:linux_chromium_cfi_rel_ng
Change-Id: Ifb056d881111f364644cd76331e833961ad9042d
Reviewed-on: https://chromium-review.googlesource.com/1061579Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559156}

This fixes the issue when ARC++ window goes in/out full-screen or
minimized/restored. In this case a window is removed deep inside
the top ARC++ window and this triggers the wrong logout time
activation.
On removing l
This CL checks removing window that belongs to tracked top windows and
ignored hierarchy change events for other child windows.

Test: Manually + unit test
Bug: b/79169326
Change-Id: I825dd9d16d32ce305d43003fb2e77194cfc5ca7c
Reviewed-on: https://chromium-review.googlesource.com/1045827
Commit-Queue: Yury Khmel <khmel@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559155}

https://chromium-review.googlesource.com/c/chromium/src/+/818075
moved the chromium.clang waterfall to generated json files.  It tried
to match the existing waterfall setup, but the difference in tests
wasn't really intentional (and I was on leave when that change happened
and nobody else familiar with the waterfall was cc'd on that change),
so undo most of the exceptions added there.

While here, also remove now-nonexistent bot 'ThinLTO Linux ToT',
and latency_tests to 'Linux Tests', run nacl_helper_nonsfi_unittests
on 'Linux Chromium OS ASan LSan Tests (1)', and metrics_python_tests
on 'Win7 Tests (dbg)(1)'.

On chromium.clang, adds
- nacl_helper_nonsfi_unittests
- services_unittests
- viz_unittests
- blink_heap_unittests
- blink_platform_unittests
- crashpad_tests
- webkit_unit_tests
- wtf_unittests
- net_unittests
- components_browsertests
- extension_browsertests
- gn_unittests
- native_theme_usertests
- nacl_loader_unittests
- storage_unittests
- latency_unittests
- mac_installer_unittests
- content_shell_crash_test
- metrics_python_tests
- device_unittests
- views_unittests
on at least one of the bots.

Most of these should pass at least, and since they run on swarming
hopefully they won't slow down the bots too much. Maybe I'll have
to undo some of this again as a follow-up though.

Bug: 843511
Change-Id: I3b6f0619c97d86d8768d10572a3c8beca20cea67
Reviewed-on: https://chromium-review.googlesource.com/1060293
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Hans Wennborg <hans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559154}

We no longer need Narrow dropdown UI experiment because it's been
adopted as part of the Material Refresh spec.

Bug: NONE
Change-Id: Iaf33efbd7e6f86321956290165d13dad69272c48
Reviewed-on: https://chromium-review.googlesource.com/1056148
Commit-Queue: Tommy Li <tommycli@chromium.org>
Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Reviewed-by: Trent Apted <tapted@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559153}

This adds a new component //gpu/vulkan/init that fills the same role as
//ui/gl/init. It will allow ozone ports to provide the factory functions
for surface types while still having a centralized entry point for
initializing vulkan.

Certain factory functions (e.g. VulkanSurface::CreateViewSurface) moved
into a new VulkanImplementation factory object; platforms override those
functions in order to build the right surface type.

Common code for surface creation moved into VulkanSurface from its single
anonymous subclass (VulkanWSISurface). This means VulkanSurface is not a
pure interface anymore, but neither are any of the other wrapper classes.
We could alternatively keep the pure interface and provide a "base"
subclass to inherit from, but it's not clear that such a separation is
useful.

This also removes the VkInstance from the global scope. Nothing depended
heavily on the fact that it was global, and since the vulkan API supports
instancing of vulkan itself, it seems better to pass the instance
directly into any components where it is needed. This makes any sharing
explicit and makes instancing possible. Also, the VkInstance could not
previously be destroyed, but now this is supported and exercised by the
test suite.

The Android code is also moved into this scheme, although it seems
incomplete prior to this change, does not compile, and is therefore
untested.

Bug: 581471
Test: vulkan_tests

Change-Id: Icefe29b0bfd4fe5ff2c951cefc47b0472250bce7
Reviewed-on: https://chromium-review.googlesource.com/1055824
Commit-Queue: Michael Spang <spang@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559152}

The hashing algorithm changes depending on the authentication method, and also
possibly based on state in cryptohome (see cryptohome_authenticator.cc). A
cryptohome key can dynamically specify which hashing algorithm it uses.

Remove the SyncPasswordData mojom type; it will be computed automatically with
the plain-text password.

In the future, all cryptohome-related logic should be moved to ash. This will be
more feasible after webui login is gone. Then, we should be able to eliminate
the browser process ever having access to the plain-text or hashed password.

In terms of security, this causes no regression compared to webui-based login.

Bug: 826773
Change-Id: I9258be00afe151ffc0b8f61aafeb2b42ba8d12ff
Reviewed-on: https://chromium-review.googlesource.com/1052381Reviewed-by: Mattias Nissler <mnissler@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Jacob Dufault <jdufault@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559151}