GitLab

A child can be "throttled" for an arbitrary length of time if it is never
embedded. This skews blocked duration metrics. Simply don't report those
metrics if a surface is blocked on a parent.

Bug: 890767
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: I3c8a8494a5b1e5a973b2e5c2b61cffe5c2b76f6f
Reviewed-on: https://chromium-review.googlesource.com/c/1274591
Commit-Queue: Fady Samuel <fsamuel@chromium.org>
Reviewed-by: Saman Sami <samans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598886}

To facilitate sharing logic between DataReductionProxyURLLoaderThrottle and DataReductionProxyInterceptor.

Bug: 721403
Change-Id: I8dd9493346d58c1c6fb99b7887d3775645b650a3
Reviewed-on: https://chromium-review.googlesource.com/c/1273950
Commit-Queue: Eric Roman <eroman@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598885}

We need to update the bottom margin on initialization in case that
browser controls constraints are not updated during navigation.

Bug: 884803
Change-Id: I117aa9566b73cd1434d4f8b1331c08688b347573
Reviewed-on: https://chromium-review.googlesource.com/c/1277369Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Becky Zhou <huayinz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598884}

https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Headers.git/+log/a44009e38ccd..801cca810424


git log a44009e38ccd..801cca810424 --date=short --no-merges --format='%ad %ae %s'
2018-10-11 johnkslang@users.noreply.github.com Merge pull request #79 from Thog/csharp-definition


Created with:
  gclient setdep -r src/third_party/spirv-headers/src@801cca810424

The AutoRoll server is located here: https://autoroll.skia.org/r/spirv-headers-chromium-autoroll

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.


TBR=dsinclair@chromium.org

Change-Id: I4d367ec17f47c9412d727f2706a6362615140f49
Reviewed-on: https://chromium-review.googlesource.com/c/1277465Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#598883}

Adds bool parameter for enabling/disabling NTLM on Mount.

Bug: chromium:888096
Change-Id: Ie2f380da0965472b663b8997d21de1c727edb718
Reviewed-on: https://chromium-review.googlesource.com/c/1259286Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Commit-Queue: jimmy gong <jimmyxgong@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598882}

Grab the device scale factor from the client instead (which is more
correct anyway). This will pave the way for getting rid of
OnFirstSurfaceActivation.

Bug: 893731
Change-Id: Ib274ade2fcb3295cc667bf7bcf389e9c83e66d47
Reviewed-on: https://chromium-review.googlesource.com/c/1274452Reviewed-by: Khushal <khushalsagar@chromium.org>
Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Reviewed-by: Eric Seckler <eseckler@chromium.org>
Commit-Queue: Saman Sami <samans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598881}

This reverts commit 8b3faf7c.

Reason for revert: crbug.com/894193

Original change's description:
> Refactor menu footnote unittests
> 
> Bug: 889229
> Change-Id: I7b2a0f0c64b136f7210fda4c6ead654558de1e56
> Reviewed-on: https://chromium-review.googlesource.com/c/1271780
> Reviewed-by: Michael Wasserman <msw@chromium.org>
> Commit-Queue: Nicolas Ouellet-Payeur <nicolaso@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#598076}

TBR=msw@chromium.org,nicolaso@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 889229
Change-Id: Idc3a12270c7f11b84cfc3f6437a85f3472d0f405
Reviewed-on: https://chromium-review.googlesource.com/c/1276545Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Nicolas Ouellet-Payeur <nicolaso@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598880}

crrev.com/c/1156995 introduced a regression in locked fullscreen mode where it
became possible to exit the mode using the controls that auto-hide at the top
of the screen (normally they should be disabled in locked fullscreen mode).

Fix this by disabling immersive mode if we're in locked fullscreen, and also
disable the FullscreenControlHost which shows a bubble exit target when no
other UI is shown.

Bug: 883104
Change-Id: I489e471aed2b3f9f809ad1d11f76b37d6c6b4a00
Reviewed-on: https://chromium-review.googlesource.com/c/1234334
Commit-Queue: Ivan Šandrk <isandrk@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598879}

The KA relies on the FocusedNodeChanged event that it receives as a
RenderFrameObserver. This event however is not triggered when the focus
moves outside the frame (e.g. on the omnibox). In order to detect such
a focus change we use DidEndTextFieldEditing to hide the KA, same as
for the autofill popup.
When the user taps back onto the field DidCompleteFocusChangeInFrame is
called, which leads to the accessory being shown again.

TBR for 1 line in components/autofill/content/renderer/autofill_agent.cc
TBR=dvadym@chromium.org

Bug: 893695
Change-Id: I76a66ce43fad0a74c0abbc10c42d8916fd7e891a
Reviewed-on: https://chromium-review.googlesource.com/c/1268246Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Commit-Queue: Ioana Pandele <ioanap@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598878}

This was added when I thought the bug was a CHECK, but none of the dumps
include any data in the value aliases, which leads me to believe the bug is
that |this| has been deleted.

BUG=867035
TEST=none

Change-Id: I4189b97f62c1a581086cdc6bb4563b54ae3724f2
Reviewed-on: https://chromium-review.googlesource.com/c/1277187Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598877}

Details :
1 - Search filter is cascaded before the type filter in the filter chain,
    hence chips that don't have item types in the search text will be hidden.
2 - Empty view will show a different string when we are in search mode
    and we have no matching results.

Bug: 892332
Change-Id: Ib99534b9c1a0b3f5333d4646356863a8639cd926
Reviewed-on: https://chromium-review.googlesource.com/c/1275140
Commit-Queue: Shakti Sahu <shaktisahu@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598876}

Some of the DCHECKs were disabled due to a bug which was causing
same anchor element to be reported multiple times to the browser process.
Now, since that bug has been fixed, we can reenable some of the
DCHECKs in navigation predictor which ensure that the size occupied
by any target HREF (after aggregating across all anchor elements
that point to the same target) does not exceed 1.0.

Bug: 894092
Change-Id: Iec003a857e8b990bcc01f522e49ed8cdd6191137
Reviewed-on: https://chromium-review.googlesource.com/c/1277372
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598875}

Also fixed swiftshader symbol generation on MacOS

Bug: chromium:719257 chromium:888082
Change-Id: I5e8754c278914c519e71c77ed792f198516a1556
Reviewed-on: https://chromium-review.googlesource.com/c/1276550Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Alexis Hétu <sugoi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598874}

This is a follow up fix for go/cgcl/1272238.

Bug: 893521
Change-Id: I3ea08e13eb0909e7b216448d9cdad2761c5e4647
Reviewed-on: https://chromium-review.googlesource.com/c/1277385Reviewed-by: Alex Newcomer <newcomer@chromium.org>
Commit-Queue: Weidong Guo <weidongg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598873}

The feature will be rolled out gradually to M70 and should be enabled by default on M71

Bug: 850760
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: Ib69d8f919a48be151b282ba78677c19749481723
Reviewed-on: https://chromium-review.googlesource.com/c/1269183
Commit-Queue: Mohammad Refaat <mrefaat@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598872}

This CL adds the metrics for download media parser, so we can
understand the overall reliability of the feature.

TBR=jwd@chormium.org

Bug: 826021
Change-Id: I2f556b3ab206c2a2cdbca9bd8d7d99979cd385a9
Reviewed-on: https://chromium-review.googlesource.com/c/1257859
Commit-Queue: Xing Liu <xingliu@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Reviewed-by: Min Qin <qinmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598871}

Move the existing SadTabBulletSpan to a new
ui/widget/../ChromeBulletSpan.java and re-use for the material design
incognito NTP. This fixes a text wrapping issues caused by the bullet
previously being included in the text string.

BUG=740619,740619

Change-Id: I172ee3e388962efc90d0defe01525828491883cf
Reviewed-on: https://chromium-review.googlesource.com/c/1277376Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598870}

The mobile setup UI loads carrier activation site in a webview.
The webview is initially hidden, and then shown when the carrier
content is loaded. This prevents any interstitial pages from getting
displayed - in particular, an SSL error page in M71+.

While the issue should be fixed server-side, by the carrier, not showing
the interstitial (however scary it is), prevents the user from
proceeding with mobile activation. To unblock testing the flow, update
mobile setup UI to display the webview contents sooner - when the
carrier page load starts (instead of when the navigation to the target
page is committed, which will not happen if interstitial is shown).

BUG=894281

Change-Id: I36de9d00afcf0f058bac95a938381c75d5e9a18e
Reviewed-on: https://chromium-review.googlesource.com/c/1275138Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Toni Baržić <tbarzic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598869}

Bug: 893874
Change-Id: I87c9b49f2142c136c09b534583e9e1b37127faf4
Reviewed-on: https://chromium-review.googlesource.com/c/1275293Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Roger Tawa <rogerta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598868}

Since PictureLayerImpl::AppendQuads and SolidColorLayerImpl
::AppendSolidQuads both use scale=1 for its shared quad state,
pages like chrome://about can generate ~200 SCDQ on hi dpi
phones (e.g. pixel 2).

SolidColorDrawQuads are cheap to draw. In this CL, I re-visited
the tile management and generate only 1 SolidColorDrawQuad.

I tested the performance on cc_scroll_200_layer_grid, and
thread_GPU_cpu_time_per_frame is improved to 2.215 from 2.754.

Performance result summary:
https://x20.corp.google.com/users/yi/yiyix/www/1%20solid%20color%20draw%20quad%20analysis

Bug: 879379

TBR=kbr@chromium.org

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;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I8deaf29d1f0ed8f2d052ff77c8673b4e39877ab6
Reviewed-on: https://chromium-review.googlesource.com/c/1258386
Commit-Queue: Yi Xu <yiyix@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598867}

Now we have an extensive set of tests in draw-high-bit-depth-images.html, we don't need
to extend these tests any more.

NOTRY=true
TBR=fserb@chromium.org

Bug: 713867
Change-Id: I7390b9fe420f35ada44c2e89b7ebdce29952ff4d
Reviewed-on: https://chromium-review.googlesource.com/c/1276891
Commit-Queue: Mohammad Reza Zakerinasab <zakerinasab@chromium.org>
Reviewed-by: Mohammad Reza Zakerinasab <zakerinasab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598866}

This CL is a quick fix for the "green buttons" bug where PWA windows
use the main browser theme colours for frame caption buttons on
Windows 10.

Before: https://bugs.chromium.org/p/chromium/issues/attachment?aid=362481&signed_aid=wZlcGI_yPhzQvEb3LIIImA==&inline=1
After: https://bugs.chromium.org/p/chromium/issues/attachment?aid=362482&signed_aid=oxJ3bwmmjcCErDhvgZue-w==&inline=1

This is a temporary work around for M71 while a more robust fix is
worked on for PWA windows and browser themes:
https://chromium-review.googlesource.com/c/chromium/src/+/1272896

Bug: 891560
Change-Id: Ic5fe4ddc1b8f60011d3b687a78ae2aad5fe7e185
Reviewed-on: https://chromium-review.googlesource.com/c/1275466
Commit-Queue: Bret Sepulveda <bsep@chromium.org>
Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598865}

Many methods in //net use the "int" return type to return either a
net::Error or a number (e.g., bytes read). However, quite a few methods
also use the "int" return type, even though they only return
net::Errors. AppCacheDiskCache, which is built on top of
//net/disk_cache, followed the same pattern.

This CL replaces int with net::Error where applicable in
AppCacheDiskCache. This is intended to help readers distinguish between
methods that return an error code and methods that may return a number
or an error code.

Change-Id: I495d70e1ba2aaf68d6386125c99d2c2f1f14d481
Reviewed-on: https://chromium-review.googlesource.com/c/1274447Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Commit-Queue: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598864}

Since atspi-2 does not support getting version information at compile
time, we must do this manually with pkg-config. Add defines for the
versions of atspi-2 that we care about and guard newer enum values with
those defines.

Bug: 887908
Change-Id: I8eecb2eeada48cc2176117b764adbf77b26ce351
Reviewed-on: https://chromium-review.googlesource.com/c/1238437
Commit-Queue: Martin Robinson <mrobinson@igalia.com>
Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598863}

This eliminates segfaults when the device administrator has prohibited
all multi-device features and fixes some tests which break when the
multi-device flags are enabled by default.

Bug: 884066
Change-Id: I6ac54f2e5c065d8368af6c51eb1a61cfb6b5abd7
Reviewed-on: https://chromium-review.googlesource.com/c/1275307
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Jeremy Klein <jlklein@chromium.org>
Reviewed-by: James Hawkins <jhawkins@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598862}

IsNTLMAuthenticationEnabled checks if NTLM is enabled by policy.

Bug: chromium:888096
Change-Id: If42b2e2125590e3434cdb2be9d931cd4531f1ebe
Reviewed-on: https://chromium-review.googlesource.com/c/1268670
Commit-Queue: jimmy gong <jimmyxgong@chromium.org>
Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598861}

Existing ChromeDriver build script uses Git to determine if it is
built in a release branch. However, some distros build ChromeDriver from
source tarball, detached from Git repository (e.g., see
https://groups.google.com/a/chromium.org/forum/#!topic/chromium-packagers/LxpjcTrAzGA).
This CL updates the build script to handle such cases.

Change-Id: I9c59c90fc94dfa0bfebbbb83584ef7dda7153dc7
Reviewed-on: https://chromium-review.googlesource.com/c/1274894Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598860}

Since non-Android platforms get copies of RenderFrameMetadata and also
support touchscreen devices with pinch, it seems like we should be
exporting page scale factor data for all platforms.

Bug: n/a
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I976813d9d7d0910d8763425733d10ba0b5e41aea
Reviewed-on: https://chromium-review.googlesource.com/c/1234971Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Commit-Queue: James MacLean <wjmaclean@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598859}

Change-Id: I05ec82f95e2a1629d0c51f7f7f942fda5c70a465
Reviewed-on: https://chromium-review.googlesource.com/c/1275949Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Commit-Queue: François Beaufort <beaufort.francois@gmail.com>
Cr-Commit-Position: refs/heads/master@{#598858}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/2146d0609ce9..d75c465bc3db


Created with:
  gclient setdep -r src-internal@d75c465bc3db

The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll

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.


TBR=mmoss@chromium.org

Change-Id: I77aba231ccebbe69836f2105b3dcca0fe32159ef
Reviewed-on: https://chromium-review.googlesource.com/c/1276469Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#598857}

This has been migrated to tryserver.chrome.win on LUCI.

BUG=731383

Change-Id: Ic74dcc5ec53ce4b44b461a182caf91a8a934f012
Reviewed-on: https://chromium-review.googlesource.com/c/1271580Reviewed-by: Eric Foo <efoo@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Michael Moss <mmoss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598856}

Using wpt-import in Chromium 2ca2969a.
With Chromium commits locally applied on WPT:
65d72632 "Make DTMF tone change more deterministic"


Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/25949

Note to sheriffs: This CL imports external tests and adds
expectations for those tests; if this CL is large and causes
a few new failures, please fix the failures by adding new
lines to TestExpectations rather than reverting. See:
https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md

Directory owners for changes in this CL:
cbiesinger@chromium.org:
  external/wpt/css/css-flexbox
foolip@chromium.org, robertma@chromium.org, smcgruer@chromium.org:
  external/wpt/infrastructure
mkwst@chromium.org, andypaicu@chromium.org:
  external/wpt/content-security-policy
rego@igalia.com:
  external/wpt/css/vendor-imports/mozilla/mozilla-central-reftests
rouslan@chromium.org, mathp@chromium.org:
  external/wpt/payment-request

NOAUTOREVERT=true
TBR=foolip

No-Export: true
Change-Id: I6e3e98012f97dded6c88efb258237ea4811783dd
Reviewed-on: https://chromium-review.googlesource.com/c/1276827
Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Reviewed-by: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598855}

By default zx_vmo_create() creates VMOs that can be resized. This is
potentially hazardous (process that tries to access mapped and
resized VMO may crash) while we never need to resize VMOs in chromium.
This change updates SharedMemoryFuchsia and
PlatformSharedMemoryRegionFuchsia to pass ZX_VMO_NON_RESIZABLE to
zx_vmo_create().

Change-Id: Idf48f3c21ad9b253da1c3a99ff79bcdebacccde4
Reviewed-on: https://chromium-review.googlesource.com/c/1275131Reviewed-by: Scott Graham <scottmg@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598854}

Change-Id: Ie637e2bfbf8ad67fbd3fb0334043a15bc477dc34
Reviewed-on: https://chromium-review.googlesource.com/c/1265127Reviewed-by: Will Harris <wfh@chromium.org>
Reviewed-by: Greg Thompson <grt@chromium.org>
Reviewed-by: Samuel Huang <huangs@chromium.org>
Commit-Queue: Samuel Huang <huangs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598853}

https://webrtc.googlesource.com/src.git/+log/f81170b48fd4..cdc959fb4240


git log f81170b48fd4..cdc959fb4240 --date=short --no-merges --format='%ad %ae %s'
2018-10-11 ilnik@webrtc.org Compute video freeze metrics on rendered frames instead of on decoded
2018-10-11 srte@webrtc.org Moves pushback controller to GoogCC


Created with:
  gclient setdep -r src/third_party/webrtc@cdc959fb4240

The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-chromium-autoroll

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:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: I59b30225d024b0f6d97a93c005dea272b09d3d7d
Reviewed-on: https://chromium-review.googlesource.com/c/1276555Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#598852}

Change-Id: Ib1ed6433c4166f42df1728d3f5e9322806a7128d
Reviewed-on: https://chromium-review.googlesource.com/c/1273523Reviewed-by: Robert Phillips <robertphillips@google.com>
Commit-Queue: Mike Klein <mtklein@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598851}

The swapbuffers call got lost in f8ffa6f2 ("viz: Separate
SkiaRenderer's code path by compositing mode") in the conversion from
if/else to switch/case.

Bug: 644851
Test: content_shell --enable-vulkan --disable-gpu

Change-Id: I93e030f9d0f5db10b9cb05e443c8454e0ded73de

Reviewed-on: https://chromium-review.googlesource.com/c/1274897Reviewed-by: enne <enne@chromium.org>
Reviewed-by: weiliangc <weiliangc@chromium.org>
Commit-Queue: Michael Spang <spang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598850}

Android defaults target determination to prompt. However, in the
case of resumption, we should not prompt user. Instead, we should
simply uniquify the file name
The issue is fixed in https://codereview.chromium.org/2618743006/
But reintroduced by https://chromium-review.googlesource.com/c/chromium/src/+/465566

BUG=894134

Change-Id: If05394eb9970f79c91770a29fc7761d41228c92e
Reviewed-on: https://chromium-review.googlesource.com/c/1275129Reviewed-by: David Trainor <dtrainor@chromium.org>
Reviewed-by: Xing Liu <xingliu@chromium.org>
Commit-Queue: Min Qin <qinmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598849}

Re-resubmit cr/1261477

The issue was that there is a race condition between the abort going
through, and the downloaded file being persisted on disk. I added an
extra check in the WPT test.

Change-Id: I98aa005b4637c08f60a126a6c7c896c1c0edfddf
Reviewed-on: https://chromium-review.googlesource.com/c/1276557
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598848}

The test registered-property-computation.html fails on wpt.fyi, because
it assumes that the tests are run in a viewport with specific dimensions.

This CL fixes that by using a standard property as a reference. For
instance, to figure out the expected value in pixels for '10vw', we
compute min-height:10vw and use that result as the expected value.

Also added some generally useful utils, and rewrote the test using those
utils to make the test more understandable.

R=futhark@chromium.org

Bug: 641877
Change-Id: Ie1ceb334eefee6e76015447f24148638ad8c55a6
Reviewed-on: https://chromium-review.googlesource.com/c/1275893Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Anders Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598847}