GitLab

Replaced the previous curly ones.

Change-Id: I46024a0dcd25cf56189edee18d7d1a62f943053f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871608Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Commit-Queue: Edward Jung (EMEA) <edwardjung@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710909}

These macros are used in all of 3 files. Instead of all this magic, maybe the components
that need this should define FOO_TEMPLATE_EXPORT_DECLARE and FOO_TEMPLATE_EXPORT_DEFINE
in their foo_export.h file instead, and make it expand to the right thing there.
That seems a lot simpler and easier to understand.

But for now, let's just add a comment.

Bug: none
Change-Id: I5fd56440a07a4c7ba879af6d809c7e1397d05737
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1890531
Auto-Submit: Nico Weber <thakis@chromium.org>
Reviewed-by: Reid Kleckner <rnk@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710908}

Change-Id: I0be89fe1fb55a352faeb05989fad1346155a0338
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1890419Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Commit-Queue: Carlos Caballero <carlscab@google.com>
Cr-Commit-Position: refs/heads/master@{#710907}

This change avoids a race condition in IndexedDBContextImpl's Shutdown
method. In that method, std::move is used on a variable on the UI,
where that variable is supposed to be only accesed or modified on the
IDB task runner.

Being a race condition, this is really hard to test, and I'm not sure
what I would do to test this. It is also not necessarily the fix for
the given bug.

Bug: 1018741
Change-Id: Ia071e5a053952af8c74aa30e0e5e218c4b97100f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1885498Reviewed-by: Chase Phillips <cmp@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710906}

The platform_window target is used from multiple components and should
therefore be a component itself. This is needed to avoid ODR violations.

One ODR problem that currently can happen is the duplication of the
global boolean backing UseTestConfigForPlatformWindows().

Bug: 1019015

Change-Id: I935df9a2fb2c6df1fec887c45c332bc833db91b9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1889293Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Michael Spang <spang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710905}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/76abb20f3770..3abb07fb77e6

git log 76abb20f3770..3abb07fb77e6 --date=short --no-merges --format='%ad %ae %s'
2019-10-30 seanabraham@chromium.org chromeos_config: make tatl and tael critical again

Created with:
  gclient setdep -r src/third_party/chromite@3abb07fb77e6

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/chromite-chromium-autoroll
Please CC chrome-os-gardeners@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel
TBR=chrome-os-gardeners@google.com

Bug: None
Change-Id: I899a94d99e0752b95bba65608d8406e393af3e60
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1890836Reviewed-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@{#710904}

Disable testPasswordIconIsNotVisibleWhenPasswordStoreEmpty because it is
failing in iOS 13.2

Bug: 1019535
Change-Id: Ib285e0019207a8463c52246d4864674c01f54522
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1891130Reviewed-by: Sergio Collazos <sczs@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710903}

This patch removes PlayStateUpdateScope from NotifyCompositorStartTime
and aligns the implementation of NotifyStartTime with the 'pending
play task' in the web-animations spec.

https://pinpoint-dot-chromeperf.appspot.com/job/11bd74d8220000

Bug: 960944
Change-Id: I5b296e7f67458e362470ef1f151e73f07bf60bff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1881123
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710902}

Plus some JavaScript scaffolding to avoid re-uncompressing the .size
file on every buildTree() invocation.

Bug: 1011921
Change-Id: I839fb8a8e0ea0b1509620b391a1dd3153a157e9a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1888371
Commit-Queue: Jasper Chapman-Black <jaspercb@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710901}

(1) Simplify clipboard_constants code by consistently specifying
constants in clipboard_constants (as opposed to clipboard_format_type).

(2) Add comments to explain the need for separation between
clipboard_constants and clipboard_constants_mac.

No intended functional changes.

Change-Id: I8c9520341c4d90f1a071c65d22b91e91eca5d410
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1886112Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Darwin Huang <huangdarwin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710900}

Using wpt-import in Chromium cd0f6a46.
With Chromium commits locally applied on WPT:
1d5b803f "Add WebVTT support for inline styling - Web Platform Tests"


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:
foolip@chromium.org, lpz@chromium.org, robertma@chromium.org:
  external/wpt/tools

NOAUTOREVERT=true
TBR=raphael.kubo.da.costa

No-Export: true
Change-Id: I974773d5cf4c8e083bfa81801d661704bafd2650
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1890791Reviewed-by: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#710899}

Fixed: 980716
Change-Id: Idcb779085be438c29af233cc805cfe73f7ebd42c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1877820
Commit-Queue: Jared Saul <jsaul@google.com>
Reviewed-by: Evan Stade <estade@chromium.org>
Reviewed-by: Siyu An <siyua@chromium.org>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710898}

This happens because the adapter and layer for the top controls is only
created once height and width are > 0. We were assuming this had already
been created in setTopControlsOffset().

Change-Id: Idf104f9d5c951c1fa8719fa30661dceae59b4887
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1890492
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710897}

Bug: 1018888
Change-Id: Ia548a163261b25f06222916498c7b8ea83fa03d7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1885211Reviewed-by: Ender <ender@google.com>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Gang Wu <gangwu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710896}

Introduce a new CustomViewBinder interface that allows
AppMenuPropertiesDelegates to handle binding for custom menu items.

This interface is used to provide a custom binder for the update menu
item, which relies on UpdateMenuItemHelper methods/classes that will not
be moved to the appmenu/ package when its modularized.

Bug: 966644
Change-Id: I6c49522775c1f0fca3cd64764a0eba6a5b82f3b1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872980Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: Theresa  <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710895}

Clicks on the toolbar are currently passed through the url_bar behind it.
This leads to unexpected behavior when not user-visible views handle click events.
The change makes the toolbar intercept all click events on not user-visible views.

Accessibility is unaffected, see here: https://drive.google.com/file/d/1LDGfFfaCkg2meUNPX3211HE2_bIJGJNr/view?usp=sharing

Bug: 982018
Change-Id: Ibadba84a8f500cb7cf7aaa5129c91b11f2a5e9e0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1887150Reviewed-by: Yusuf Ozuysal <yusufo@chromium.org>
Reviewed-by: Ganggui Tang <gogerald@chromium.org>
Commit-Queue: Mia Glaese <glamia@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710894}

This involved updating the test fixture to use a different
mechanism because the execution of the JS script bodies via
ChromeEarlGrey injection hangs because of JS execution halts
while the dialogs are displayed.  Instead, there is now a
tappable link on the page that executes the dialog scripts
with a timeout so that the script execution can return while
the dialog is displayed.

Bug: 987646
Change-Id: Ifa90d923360ca03c686d662a7cc34575dff94037
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1883137
Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Auto-Submit: Kurt Horimoto <kkhorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710893}

We were missing a WaitForFirstVisuallyNonEmptyPaint in the test but
actually we can simplify it quite a bit as there is no need to put the
page in the bfcache to exercise the code under test.

Bug: 1019664
Change-Id: I1b714d77a4a4002ba8b3eae08ea881bcaad4b93e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1890338Reviewed-by: Alexander Timin <altimin@chromium.org>
Commit-Queue: Carlos Caballero <carlscab@google.com>
Cr-Commit-Position: refs/heads/master@{#710892}

Change-Id: I0681b6feafe06b9434ea0df66ad0724f290aa17b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1886897
Commit-Queue: David Roger <droger@chromium.org>
Reviewed-by: Monica Basta <msalama@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710891}

set_sources_assignment_filter() is considered as a mis-feature
of gn (as it makes it difficult to reason about the BUILD.gn
files individually).

Convert BUILD.gn files below //base to instead use conditional
to include source files only on the platformn where they are
used.

The conversion was done by using a modified version of gn that
display all files filtered by set_sources_assignment_filter()
and updating the BUILD.gn files manually to explicitly add the
source files only on the platform that used them.

Bug: 1018739
Change-Id: I236542d7b8e2b5cba5b633b37791d1f1dbbe8d2a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1879458
Commit-Queue: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710890}

This reverts commit 5f5c6c4b.

Reason for revert: As Boris points out in https://bugs.chromium.org/p/chromium/issues/detail?id=789531#c56 , my original revert was mistaken, it wasn't the offending CL, but rather was fixing the issue. Relanding.

Original change's description:
> Revert "[Android][Signin] Fix bookmark signin promo dismiss tests"
> 
> This reverts commit 04962c50.
> 
> Reason for revert: Test failures, see https://ci.chromium.org/p/chromium/builders/ci/Lollipop%20Tablet%20Tester/14131
> 
> Original change's description:
> > [Android][Signin] Fix bookmark signin promo dismiss tests
> > 
> > This CL fixes the bookmark signin promo tests when the promo is
> > dismissed in different scenarios.
> > 
> > Bug: 789531
> > Change-Id: I852e60cb3e56f9db737cb0e03073d36373908f68
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1883628
> > Reviewed-by: Boris Sazonov <bsazonov@chromium.org>
> > Reviewed-by: Theresa  <twellington@chromium.org>
> > Commit-Queue: Alice Wang <aliceywang@chromium.org>
> > Auto-Submit: Alice Wang <aliceywang@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#710784}
> 
> TBR=twellington@chromium.org,bsazonov@chromium.org,aliceywang@chromium.org
> 
> Change-Id: I68d849103de344e495520b8c015edfba75fd6388
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 789531
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1890506
> Reviewed-by: Sky Malice <skym@chromium.org>
> Commit-Queue: Sky Malice <skym@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#710853}

TBR=twellington@chromium.org,skym@chromium.org,bsazonov@chromium.org,aliceywang@chromium.org

Change-Id: I43787dce3fd7d0004ef777b1724fec1935db0347
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 789531
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1891230Reviewed-by: Sky Malice <skym@chromium.org>
Commit-Queue: Sky Malice <skym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710889}

-Add a flag to cr-searchable-dropdown so we can track whether the user's
 current text input in the dropdown matches the previously saved value.
 We use this flag to disable the printer add button if the user typed
 invalid input into either the Manufacturer or Model dropdown.

Fixed: 950887
Change-Id: I1f632b80fd8619718f13f8a5f5332ad7a62eb69e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1880181
Commit-Queue: Gavin Williams <gavinwill@chromium.org>
Reviewed-by: Bailey Berro <baileyberro@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710888}

Bug: 932707
Change-Id: Ieb3cc5571e9e632cb451f317f87a59d912fd232a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1887718Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Commit-Queue: Michael Crouse <mcrouse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710887}

BUG=None
R=fdoray@chromium.org

Change-Id: Ic566ca8d92ddaca27b127099f9437d0e0a4d6e79
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1889973
Auto-Submit: Greg Thompson <grt@chromium.org>
Reviewed-by: François Doray <fdoray@chromium.org>
Commit-Queue: Greg Thompson <grt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710886}

This reverts commit b936d5f1.

Reason for revert: Flaky crashes on webgl bot; see bug.

Original change's description:
> css/resolver: Refactor weaknesss in MatchedPropertiesCache
> 
> MatchedPropertiesCache was the single user of custom weakness using
> HashTraits. Supporting custom weakness in hash tables is responsible for
> a lot of complications in the tracing protocol.
> 
> MatchedPropertiesCache was using weakness to hold alive a cached entry as long
> as all of its matched properties are alive. Once a single matched property dies
> the entry was removed.
> 
> This can be modeled using a custom weakness callback that performs the same
> logic. Cached entry don't have any outgoing edges except for their cached
> matched properties, so ephemeron semantic is not required. Using a custom weak
> callback is also faster because the callback is only executed once and not part
> of the ephemeron fixed point protocol. The cached entry is unlinked using the weak callback and collected on next GC cylce.
> 
> After this conversion, custom weakness can be removed from hash traits.
> Weakness should always go through already supported types (e.g.
> WeakMember).
> 
> Bug: 1019191
> Change-Id: I52b7b24dcba8a3aaca896f86a351da665667fcf9
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1886611
> Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
> Reviewed-by: Omer Katz <omerkatz@chromium.org>
> Reviewed-by: Kentaro Hara <haraken@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#710693}

TBR=haraken@chromium.org,mlippautz@chromium.org,omerkatz@chromium.org

Change-Id: I30c098eb560e7fa62c6f5bd354188fc2a3eb2ab2
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1019191
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1891190Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710885}

This change straightens out some of the convoluted logic in this method,
so that hopefully it is simpler and easier to understand.

Bug: None
Change-Id: I913e98c04c3f9f3a8c6727a25c6c0f4675695c77
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1877664
Commit-Queue: Lily Chen <chlily@chromium.org>
Reviewed-by: Maksim Orlovich <morlovich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710884}

We'd like to turn off sequence manager anti-starvation logic but we
need to change this first to ensure the expected ordering of
PostTask and content::BrowserThread::DeleteSoon.

The observable difference is BrowserThread::GetCurrentThreadIdentifier
now inherits base::TaskPriority where previously it did not which is
dangerous.

Bug: 1013535, 1019767
Change-Id: I88cf03635b37f680f10b5aefd582afae35474a45
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1886901Reviewed-by: Gabriel Charette <gab@chromium.org>
Commit-Queue: Alex Clarke <alexclarke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710883}

This reverts commit fb7771dc.

Reason for revert: Long filenames excluded.

Original change's description:
> Revert "[CompositeAfterPaint] Rebaseline tests"
> 
> This reverts commit 9dc83eeb.
> 
> Reason for revert: causes bot_update failure on Win x64 Builder (dbg).
> 
> Sample build: https://ci.chromium.org/p/chromium/builders/ci/Win%20x64%20Builder%20%28dbg%29/99428
> 
> ---
> error: unable to create file third_party/blink/web_tests/flag-specific/enable-blink-features=CompositeAfterPaint/virtual/controls-refresh/fast/forms/controls-new-ui/color-scheme-validation/color/color-suggestion-picker-appearance-with-scrollbar-expected.png: Filename too long
> ---
> 
> Original change's description:
> > [CompositeAfterPaint] Rebaseline tests
> > 
> > Most of these rebaselines are for the mock scrollbar change which missed
> > rebaselining for CAP.
> > 
> > The other rebaselines are for new tests added for
> > virtual/controls-refresh.
> > 
> > TBR=schenney@chromium.org
> > 
> > Change-Id: Ia710bd0bf371eae8367c1ee3739691985f314840
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1888572
> > Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
> > Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#710590}
> 
> TBR=wangxianzhu@chromium.org,schenney@chromium.org
> 
> Change-Id: Ic072356ff05e5c738f9b830a3ac398d0d8cb4f73
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1889710
> Reviewed-by: Takashi Sakamoto <tasak@google.com>
> Commit-Queue: Takashi Sakamoto <tasak@google.com>
> Cr-Commit-Position: refs/heads/master@{#710696}

TBR=wangxianzhu@chromium.org,tasak@google.com,schenney@chromium.org

Change-Id: Ia3500803eb9f24d078cc8919b453821147e3df9a
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1890950Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710882}

Now VisualViewport creates cc::Layers instead of GraphicsLayers, and
creates foreign layers directly during painting instead of by collecting
GraphicsLayers. This makes VisualViewport use the same code for CAP and
pre-CAP.

PaintLayerScrollableArea still uses GraphicsLayers which are created by
PaintLayerCompositor/CompositedLayerMapping.

GraphicsLayers created by PaintLayerCompositor/CompositedLayerMapping
no longer need to attach to VisualViewport which no longer creates
GraphicsLayers.

Bug: 1012594
Change-Id: I5ce76a3b5728d3810d85d536357cb437eea5fc4f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869126
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710881}

Bug: 1019148
Change-Id: Ia49f1ac8317e4270225017231179b41fa3436d17
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1890495Reviewed-by: Min Qin <qinmin@chromium.org>
Commit-Queue: Shakti Sahu <shaktisahu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710880}

The hope is when we move to a more recent version of androidx we can
makes BrowserFragment package private (by way of FragmentFactory).
This patch removes the need to use BrowserFragment directly.

BUG=none
TEST=none

Change-Id: I7a4469fcf620f38c36c84a580cf4b8f666542c9f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1888389
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710879}

Uppercases every word in manufacturer names.
Also saves chromeos device model names as the family name(chromebook)
instead of model name(eve/sand).

Bug: 1016332
Change-Id: I8d088d1707156529abd1d5e254d7704c990662e3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1879228Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Reviewed-by: Michael van Ouwerkerk <mvanouwerkerk@chromium.org>
Commit-Queue: Himanshu Jaju <himanshujaju@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710878}

The feature has shipped, so we don't need the content flag any more.

Bug: 959850
Change-Id: I21ff38122377cd66fbb4740187d0877c9fb7e058
TBR: avi@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873384
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710877}

We want to separate the HTTP auth cache by NetworkIsolationKey, as it
can be used for cross-site tracking. This will affect Enterprise more
then end users, so a (temporary) Enterprise opt-out seems warranted.

NOTRY: true
Bug: 993806
Change-Id: I96fdf314aadc5e68809f4dd34dfa2f90580d17ab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869469
Commit-Queue: Matt Menke <mmenke@chromium.org>
Reviewed-by: David Benjamin <davidben@chromium.org>
Reviewed-by: Owen Min <zmin@chromium.org>
Reviewed-by: Asanka Herath <asanka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710876}

Bug: 875486
Change-Id: I902d0e8246d01239f31d7cefc88be069bdc69756
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1846043
Auto-Submit: Wez <wez@chromium.org>
Reviewed-by: Albert J. Wong <ajwong@chromium.org>
Reviewed-by: Yuchen Liu <yucliu@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710875}

Bug: 943901
Change-Id: Icae1e9ef4865230ee29f6fd031a5d939c13d9120
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1889292Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Dan S <danan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710874}

Bug: 995916
Change-Id: I7408905aa40e083c5dac81efc34bb87c45ffcb62
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1888375Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Commit-Queue: Henrique Nakashima <hnakashima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710873}

This prepares for blink::ScrollbarDisplayItem (for CompositeAfterPaint
composited scrollbars) which will share ownership of cc::Scrollbar
with cc's painted scrollbar layers.

Also make sure that cc::Scrollbar is accessed from the main-thread
only.

Bug: 931486
Change-Id: If64b14d8d917272873d35f33302ecbb66b20126b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1884577Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710872}

Change-Id: I3c5f11a1d217b1c65af4b49a72d0fa31b9d3a862
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1890985
Commit-Queue: Luke Z <lpz@chromium.org>
Commit-Queue: Robert Ma <robertma@chromium.org>
Auto-Submit: Luke Z <lpz@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710871}

In certain cases, Gaia's /ListAccounts APIs claims accounts to be in a
valid state when they are actually invalid. This causes issues with
account reconciliation because |AccountReconcilor| uses /ListAccounts as
the source of truth and is unable to detect this state.
In this state, certain Google properties like Gmail for example send a
Mirror re-authentication header for the offending account. However, even
after the user re-authenticates the account, account reconciliation ends
up being a no-op because the reconcilor thinks that the user's cookies
are valid and there is nothing to reconcile.

Fix this by storing some flags in |CookieReminter| which are set when
we receive Mirror re-authentication headers from Gaia, and are cleared
when the next reconciliation cycle begins.

This is a temporary fix until we can submit https://crrev.com/c/1871591.

Bug: 1012649
Change-Id: I04fd971cdc788094f038ee808b4a38003ef48e22
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1883652Reviewed-by: David Roger <droger@chromium.org>
Commit-Queue: Anastasiia Nikolaienko <anastasiian@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710870}