GitLab

ShouldShowLocationBarForHTTPApp and ShouldShowLocationBarForHTTPSApp
are both flaky, with the former failing while the later crashes.

TBR=mguica@chromium.org

Bug: 815240, 815246
Change-Id: I8856047c78d503affea58a25ba6f708454642116
Reviewed-on: https://chromium-review.googlesource.com/934926Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538848}

This was unintentionally removed, and needs to be added back. In the
future, this might move to DataReductionProxyData.

Bug: 813948
Change-Id: Iee0b5c16fc99860a9682804d1948651b434ab7ea
Reviewed-on: https://chromium-review.googlesource.com/927749
Commit-Queue: Ryan Sturm <ryansturm@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538847}

For the mojo version of session storage, the 'cloning' of namespaces
has to to be called on the same mojo pipe as all session storage data
operations. This patch allows that to happen by letting the source
renderer mint the new namespace ID (and thus allowing it to call 'clone'
with that ID).

Bug: 716490
Change-Id: I7d1e20c7b1387e9caeab868217cf25c7a0119342
Reviewed-on: https://chromium-review.googlesource.com/910109
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538846}

|scrollable_viewport_size_| is cached on each
InputHandler::OnSwapCompositorFrame, but it is never used. This CL
simply removes it.

Change-Id: I3025b25cc45c5ea220870aa23d462f04964311b5
Reviewed-on: https://chromium-review.googlesource.com/933115Reviewed-by: Yi Xu <yiyix@chromium.org>
Reviewed-by: Jonathan Ross <jonross@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Commit-Queue: Shridhar Sundarraj <sundarrajs@google.com>
Cr-Commit-Position: refs/heads/master@{#538845}

Ideally we should be able to show the dialogs in a meta world when
in WebVR. For now, this patch makes sure that no dialog is opened
in WebVR. Moreover, the dialog will be dismissed.

BUG=none

Change-Id: I32e8d7aed84927f1057a4a13e42622d9eceeb301
Reviewed-on: https://chromium-review.googlesource.com/932442
Commit-Queue: Amirhossein Simjour <asimjour@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538844}

This reverts commit 21813050.

Reason for revert: Broke (at least) webrtc's deps roller and Mac bisectors

Original change's description:
> [test_env.py] Reland: Warm up vpython virtualenv cache on swarming task shards
> 
> This will prevent tests sensitive to cold vpython startup time from
> timing out.
> 
> Relands https://chromium-review.googlesource.com/c/chromium/src/+/917802 . We
> expect this to work because test shards now include a hermetic copy of
> cpython as well as vpython (which was the failure observed in
> crbug.com/812693).
> 
> R=​dpranke@chromium.org, kbr@chromium.org, tandrii@chromium.org
> 
> Bug: 804174,812693
> Change-Id: Ic38845f8af366d9af211bef64df135176ab9ee1d
> Reviewed-on: https://chromium-review.googlesource.com/933107
> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
> Reviewed-by: Dirk Pranke <dpranke@chromium.org>
> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#538652}

TBR=iannucci@chromium.org,dpranke@chromium.org,kbr@chromium.org,tandrii@chromium.org

Change-Id: Ia8f6a122db20332c67b2376a176b18c68ae9efd1
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 804174, 812693
Reviewed-on: https://chromium-review.googlesource.com/935028Reviewed-by: Charlie Andrews <charliea@chromium.org>
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538843}

This build flag is intended to be set by the "Build From Tarball" bot which does
an unbundled build.  This is necessary because some of the libraries that we
statically link (eg. harfbuzz) use features that are very new and not available
on all (or any) supported distros.

BUG=800977
R=thestig

Change-Id: Ie7d635effe148aae07a75b60221442b0c71f2a38
Reviewed-on: https://chromium-review.googlesource.com/933725Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538842}

https://skia.googlesource.com/skia.git/+log/413782e8540d..09f818d2c9c0

$ git log 413782e85..09f818d2c --date=short --no-merges --format='%ad %ae %s'
2018-02-22 halcanary SkString: use c++11 vsnprintf in windows
2018-02-22 halcanary SkQP:  do test filtering correctly
2018-02-23 skcms-skia-autoroll Roll skia/third_party/externals/skcms/ c5472f44e..569770ec9 (1 commit)

Created with:
  roll-dep src/third_party/skia


The AutoRoll server is located here: https://autoroll.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=master.tryserver.blink:linux_trusty_blink_rel;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
TBR=djsollen@chromium.org

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

Since there is a race between /proc/self/tasks being updated and the actual
state of the process's threads, call AssertSingleThreaded rather than
LOG(FATAL) when InitializeSandbox detects that the process is not
multithreaded to allow a chance for /proc to be updated before the
process is killed.

BUG=b:73166395

Change-Id: I57d662fc9e1f2fd29a0d0ab9e1147ea00ee05568
Reviewed-on: https://chromium-review.googlesource.com/920002
Commit-Queue: Drew Davenport <ddavenport@chromium.org>
Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538840}

which records the location where a QUIC internal error was generated.

This is temporary change in order to track down the cause of an increase
in INTERNAL_ERROR and should be revered once that cause is determined.

Change-Id: I42e9b584894bdc8fb38fea21cdbd0699ce4d1a58
Reviewed-on: https://chromium-review.googlesource.com/931996Reviewed-by: Mark Pearson <mpearson@chromium.org>
Reviewed-by: Zhongyi Shi <zhongyi@chromium.org>
Commit-Queue: Ryan Hamilton <rch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538839}

Add an observer interface to ArcPolicyBridge. Observers are notified
whenever policy is sent to CloudDPC or a compliance report is
received from it.

The CL also forces a compliance report to be sent after the initial
policy fetch by adding a GUID to the policy JSON which changes
whenever a new instances of ArcPolicyBridge is created. A cleaner
way to do this would be a |force_compliance_report| flag sent to
CloudDPC. This clean-up is tracked in a follow-up bug.

Bug: b/73277923
Bug: b/73762796
Test: unit_tests
Change-Id: Ib4cdfb28e4b3ea2ea0ca03d1cd7293d7e07f0bcd
Reviewed-on: https://chromium-review.googlesource.com/931705
Commit-Queue: Bartosz Fabianowski <bartfab@chromium.org>
Reviewed-by: Pavol Marko <pmarko@chromium.org>
Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538838}

Bug: 805635
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I151911fab9a5e9e53531f52453b6c481fe901eaa
Reviewed-on: https://chromium-review.googlesource.com/934586Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538837}

This way, we don't need to build blink for both target and host,
and snapshots don't work in cross builds yet anyways (crbug.com/803591).
Once they do, we can reconsider.

Bug: 495204
Change-Id: Ie20c7eff44acea3cad5697cfa61f52d3f7405ac1
Reviewed-on: https://chromium-review.googlesource.com/934685
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538836}

views::View that don't have a context menu controller
still mark the click event as handled,
forbidding further processing of this event.

Bug: 814666
Change-Id: Ie9ab6e0f0e573a4d653a52995421ac1075c686fb
Reviewed-on: https://chromium-review.googlesource.com/925269Reviewed-by: Elliot Glaysher <erg@chromium.org>
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538835}

In future, Chrome renderer will generate paint items
and send them to viz process. The RasterService in viz
will turn those paint items into SkDDL in raster threads,
and then post a task to Gpu thread to draw SkDDL. This
new SkiaRenderer can be used to test the SkDDL related
code.

This CL also removes GLRenderer and SurfacelessGLRenderer,
because we would like use Skia instead of using GL directly
in future.

Bug: None
Change-Id: I6c4f5fa73550e7958b0ef25ec5ac88421251fcfb
Reviewed-on: https://chromium-review.googlesource.com/929314Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538834}

Per https://github.com/w3c/web-platform-tests/pull/4832 remove
WebSQL cases from WPT's workers/data-url*.html since it's not
otherwise tested in WPT, and the test "passes" even if the API is
not present. Also add an addition assertion that indexedDB is
present before blithely checking that using it throws.

WebSQL is not exposed to Workers in Chrome so we don't lose
coverage here - we only "passed" because the API was not present
in these contexts. The webexposed/ tests cover this.

Change-Id: I0aa05ff9e674351a2a49ba0bae8e5a9938b2cf34
Reviewed-on: https://chromium-review.googlesource.com/929602Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Commit-Queue: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538833}

Since "ViewsBrowserWindows" is a Chrome feature, this CL follows
CreateNativeWebModalManager in declaring a function in components
and defining it in c/b/ui/cocoa.

Background:
Polychrome is an intermediate step to shipping MacViews browser.
Currently, switching between Cocoa browser and MacViews browser requires
a buildflag. Polychrome builds both Cocoa and MacViews into the same
binary and allows switching between them based on a feature flag.
More details at crbug.com/802257

As Cocoa and (much of) Views were not typically built together,
some symbols were reused. With Polychrome, these are duplicate symbols.
This CL resolves the issue by renaming the Cocoa symbols, and then
shimming them for the (regular, not Polychrome) Cocoa build.

Bug: 808017
Change-Id: I9bf1845aa22305928aafd74884793f0fa86afe56
Reviewed-on: https://chromium-review.googlesource.com/929942Reviewed-by: Mike Wittman <wittman@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Leonard Grey <lgrey@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538832}

Bug: 738611
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Id88cb1a89d7eed7e2993dbf5f690708b61cc4143
Reviewed-on: https://chromium-review.googlesource.com/932978Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538831}

Storage back-ends notify the quota system about deltas in per-origin
usage via a QuotaManagerProxy, which will do sequence-hopping to get
to the right place to talk to the QuotaManager itself.

Convert the entry points to pass url::Origin instances along instead
of GURLs. For back-ends that are already converted to use url::Origin
internally (Cache API, Indexed DB) this deletes code. For the others
(AppCache, WebSQL, FileSystem), some conversions are necessary, mostly
in test logic.

(The QuotaManager itself is not yet updated, so the proxy itself
needs to do a type conversion. That'll get tidied up soon.)

Bug: 598424
Change-Id: I7e9eb04e974053ee6cc9172ee039aaa7cdec3d89
Reviewed-on: https://chromium-review.googlesource.com/927794Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Commit-Queue: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538830}

This patch fixes the local point when hit test ends up in text fragments:

When HitTestResult's inner node is a text node, the local point should be
local to the container block flow, not the text fragment being hit-tested.
We current have the latter, which is fixed in this patch.

Bug: 811502
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_layout_ng;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I3104c126b5ee3968f25dffa15042a45a051be160
Reviewed-on: https://chromium-review.googlesource.com/915041Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538829}

It's only needed for win/cross builds, but it's a small package and the
only additional package needed for cross builds, so add it unconditionally.

Change a/chrome/tools/build/win/create_installer_archive.py to use
7zr instead of 7za (both suffice for us), so that the smaller p7zip is enough.

Bug: 495204
Change-Id: I5f4c5326dbab2f3a3257c8cad4d3524cb338fca6
Reviewed-on: https://chromium-review.googlesource.com/934686Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538828}

This works, as of https://boringssl-review.googlesource.com/c/boringssl/+/26164

Bug: 124610
Change-Id: I2503743fa950764facfbf7795d9b20811fe6bb2a
Reviewed-on: https://chromium-review.googlesource.com/923537Reviewed-by: Steven Valdez <svaldez@chromium.org>
Commit-Queue: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538827}

The LayerTreeHosts will never create resources using a
VulkanContextProvider directly, instead will go through
the RasterInterface, so remove that option. Until that is
ready, we can use a software LTFS for --enable-vulkan mode.

Bug: None
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: Ibaa522062f2282f35e03c44b4255bb4504aba5b4
Reviewed-on: https://chromium-review.googlesource.com/930034Reviewed-by: danakj <danakj@chromium.org>
Commit-Queue: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538826}

https://boringssl.googlesource.com/boringssl/+log/085955c56744a9cc82f98ed850deca2165252d2c..672f6fc2486745d0cabc3aaeb4e0a3cd13b37b12

BUG=none

Change-Id: I44a792ba4d7341f2d2eb912787d7cef0b2e711e1
Reviewed-on: https://chromium-review.googlesource.com/933161
Commit-Queue: Steven Valdez <svaldez@chromium.org>
Reviewed-by: Steven Valdez <svaldez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538825}

Bug: 813184
Change-Id: I0e3dc1d458b96ebcb31506a38cdac177e2f9a859
Reviewed-on: https://chromium-review.googlesource.com/924397
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Reviewed-by: Martin Šrámek <msramek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538824}

Per https://w3c.github.io/webauthn/#dictdef-publickeycredentialcreationoptions

Change-Id: I78783bf1722d727e7014893e5f98e8e77c313b39
Reviewed-on: https://chromium-review.googlesource.com/933372Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Commit-Queue: Kim Paulhamus <kpaulhamus@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538823}

Instead, make a SyncToken when generating the gpu::Mailbox for each
(new) resource. If a resource is reused from the ResourcePool, then
no SyncToken will be be generated. Previously we always called
OrderingBarrier and inserted a SyncToken each time we prepared tiles
for raster, even if the resources were reused.

R=sunnyps@chromium.org

Bug: 730660
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: I4bdf5ab00f82fe8a9eed56f5cabc6628c1dffc22
Reviewed-on: https://chromium-review.googlesource.com/909070Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
Commit-Queue: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538822}

This adds a class that lives from login until logout. It observes the
pref that indicates whether to log events for app push-installs:
* If logging is enabled, an app push-install event log manager
  is created that handles collection, storage and upload of app
  push-install event logs.
* If logging is disabled, the manager is destroyed and any data related
  to the app-install event log is cleared from disk.

Dynamic pref changes are supported.

Bug: b/73277923
Test: unit_tests
Change-Id: I851f75224ed6f96364a88109ffece1e05d30069e
Reviewed-on: https://chromium-review.googlesource.com/929322
Commit-Queue: Bartosz Fabianowski <bartfab@chromium.org>
Reviewed-by: Pavol Marko <pmarko@chromium.org>
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538821}

https://webrtc.googlesource.com/src.git/+log/d60d5c4479d2..f35c6667d6f7

$ git log d60d5c447..f35c6667d --date=short --no-merges --format='%ad %ae %s'

Created with:
  roll-dep src/third_party/webrtc


The AutoRoll server is located here: https://webrtc-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=master.tryserver.chromium.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng;master.tryserver.chromium.win:win-msvc-dbg
TBR=webrtc-chromium-sheriffs-robots@google.com

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

This CL adds a new class ScrollingCoordinatorContext which contains
state that used to belong to ScrollingCoordinator but needs to be
duplicated for each local frame root when OOPIFs are instantiated. It
is lazily created on LocalFrameViews that are belong to local roots
(i.e. OOPIFs or main frames).

This also moves layers_with_touch_rects_ out of ScrollingCoordinator,
because reuse of that HashSet between frame roots was causing the crash
in bug 812364.

Bug: 680606, 812364
Change-Id: I09feb2add534b460dd9425fb918a6c856e325efb
Reviewed-on: https://chromium-review.googlesource.com/922702Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: Ken Buchanan <kenrb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538819}

Chrome has a "should remain available" disk space threshold; when less
than this amount is free, the effective quota for each origin drops to
0 so new writes will fail. This is present to avoid Chrome being
responsible for filling the disk which generally makes devices unhappy.

The threshold was set at 10%, which is too conservative; offline
storage would basically stop working when a disk was 90% full, which
is a common case - e.g. on a 200GB disk, writes start to fail with
20GB free! This change adjusts the threshold to 1%; for example, on a
32GB device this ensures Chrome does not push usage past 320MB
remaining free.

Similarly, Chrome has a "must remain available" threshold at which
point data starts being evicted - keeping the device functional, but
potentially losing user data. This was set at 1%, but is similarly
adjusted down to 0.25%. For a 32GB device this ensures Chrome will
drop data only when less than 80MB are free.

Bug: 802027
Change-Id: I09ec3531ef34637413a1d239b546dc200d3d648a
Reviewed-on: https://chromium-review.googlesource.com/933365
Commit-Queue: Joshua Bell <jsbell@chromium.org>
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538818}

This reverts commit 97218f98.

Reason for revert: This appears to be quite flaky on the Mac test bots.

Flakiness dashboard for this test (failures start with this commit)
https://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=PowerMonitorTest.TestGpuProcess&testType=content_browsertests



Original change's description:
> NetworkService: fix PowerMonitorTests
> 
> PowerMonitorTests were not expecting the utility service to be started
> during initialization, and could fail due to no closure being set by the
> test. We now don't attempt to bind the PowerMonitor unless the test has
> asked for it beforehand.
> 
> Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
> Change-Id: I15071d2a55dbc251240835c1046b095e6b22e0c4
> Reviewed-on: https://chromium-review.googlesource.com/931468
> Reviewed-by: John Abd-El-Malek <jam@chromium.org>
> Commit-Queue: Camille Lamy <clamy@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#538772}

TBR=jam@chromium.org,clamy@chromium.org

Change-Id: I27715f6f11388034ca501146aa0414da79b7413d
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Reviewed-on: https://chromium-review.googlesource.com/934861Reviewed-by: Ian Clelland <iclelland@chromium.org>
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538817}

The enterprise admin will be able to configure the display_mode
(standalone/fullscreen/minimal-ui) with which the enterprise WebAPK is
launched. The enterprise server will generate a WebAPK with the
requested display mode in the org.chromium.webapk.shell_apk.displayMode
<meta-data> tag.
The WebAPK server will no longer populate the
org.chromium.webapk.shell_apk.disableFullScreenMode <meta-data> tag.

BUG=None

Change-Id: I49c0f4965d54ea76572e34fc54d78db5e82edb50
Reviewed-on: https://chromium-review.googlesource.com/934633Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538816}

BUG=none
TEST=existing tests

Change-Id: I65793a97dd3a3798014a39756441094fb4d4d4a7
Reviewed-on: https://chromium-review.googlesource.com/931624Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538815}

This class ties together collection, storage and upload of app
push-install event logs. It creates an |AppInstallEventLogger|
that generates log entries, collects the entries, schedules their
upload to the server and their storage on disk.

All operations related to the log file happen on a background task
runner.

This CL also adds the |AppInstallEventLogger| which, however, for
now does not generate any log entries yet.

Bug: b/73277923
Test: unit_tests
Change-Id: I3eb421111339b1566aa6c7f5d8897af6e16fe090
Reviewed-on: https://chromium-review.googlesource.com/929502Reviewed-by: Pavol Marko <pmarko@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538814}

The first few frames received after entering VR could still contain the
browser-compositor-drawn omnibox texture, so we have to wait until we get a
frame without that (using the content offset as a proxy to know when the
omnibox is gone).

Bug: 807647
Change-Id: Ib9119aacaefe653c09c80da553305e79d14a2413
Reviewed-on: https://chromium-review.googlesource.com/934404Reviewed-by: Yash Malik <ymalik@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538813}

The previous calculation used platform, process counters, which includes
anonymous, faulted, shared memory. Since we now explicitly track all shared
memory regions, we discount by anonymous, resident, shared memory. This
introduces a slight source of error [difference between resident vs faulted],
but the error should be lower than previous.

Measured locally, this change will cause PrivateMemoryFootprint to be lower by
0-8MB for most processes, up to 30MB [rarely] for the browser.

Change-Id: I8b562fc185d215debbcfde60a3ad5c35302271b9
Bug: 812346
Reviewed-on: https://chromium-review.googlesource.com/924541
Commit-Queue: Erik Chen <erikchen@chromium.org>
Reviewed-by: Primiano Tucci <primiano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538812}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/c891f13e..a5154855

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;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;master.tryserver.chromium.android:android_optional_gpu_tests_rel

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

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

https://skia.googlesource.com/skia.git/+log/37c0f7183ebc..413782e8540d

$ git log 37c0f7183..413782e85 --date=short --no-merges --format='%ad %ae %s'
2018-02-23 angle-skia-autoroll Roll skia/third_party/externals/angle2/ f7f0b8c3a..e41df6556 (1 commit)

Created with:
  roll-dep src/third_party/skia


The AutoRoll server is located here: https://autoroll.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=master.tryserver.blink:linux_trusty_blink_rel;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
TBR=djsollen@chromium.org

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

It suggested some renaming that I'm not sure is a good idea anymore.

TBR=stevenjb@chromium.org

Bug: none
Change-Id: Icceb6281b3962f7d99b6370ed37a3a51efebf615
Reviewed-on: https://chromium-review.googlesource.com/934637Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538809}