GitLab

The Certificate verifier needed to explicitly distrust Cloudflare
certificates issued before April 2nd, 2014. Those certificates have now
all expired and special distrust is no longer needed.

Change-Id: I07d7bfea8496e61725cd5307a57dccf08c3b3536
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1552099
Commit-Queue: Adam Langley <agl@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Adam Langley <agl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647782}

Before this CL:
All transaction started in PasswordSyncBridge were always committed
even in case of failure which could result in some in consistent
DB state (e.g. data written without the metadata)

After this CL:
Transaction are rolled back in case of error, and committed only if
every steps is successful.

Bug: 902349
Change-Id: I301087dd596ae35b7af80549aad880a11377a535
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1552869
Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org>
Reviewed-by: Jan Wilken Dörrie <jdoerrie@chromium.org>
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647781}

They were originally separate because it wasn't clear the framebusting
intervention would ship. It has, and is no longer behind a flag, so
streamline the logic.

Change-Id: Ib771156193c7ab99e8c9f849723bd351ebbe1bae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1534917Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Nate Chapin <japhet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647780}

This avoids including web_contents_observer.h for consumers of the struct
that aren't WebContentsObserver.

Bug: 947806
Change-Id: Ide735ae9b78df2d2640ac6a54635428ab47b54da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1547057
Commit-Queue: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647779}

Code in blink/modules/foo/*.cc often use code in modules:modules
which in the build system is not an allowed include. This makes
it legal.

This has no visible impact since the build order is already ok
and gn check errors are disabled for blink, but long term we'd
like to enable gn check and this is a small step on that route.

Bug: 800764

Change-Id: I083ec02f5190b5ee17e0394e1f5add940d1f4172
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1552808
Commit-Queue: Kentaro Hara <haraken@chromium.org>
Auto-Submit: Daniel Bratell <bratell@opera.com>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647778}

Bug: 877147
Change-Id: Id718dc6ebd74a8db0925f085c6df305141ee87ab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1547936Reviewed-by: Kai Ninomiya <kainino@chromium.org>
Reviewed-by: Corentin Wallez <cwallez@chromium.org>
Commit-Queue: Austin Eng <enga@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647777}

Uses the collectionViewContentSize as the cell size for the shortcuts.
In order to do this, ShortcutsViewController now is a UICollectionVC.
To avoid issues with rotation, configureLayout: method now takes
targetSize: parameter that allows pre-calculating the insets when the
ShortcutsVC's view transitions to a new size.

Change-Id: I9a740289bb60c43e0b443217fb94798e0ac3bc92
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1552846
Commit-Queue: Stepan Khapugin <stkhapugin@chromium.org>
Reviewed-by: Robbie Gibson <rkgibson@google.com>
Cr-Commit-Position: refs/heads/master@{#647776}

Bug: skia:8937
Change-Id: I38688af3dfe3224541549860b1e1641a6722c0e0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1553161
Commit-Queue: Mike Reed <reed@google.com>
Commit-Queue: Florin Malita <fmalita@chromium.org>
Reviewed-by: Florin Malita <fmalita@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647775}

|prefs::kSearchSuggestEnabled| is added to the list
of synced prefs that are observed during settings opt-in.

Bug: 933647
Change-Id: Ia70c75e7dae921552c29afbe1bdb7d312decaf89
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1552873Reviewed-by: Jérôme Lebel <jlebel@chromium.org>
Commit-Queue: Thomas Tangl <tangltom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647774}

Consolidate display moving logic into ClientRoot's
OnWindowRemovingFromRootWindow and OnWindowAddedToRootWindow
and avoid sending bounds update in middle of display changing.

Bug: 949294
Change-Id: Iab728ea126f056cf4dcb680c2297da00aa100f26
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1552286Reviewed-by: Jun Mukai <mukai@chromium.org>
Commit-Queue: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647773}

to support Periodic Sync registrations.

Also updates GetSoonestWakeupDelta() to only consider one-shot Sync
registrations for the existing wake up task.
A follow-up CL will add a wake up task for Periodic Background Sync.

Bug: 925297, 948206
Change-Id: I616371da7d6d61b4893acf961043b925dc42195d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1524352
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647772}

After the cleanup work done to migrate away from net::CompletionCallback()
and use net::Completion{Once|Repeating}Callback instead, this file is not
needed anymore, so let's remove it to prevent accidental new usages of
those generic callbacks, and force using the new ones.

Bug: 807724
Change-Id: Ie47786e4e3da64481dde4bf91987844fa6dfcab4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1552821
Commit-Queue: Matt Menke <mmenke@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647771}

This CL teaches GLImageNativePixmap how to map BGRX_1010102 to
the DRM one, and adds it to the unit test case list.

 (needs  https://crrev.com/c/1552107).

Test: /tmp/ozone_gl_unittests --gtest_also_run_disabled_tests
Bug: 949260
Change-Id: Id499073d004e3b6319cb1131fbb5b80507683e6c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1552105Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Commit-Queue: Daniele Castagna <dcastagna@chromium.org>
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647770}

This reverts commit 4e001d88.

Reason for revert: Suspected of breaking 
DataReductionProxyFallbackBrowsertest.ProxyBlockedOnAuthError
DataReductionProxyFallbackBrowsertest.RedirectCycle
on  linux-chromeos-dbg

Bug:949577

Original change's description:
> Fix quic webdriver test
> 
> Net.QuicAlternativeProxy.* histogram is not recorded with servicification.
> So that check is removed in the test. The DataReductionProxy.Quic.ProxyStatus
> histogram used in the test should be sufficient.
> 
> Bug: 934875
> Change-Id: I1cdb16e347bd4cf852cc30481887a94dabceef8b
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1551710
> Commit-Queue: rajendrant <rajendrant@chromium.org>
> Reviewed-by: Robert Ogden <robertogden@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#647481}

TBR=robertogden@chromium.org,rajendrant@chromium.org

Change-Id: I5f8768916c18cc3a2cbf8634672ec49ebf42f9b3
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 934875
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1552878Reviewed-by: Christos Froussios <cfroussios@chromium.org>
Commit-Queue: Christos Froussios <cfroussios@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647769}

This CL enables the handling of WebUI pages by WKWebView by default.

Bug: 739844
Change-Id: I45853c60c7e598ecfdda4028e86547568bb7bd9f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1551663
Auto-Submit: Gauthier Ambard <gambard@chromium.org>
Commit-Queue: Eugene But <eugenebut@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647768}

The path-related methods in base::Value currently take either
a std::initializer_list<StringPiece> or a std::span<const StringPiece>
argument to specify the path of dictionary items, but this turns out
to generate larger code than necessary, and even force heap allocations
in the case of std::span<> (which is typically used to pass a
std::vector<std::string> as an argument).

This CL introduces new versions of these methods that take a single
StringPiece for the path parameter (using simple dots to delimit
path components).

In addition to this, type-specialized methods like FindStringPath()
or SetIntPath() are also provided to provide a more user-friendly
API, and in the case of Set<Type>Path(), more efficient as well.

The old methods are not removed yet but tagged deprecated and will
continue to function, until all callers have been updated to the
new ones.

BUG=646113
R=dcheng@chromium.org,jdoerrie@chromium.org,sdefresne@chromium.org,hidehiko@chromium.org

Change-Id: Ia28c604d5b2a017eb92508ab230fe9ea2288f3df
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1538292
Commit-Queue: David Turner <digit@chromium.org>
Reviewed-by: Jan Wilken Dörrie <jdoerrie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647767}

- A user is now allowed to bypass entering their old password when
updating their windows password if they forgot their old password.
- The user's password will be forcefully reset once they confirm
they wish to reset their password. This will cause them to lose
all their encrypted data.

Bug: 912609
Change-Id: I308a41d2ba278c0e15c6976fb41bb0ebcf9bd414
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1551465
Commit-Queue: Tien Mai <tienmai@chromium.org>
Reviewed-by: Roger Tawa <rogerta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647766}

This CL prepares CanAccessDataForOrigin (which can be called on the UI
or IO thread) to support citadel-style enforcement (which requires
calling DoesSiteRequireDedicatedProcess).  See https://crbug.com/764958
for more details.

Bug: 764958
Tbr: servolk@chromium.org (for mechanical //chromecast changes)
Change-Id: Iec64cbe3a42164c1993d2e41ee1ec18655160626
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546323
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647765}

https://android.googlesource.com/platform/external/perfetto.git/+log/b053961e125c..9c85e2560369


git log b053961e125c..9c85e2560369 --date=short --no-merges --format='%ad %ae %s'
2019-04-04 lalitm@google.com Merge "trace_processor: fix generation of proto names"
2019-04-04 treehugger-gerrit@google.com Merge "Do not start heapprofd in integrationtest."


Created with:
  gclient setdep -r src/third_party/perfetto@9c85e2560369

The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-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=perfetto-bugs@google.com

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

A previous update to AXPlatformNodeWin caused get_localizedExtendedRole
to return S_OK and empty strings when the role description was not
explicitly set. Consequently, the UA would report empty descriptions
instead of the implicit defaults. This had wide impact since as most
objects do not set their role descriptions.

This change ensures that the function returns S_FALSE when the role
description is not explicitly set. This tells the UA that it should use
the default description.

Bug: 947762
Change-Id: I124d2c61d5f6e3d9545bd350cabd674f7f5fe354
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1545685Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647763}

Bug: 948646, 949538
Change-Id: Ib439b1111be76febdd212e00e8895a65cc2b0387
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1553160Reviewed-by: Jonathan Backer <backer@chromium.org>
Commit-Queue: Michael Ludwig <michaelludwig@google.com>
Cr-Commit-Position: refs/heads/master@{#647762}

... to 454b6bcf7d08535681bbd967030f5248bcbc8e6a

This bumps the stack limit for JSON / CBOR to 300.

Change-Id: I6549765c1d9e23072c488dd4f7ec8437bd8d1a66
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1552648
Auto-Submit: Johannes Henkel <johannes@chromium.org>
Commit-Queue: Andrey Kosyakov <caseq@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647761}

Makes Frame a top-level class so that it can be reused in unwinding code
independent of building a profile.

Bug: 909957
Change-Id: I8864863b41f7846eca8efa220cec8476e4875a57
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1543809
Commit-Queue: Mike Wittman <wittman@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: oysteine <oysteine@chromium.org>
Reviewed-by: Leonard Grey <lgrey@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647760}

https://webrtc.googlesource.com/src.git/+log/6c371ca7005a..21f6fd79ad05


git log 6c371ca7005a..21f6fd79ad05 --date=short --no-merges --format='%ad %ae %s'
2019-04-04 jakobi@webrtc.org Add preemptive rate and preferred buffer size plots to event log visualizer.
2019-04-04 gustaf@webrtc.org AEC3: Remove unused config parameters


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

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.



BUG=chromium:None
TBR=webrtc-chromium-sheriffs-robots@google.com

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

Currently, after calling OverrideBinderForTesting, we completely drop
the existing registered interface binders. This CL modifies this
behavior, and lets us fall back to the pre-existing registered
binder for an inteface if it hasn't been explicitly overriden by
OverrideBinderForTesting.

Change-Id: I59673ac42f98615451be518bfd61dd0f8f6b3ad2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1543455Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Adithya Srinivasan <adithyas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647758}

A missing dependency made chromedriver builds flaky.

This was reported as a dependency error by
gn check --check-generated after enabling dependency checks
of chrome/test/* in .gn so having those dependency checks
enabled would have prevented this.

Bug: 949518
Change-Id: I3be5864d27e8258be193e67dc9f05f303b7c00fe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1552849
Auto-Submit: Daniel Bratell <bratell@opera.com>
Commit-Queue: John Chen <johnchen@chromium.org>
Reviewed-by: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647757}

Change-Id: Ia520380215f04c3686ad96b88a2db7f170b8852a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1552220
Commit-Queue: Jochen Eisinger <jochen@chromium.org>
Auto-Submit: Jochen Eisinger <jochen@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647756}

Suffix all GC calls for testing as such to illustrate this these methods should
never be called from production code.

Rename full GC to forced GC for testing.

Bug: 948807
Change-Id: I03e6139ee365b575e7634a4058419af9b0c90cc4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1549259
Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647755}

* Remove RetainWrapperDuringConstruction().
* Remove warnings about special GC semantics.
* Remove holder_ hack from transform_stream_test.cc.

Change-Id: Iaf5d5868679b33c1411fb944120c4711d8d00a44
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1547715Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Kentaro Hara <haraken@chromium.org>
Auto-Submit: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647754}

This is the 5th refactoring CL aimed at reducing duplication and
inconsistency for classifying omnibox results.

For classification, document suggestion contents and historyUrl
suggestion descriptions currently use
a) bookmarks::CleanUpTitleForMatching,
b) AutocompleteProvider::TermMatchesInString, and
c) HistoryProvider::SpansFromTermMatch.

Document suggestion descriptions (e.g. 'Google Drive') are not
classified, and historyUrl suggestion contents have unique
classification logic which this CL does not address.

This CL changes document suggestion contents and historyUrl suggestion
descriptions to use FindTermMatches and ClassifyTermMatches defined in
autocomplete_match_classification.cc instead. These methods were created
in the previous refactoring CL's and are based on the methods (a), (b),
and (c). But unlike the previous methods, these are located adjacently
in a single file and are more generic to allow reuse by ideally all
providers.

Additionally, this CL removes the
AutocompleteProvider::TermMatchesInString method as it's no longer used.

Migrating from the previous to the new classification methods has a few
behavior changes as well:

1) The document and historyUrl suggestions now check for prefixes
matching, where if the user text is an exact prefix of the suggestion
text, further occurrences of the user text are not styled. E.g., the
user text "the" will bold only the first occurrence in the suggest text
"[the] dog ate the moon".

2) The document and historyUrl suggestions do not restrict matches when
the user text contains symbols. Previously, the user text 'the-' would
match the suggest text '[the-]dog' but not the suggest text 'the dog'.
With this CL, symbols in the user text are disregarded unless prefix
matching, and 'the-' matches '[the] dog'.

Bug: 366623
Change-Id: I48a7d06e05f5c77551033bc085a263b57840cd57
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1552140Reviewed-by: Tommy Li <tommycli@chromium.org>
Commit-Queue: manuk hovanesian <manukh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647753}

OnForwardScrollUpdateToMainThreadOnImpl is used to record latency
components that aren't used downstream.

There is still some follow-on work to remove the unused latency
components definitions from LatencyInfo.

Change-Id: I7d54a3fcabecd63ddabfc4705924a3c37d2ad480
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1551063Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Commit-Queue: Tom McKee <tommckee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647752}

Fixes Cmd+C and Cmd+V in pre-edit. Adds a unit test to prevent
future regressions. Currently an EGTest is not possible, as EGTest
doesn't have actions for sending keyboard events.
Removes a DCHECK for OmniboxTextFieldIOS' delegate to be a more
specific subclass, which seems fine as all of the methods of
OTFIDelegate are optional


Bug: 945024
Change-Id: I216bc8361e01e9874623e2105416e2cfa9ff03aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1547747
Commit-Queue: Stepan Khapugin <stkhapugin@chromium.org>
Auto-Submit: Stepan Khapugin <stkhapugin@chromium.org>
Reviewed-by: Robbie Gibson <rkgibson@google.com>
Cr-Commit-Position: refs/heads/master@{#647751}

Change-Id: Ib825aec08f3d55d6e4c6cbf25ba63c5f36bb41c0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1552899
Auto-Submit: Taiju Tsuiki <tzik@chromium.org>
Commit-Queue: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647750}

The old JSON-RPC endpoint is still the default one, but we will
gradually transition users to the new REST endpoint, as the JSON-RPC
one is being deprecated.

The difference between the 2 endpoints is very small and are
highlighted in the following doc:
docs.google.com/document/d/1tmqz3QTF-lhbbkBxqOSYMdNZ-OOhlMIhb8hczhbZVhQ

Bug: 943108
Change-Id: I87a9fc8bbe9c4571528256d20d86748384caed61
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1542418
Commit-Queue: Guillaume Jenkins <gujen@google.com>
Auto-Submit: Guillaume Jenkins <gujen@google.com>
Reviewed-by: Nicolas Ouellet-Payeur <nicolaso@chromium.org>
Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Reviewed-by: anthonyvd <anthonyvd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647749}

BCKSF (BrowserContextKeyedServiceFactories) can depend on SKSFs
(SimpleKeyedServiceFactories), but adding the dependency to
DependencyManager cause issues as they are two separate graphs.

https://chromium-review.googlesource.com/c/chromium/src/+/1534708
allows these dependencies and makes them no-op using a workaround.

Bug: 944906
Change-Id: Iea4fa4655ff06a9903c92648a8f744878d7f7787
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1551933Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: Colin Blundell <blundell@chromium.org>
Commit-Queue: Henrique Nakashima <hnakashima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647748}

The problem is because the window size and swapchain's
size do not match during resizing, and then the
vkQueuePresentKHR() will fail. This CL create a child
window, and create a surface and swapchain from it.
During resizing, we will resize the child window and
re-create the swapchian at same time.

Bug: None
Change-Id: I160dd26d6de2a8f2b2a01d201d5a2c428c2f2139
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1548315Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647747}

https://skia.googlesource.com/skia.git/+log/98f4e81d49dc..a064c2812eb5


git log 98f4e81d49dc..a064c2812eb5 --date=short --no-merges --format='%ad %ae %s'
2019-04-04 kjlubick@google.com [canvaskit] Make SkImageShader from SkImage
2019-04-04 ethannicholas@google.com SkSL now properly errors when invocations are used outside of a geometry shader
2019-04-04 robertphillips@google.com Stop using pendingIO in read/writeSurfacePixels
2019-04-04 kjlubick@google.com [canvaskit] adding drawAtlas to canvas API


Created with:
  gclient setdep -r src/third_party/skia@a064c2812eb5

The AutoRoll server is located here: https://autoroll.skia.org/r/skia-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:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;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=jlavrova@chromium.org

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

This CL use R.color.sheet_bg_color for the background color of the
Chrome BottomSheet instead of R.color.modern_primary_color.

This should have no visible effect in the default/light theme. In the
dark theme, the background color will now be
modern_grey_900_with_white_alpha_6 (#2D2E31) instead of modern_grey_900
(#202124), to match with the payment request sheet background.

Change-Id: I936f4399d013445e38c215b9f3da52aadb5156c5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1552872Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Jordan Demeulenaere <jdemeulenaere@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647745}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/ddb565a9417c..98c9c09ca5ff


Created with:
  gclient setdep -r src-internal@98c9c09ca5ff

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.

CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome
TBR=fergal@chromium.org,alph@chromium.org,avi@chromium.org,cfroussios@chromium.org

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

This CL is removing the deprecated flag to disable DWrite rendering.
The renderers are only using DWrite. Chrome should not work without
DWrite.

The current CL is changing the GDI path to a CHECK.

Renderers removed GDI path:
  https://bugs.chromium.org/p/chromium/issues/detail?id=579678

R=robliao@chromium.org, asvitkine@chromium.org
CC=dfried@chromium.org

Bug: 944227
Change-Id: I466732d9f46c009834532461dc45f3136264b6a5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1551121
Commit-Queue: Etienne Bergeron <etienneb@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647743}