GitLab

Bug: 773295
Change-Id: I37fd708a0224d82a460204e9b8f5617c34200e0a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1657387
Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org>
Auto-Submit: Takashi Toyoshima <toyoshim@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669168}

This cl is part of the effort to use CoreAccountId instead of std::string
to denote account_id.

Bug: 959157
Change-Id: I6f43a0ba28f7eefaa954482ccad638c3fe4c46e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1655450Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Commit-Queue: Tanmoy Mollik <triploblastic@google.com>
Cr-Commit-Position: refs/heads/master@{#669167}

Bug: 919926

Change-Id: I3e701d52889fc87e9d2ca734d1091f9092633e29
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1655434Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Mohamed Amir Yosef <mamir@chromium.org>
Commit-Queue: Pauline Leitao <psivieroleitao@google.com>
Cr-Commit-Position: refs/heads/master@{#669166}

This reverts commit b47670a1.

Reason for revert: Caused content_browsertests failure.
https://ci.chromium.org/p/chromium/builders/ci/Mac10.12%20Tests/23929

Original change's description:
> Migrate aec_dump_messages.h to Mojo
> 
> A nice side-effect of this change is that it moves complexity out of
> RenderProcessHostImpl.
> 
> Bug: 967834
> Change-Id: I39e93344e1db84668ef11b535447160ee3ab54cd
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1654238
> Reviewed-by: Tom Sepez <tsepez@chromium.org>
> Reviewed-by: John Abd-El-Malek <jam@chromium.org>
> Commit-Queue: Darin Fisher <darin@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#668864}

TBR=jam@chromium.org,darin@chromium.org,tsepez@chromium.org

Change-Id: I07567f80a6596510cb0bcf123e37d87158406647
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 967834
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1660492Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669165}

This reverts commit 04d43cf5.

Reason for revert: This is culprit of https://ci.chromium.org/p/chromium/builders/try/android-kitkat-arm-rel?limit=200

Original change's description:
> [WebSocket] Add --websocket-renderer-receive-quota-max command line flag.
> 
> This patch adds the flag that overrides default threshold value
> that the renderer calls AddReceiveFlowControlQuota() to the browser per
> receiving this amount of data so that the browser can continue sending
> remaining data to the renderer.
> Default value is 32k Bytes.
> 
> The more the value is, browser tends the less stop sending packets
> and then consumes more memory.
> 
> This flag will be used to investigate the performance issue.
> You can use this flag both on chrome and content_shell:
> $ ./chrome.exe --websocket-renderer-receive-quota-max=3000000
> This flag sets the threshold 3M Bytes.
> 
> Implementation detail:
> This patch moves the default value constant from blink to
> net/websockets/websocket_channel.h so that we can pass the command line
> flag to the renderer.
> This change also enables us to modify the value while considering sent buffer
> from a server later on for further optimization.
> 
> Bug: 865001
> Change-Id: Ib0f9638ece24fbc0523b94345d09a4382e9cf6a1
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1642850
> Commit-Queue: Yoichi Osato <yoichio@chromium.org>
> Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
> Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
> Reviewed-by: Adam Rice <ricea@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#669123}

TBR=kinuko@chromium.org,ricea@chromium.org,yhirano@chromium.org,yoichio@chromium.org,karandeepb@chromium.org

Change-Id: Ie05433698213a42e86d27c94d1d995f93ff8c549
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 865001
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1660391Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
Commit-Queue: Takuto Ikuta <tikuta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669164}

This CL moves the handler method for window.history.willChangeState
message from CRWWebController into CRWJSNavigationHandler.

Bug: 956511
Change-Id: I2d07091e42f8efd469566bac46b23fac0b3cf153
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1657838
Commit-Queue: Yi Su <mrsuyi@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669163}

The common code will be used by LoginScreenUiHandler browser tests [1].


[1] https://chromium-review.googlesource.com/c/chromium/src/+/1640406

Change-Id: Id3210f957af716037005c7ec973ecede376f4867
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1645365Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Reviewed-by: Alexander Hendrich <hendrich@chromium.org>
Commit-Queue: Jit Yao Yap <jityao@google.com>
Cr-Commit-Position: refs/heads/master@{#669162}

TBR=ericale@google.com,edchin@chromium.org

Bug: 974152
Change-Id: Id9859696f03db670ec291f71bbaf7531c55191db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1660488
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669161}

The previous comment contained an obsolete TODO (which was resolved),
and missed some details

Bug: none
Change-Id: I217f74abd75504b32f80180c90121e3464182255
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1658016
Commit-Queue: Marc Treib <treib@chromium.org>
Auto-Submit: Marc Treib <treib@chromium.org>
Reviewed-by: Jan Krcal <jkrcal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669160}

Calling Close on a NotificationDelegate after its associated notification has
been closed can cause a Chrome crash.

Bug: None
Change-Id: I402f474e70a54e7eabe6d82c5a396011e836c8e1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1659558Reviewed-by: Fergus Dall <sidereal@google.com>
Commit-Queue: Nicholas Verne <nverne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669159}

MessageLoop will go away, eventually.

ScopedTaskEnvironment will per default start a ThreadPool, which should
be fine in most of the cases. If you belive your test needs to make sure
that no ThreadPool runs let me know and I will update the patch.

BUG=891670
This CL was uploaded by git cl split.

R=weili@chromium.org

Change-Id: Ic0c89215f9b24d23f1b3607850791a157b09bbad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1649541
Auto-Submit: Carlos Caballero <carlscab@google.com>
Reviewed-by: Wei Li <weili@chromium.org>
Commit-Queue: Carlos Caballero <carlscab@google.com>
Cr-Commit-Position: refs/heads/master@{#669158}

This CL creates CRWJSNavigationHandler, and moves "window.hashchange"
handling from CRWWebController into this new class.

Bug: 956511
Change-Id: I84d756a80b3b34773fcd4bc02c9ba3da6d1398db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1649683
Commit-Queue: Yi Su <mrsuyi@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669157}

It seems clang-cl generates an extra 'brk #1' targeting arm64 on Windows.
It needs to extend the unit test to check this instruction as well.

Bug: 973794
Change-Id: Ice77e08609de7e5a7c1e76bb87d36698a4eb4e34
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1658017Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669156}

This fixes a messy looking update while the CustomTabBar is animating
out, and has the added benefit of preventing extra work.

Bug: 959738
Change-Id: I5a930ac3b4d0c754e6e20b15a91d71b260345846
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1659660
Commit-Queue: Jay Harris <harrisjay@chromium.org>
Reviewed-by: Alan Cutter <alancutter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669155}

A rendering of this doc (CSS styles may differ) is available internally
here:

https://g3doc.corp.google.com/experimental/users/olsen/g3doc/writing_js_unit_test.md?cl=240342366

Change-Id: I35ee7a81283b9adf7af3f20d20c2e91ecd80b71a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1655529
Commit-Queue: A Olsen <olsen@chromium.org>
Reviewed-by: Lutz Justen <ljusten@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669154}

Now that pseudo-USS is fully launched and the old DataTypeController is
gone, this code path isn't needed anymore.

Some tests (ExtensionSettingsApiTest) needed fairly straightforward
updates to do things on the correct thread.

Bug: 933874
Change-Id: I6416f02a2796eed791f64773113c7a099251518b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1655477Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Auto-Submit: Marc Treib <treib@chromium.org>
Commit-Queue: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669153}

Port BookmarkAppHelper browser tests to new unified install
system.

bookmark_app_helper_browsertests.cc will be erased soon.

TBR=dominickn@chromium.org

Bug: 915043
Change-Id: I6436bea69aa58e23eb7c999fd73c615aa459cf2a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1660372Reviewed-by: Alexey Baskakov <loyso@chromium.org>
Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Commit-Queue: Alexey Baskakov <loyso@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669152}

This adds basic device status reporting for registered Crostini
Apps (name, package name, version, last launched window). Reports
are only sent for managed devices, if enabled by policy. The
additional reporting is also hidden behind a feature flag which
is currently disabled by default.

Bug: 844468
Test: browser_tests --gtest_filter="DeviceStatusCollectorTest.*"
Change-Id: I56dc5e112cff0fd9a46aec86d499c9442d74558c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1640641Reviewed-by: Denis Kuznetsov <antrim@chromium.org>
Reviewed-by: Timothy Loh <timloh@chromium.org>
Commit-Queue: Alex Oldemeier <aoldemeier@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669151}

This reverts commit d9a56afc.

Reason for revert:

Findit (https://goo.gl/kROfz5) identified CL at revision 669086 as the
culprit for flakes in the build cycles as shown on:
https://analysis.chromium.org/p/chromium/flake-portal/analysis/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyQwsSDEZsYWtlQ3VscHJpdCIxY2hyb21pdW0vZDlhNTZhZmNiZGY5ODUwYmMzOWJiM2VkYjU2ZDA3ZDExYTFlYjJiMgw

Sample Failed Build: https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-rel/25818

Sample Failed Step: content_browsertests on Ubuntu-16.04

Sample Flaky Test: ScrollLatencyScrollbarBrowserTest.ScrollbarThumbDragLatency

Original change's description:
> Add explicit flag for compositor scrollbar injected gestures
> 
> The original change to enable scrollbar latency for the composited
> scrollbars incorrectly used an existing member to try and determine
> whether a GestureScrollUpdate was the first one in an injected sequence
> or not. is_first_gesture_scroll_update_ was incorrect because it is only
> updated when input is actually dispatched to InputHandlerProxy, and the
> flag is cleared for all GSUs before the location where it was being
> read.
> 
> This bug was missed because of incorrect tests. The
> VerifyRecordedSamplesForHistogram method doesn't actually assert or
> expect anything - the return value must be inspected.
> 
> As part of fixing up the tests, I made a few other changes to get them
> passing consistently across all platforms:
> - turn on main thread scrollbar injection feature (in case it's ever
>   turned off we don't want the tests to start failing)
> - enable mock scrollbars
> - disable smooth scrolling
> - don't run scrollbar tests on Android
> 
> The composited scrollbar button test is disabled due to a bug in how
> the mock theme reports its button sizes, which throws off the region
> detection in ScrollbarLayerImplBase::IdentifyScrollbarPart (filed
> crbug.com/974063 for this issue).
> 
> Change-Id: Ie1a762a5f6ecc264d22f0256db68f141fc76b950
> 
> Bug: 954007
> Change-Id: Ib258e08e083e79da90ba2e4e4216e4879cf00cf7
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1652741
> Commit-Queue: Daniel Libby <dlibby@microsoft.com>
> Reviewed-by: David Bokan <bokan@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#669086}


Change-Id: Icc743e48fa740fe27f0cb0cfa21b209a696f518c
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 954007
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1660114
Cr-Commit-Position: refs/heads/master@{#669150}

Bug: 950159
Change-Id: I587995f70d0f4cad06fde64ce91612fbe57b854a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1658009Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Commit-Queue: Colin Blundell <blundell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669149}

Bots are added in
https://chrome-internal-review.googlesource.com/c/infradata/config/+/1387672

Let me change dimension for test on swarming separately until
crbug.com/973024 is fixed.

TBR=jbudorick

Bug: 954450
Change-Id: Id32b5c808ce169d98fdd72603f194055270b1255
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1659567Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
Commit-Queue: Takuto Ikuta <tikuta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669148}

Style the ends of the progress stroke to 'round' to match the
design spec (before they were square).

Also, setting the text count indicator in the centre of the progress
indicator needs to be forced to string to display correctly.

Bug: 947388
Change-Id: Id594f74fc4f8f245845b115cb4f1824e0bb44c0d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1657377Reviewed-by: Noel Gordon <noel@chromium.org>
Commit-Queue: Alex Danilo <adanilo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669147}

TBR=ellyjones

Bug: 937166
Change-Id: Ied71d51fcc84be401af0eced5b6559a62720f0dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1659563Reviewed-by: ccameron <ccameron@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669146}

The webcam_private api expects that |device_id| to be set as the corresponding
device path. This CL gets the device path from vendor tag. The platform side CL
is I37c16ff94b1c6a282e7355839ad0e381a5fdd1fb.

Bug: b:134918107, b:134551601, b:117816888
Test: Passes capture_unittests and use chrome.webcamPrivate to set zoom
  level in camera app with Huddly Go.

Change-Id: Ia99cc84a8ca4a53ba7091eb5f80bf1f1ffc5c806
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1654743
Commit-Queue: Shik Chen <shik@chromium.org>
Auto-Submit: Shik Chen <shik@chromium.org>
Reviewed-by: Wei Lee <wtlee@chromium.org>
Reviewed-by: Ricky Liang <jcliang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669145}

TBR=eae@chromium.org
NOTRY=true

Change-Id: Ifb24d6d1c01c34640eb13ab5c4d69f1065a0cf29
Bug: 970200, 974139
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1659565Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669144}

WPT to verify the behavior of getBoundingClientRect()
when called on a locked element/element within a locked subtree.

Bug: 882663
Change-Id: Ic4ab18846724cfd211edb44dd2224cc9188cdbc1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1624011
Commit-Queue: Rakina Zata Amni <rakina@chromium.org>
Reviewed-by: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669143}

When user clicks on a non client area, the content
area stops receiving events because base implementation
of the HasCapture method always returns false. This
confuses the capture client, and capture is never
reset.

Thus, to fix the problem, implement the method on
the X11WindowOzone level and provide up-to-date
information whether the window has explicit capture
or not.

Bug: 789065
Change-Id: I4445f4cceb7c801f0ab0cfe4df005e977ba36569
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1657829Reviewed-by: kylechar <kylechar@chromium.org>
Commit-Queue: Maksim Sisov <msisov@igalia.com>
Cr-Commit-Position: refs/heads/master@{#669142}

BUG=None

Change-Id: I283883c95246997c93d6f0b419a3c8662ad3af0f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1659550
Commit-Queue: Anand Mistry <amistry@chromium.org>
Reviewed-by: François Degros <fdegros@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669141}

The 'xf-panel-item' custom elements allows configuration of the
indicators and buttons by setting attributes on the element or
by changing properties on the JS object referencing it.

Our feedback panels have a number of standard types, e.g. a
progress panel, summary panel, activity complete panel, etc.

This CL adds a convenience method setPanelType() that sets
up the various panel types using a single argument that can
be used by host elements that embed 'xf-panel-item'.

Bug: 947388
Change-Id: I29199a2402f1f508a4c59891b60891dfccba9cb1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1657078Reviewed-by: Noel Gordon <noel@chromium.org>
Commit-Queue: Alex Danilo <adanilo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669140}

Following bot results are included.
21292 21294 21301 21304 21312 21323 21333 21335

0 lines were removed and 2 lines were deflaked by consecutive
results since 21252.

TBR=eae@chromium.org, mstensho@chromium.org
NOTRY=true

Bug: 591099
Change-Id: Ib5d00b6648e61af13afbe045bbe7fee801fa335b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1657526Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669139}

Without it running whole PerfettoIntegrationTest suite will end with a crash at
the second test, due to invalid task runner in PerfettoTracedProcess and
TracingConsumerTest will fail in LargeDataSize and PrivacyFilterConfigInJson tests due
to invalid data sources in PerfettoTracedProcess

Change-Id: I952afa3226d085916fae047158c1a62b0ac14c13
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1658472
Commit-Queue: Michal Pichlinski <mpichlinski@opera.com>
Reviewed-by: oysteine <oysteine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669138}

Currently we just leave linux package operation notifications hanging
around uncompleted if the vm is shutdown before the operation
finished. Change this to have them switch to the error state on VM
shutdown. We don't try to detect shutdowns that don't go though the UI.

Bug: 966334
Change-Id: Ibdfba27291cd3f4aa3780b5b10a549dd4ea91b17
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1659556Reviewed-by: Nicholas Verne <nverne@chromium.org>
Commit-Queue: Fergus Dall <sidereal@google.com>
Cr-Commit-Position: refs/heads/master@{#669137}

Previously we were creating a Browser window with an app_name that
didn't correspond to any apps. This resulted in a window with a white
title bar and no icon.

Bug: 959670
Change-Id: I0b7a36232d8a8017a6d5f26041af2da0825ca8e6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1652388
Commit-Queue: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Reviewed-by: Trent Apted <tapted@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669136}

Previously we immediately return before setting layout dirty if we
call acquire() when the element is already locked, keeping the layout
values and painted output with the old size until the layout is dirtied
by some other cause.

Bug: 966451
Change-Id: I20f5f3bd7613046039d8149b81360db9df362102
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635127
Commit-Queue: Rakina Zata Amni <rakina@chromium.org>
Reviewed-by: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669135}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/cdd2c3ad..608c4a9c

Please follow these instructions for assigning/CC'ing issues:
https://v8.dev/docs/triage-issues

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

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: I1811225bb50b8a0b92dfa696642b007fed847484
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1660188Reviewed-by: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#669134}

There are certain cases where we fail to layout certain nodes, for which
there is no NGOffsetMapping, and hence, we can't paint selection.
This patch stops marking such nodes for selection painting to work
around the crashes.

Note: This patch only works around the crash. We should eventually fix
the missing layout.

Bug: 973226
Change-Id: I3138b2aff9be16b6c13e85a2717c126dfe7cbeee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1657253
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Auto-Submit: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669133}

Bug: 836128
Change-Id: I5701003f6dacf61cfa93d4f0cc5a8e8b4e857470
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1659659Reviewed-by: calamity <calamity@chromium.org>
Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Commit-Queue: calamity <calamity@chromium.org>
Commit-Queue: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Auto-Submit: calamity <calamity@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669132}

The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-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:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast
TBR=cr-fuchsia+bot@chromium.org

Change-Id: Ifc0862a6e5329b000b851d2fbcc60389622eac09
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1660168Reviewed-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@{#669131}

This is fix for
https://chromium-review.googlesource.com/c/chromium/src/+/1654757

Bug: 956776
Change-Id: I700924f1962ce20110beb5e37ecb02ea3fa616ab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1659661Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
Commit-Queue: Takuto Ikuta <tikuta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669130}

This CL moves platform/wtf/allocator.{h.cc} to platform/wtf/allocator/
and ports other dependent files to refer to a new include path.

Bug: 950130
Change-Id: If4f4941083786606fe3312dd71c317453019bddc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1558550
Commit-Queue: Abhijeet Kandalkar <abhijeet@igalia.com>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669129}