GitLab

KeyboardController has the concept of "locked". When the keyboard is
locked (e.g. when it is launched from the accessibility menu), the
work area of the screen is shrunk, so that only the part above the
keyboard is considered 'useable'.

Currently, this is implemented in the shelf by observing changes to the
keyboard bounds. If the bounds change and the keyboard is locked, we
update the work area with the given bounds.

While this is correct, whether the keyboard is locked or not should be
internal to the keyboard. Instead, shelf should be listening for the
*displaced* bounds, which essentially tell observers how much of the
screen is now unuseable.

Thus, we replace the keyboard bounds in shelf to either the displaced
bounds or the occluded bounds, depending on what the shelf actually
wants. If the bounds are used for the work area, then it's the displaced
bounds. Otherwise, it's the occluded bounds.

Change-Id: I7c53d0b2fe8b3b6769ce7113b924def34db2785e
Bug: 845780
Reviewed-on: https://chromium-review.googlesource.com/1146530Reviewed-by: Yusuke Sato <yusukes@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Blake O'Hare <blakeo@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579992}

Frames have more granular information than the container,
so let's use the color space from the frames rather than
from the container.

BUG=870050

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I4dd972561dd85f8ddce3ca55a01e34dc3a8cf386
Reviewed-on: https://chromium-review.googlesource.com/1155785
Commit-Queue: Fredrik Hubinette <hubbe@chromium.org>
Reviewed-by: Tom Finegan <tomfinegan@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579991}

sql::Connection represents an opened SQLite database. Pedantically, the
name is correct. At the same time, it is inconsistent with the naming
convention of similar software -- IndexedDB, LevelDB, and WebSQL all use
a derivative of "Database" (IDBDatabase, DB, WindowDatabase) to name
this concept. Furthermore, most sql::Connection instances have names
like "db" and "database".

This CL renames the class to sql::Database, reducing the cognitive load
caused by dissonances like "sql::Connection db_".

TBR=mpearson

Bug: none
Change-Id: I8abf34016bca236b6e38a772f5848e7ea9bf1c59
Reviewed-on: https://chromium-review.googlesource.com/1157876
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579990}

chrome.send() must always be enabled for dialogs, since dialogs rely on
chrome.send() to notify their handlers that the dialog should be closed.

Bug: 824568
Change-Id: I12325c243e2f2cf04d417ea71b03519bcb3d1159
Reviewed-on: https://chromium-review.googlesource.com/1145580Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579989}

Rename "isInteresting" to "isActionable" for precision.

Bug: None
Change-Id: I40d6e2c74b80a0717f0c2b864010d5650bd69378
Reviewed-on: https://chromium-review.googlesource.com/1159179Reviewed-by: David Tseng <dtseng@chromium.org>
Commit-Queue: Zach Helfinstein <zhelfins@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579988}

There are several DidUpdateLayout functions but it is not obvious that
these are only called when the main frame lays out (see the callsite in
Document::LayoutUpdated). I confirmed this locally. This patch renames
these to DidUpdateMainFrameLayout so it is more obvious that this is
only called for main frame layouts.

The comments indicate that DidUpdateMainFrameLayout should only be
called with clean layout, but this is not true for the callsite in
RenderViewImpl::OnEnablePreferredSizeChangedMode.  A TODO has been added
to clean up RenderViewImpl::OnEnablePreferredSizeChangedMode.

Bug: 868983
Change-Id: I66de3e8c402e7edeff9a8b1e7991716f55b771a8
Reviewed-on: https://chromium-review.googlesource.com/1156991Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579987}

Bug: 841671
Change-Id: Ieb86ea9e6636651edd0655c2721c11ea430f96cd
Reviewed-on: https://chromium-review.googlesource.com/1148022Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Commit-Queue: Paul Dyson <pdyson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579986}

The cookie RFC[1] does not define an encoding for cookie names/values;
they are treated as a sequence of octets.

The Cookie Store spec[2] mandates treating the octets as UTF-8 encoded.
When decoding octet sequences into strings, the decode should be done
without treating a leading U+FEFF as a BOM. Add a test to verify this.

[1] https://tools.ietf.org/html/draft-ietf-httpbis-rfc6265bis-02
[2] https://wicg.github.io/cookie-store/

Bug: 729800
Change-Id: I23b7eb82b35862b8797a203ae6ea86cbd69001d2
Reviewed-on: https://chromium-review.googlesource.com/1159336Reviewed-by: Victor Costan <pwnall@chromium.org>
Commit-Queue: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579985}

This one is real simple.

I've also tweaked the constant for the native default to
be of the same type as the fromNative that uses it, so
it's slightly easier to read.

Change-Id: Iaaa24d4ee9dbf195ec520a568006812d4549f72e
Reviewed-on: https://chromium-review.googlesource.com/1158997Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Commit-Queue: Johannes Henkel <johannes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579984}

Bug: 866671
Change-Id: Ibee4b8efc16008d4d181b3008860858c9d75efa5
Reviewed-on: https://chromium-review.googlesource.com/1157872
Commit-Queue: Bret Sepulveda <bsep@chromium.org>
Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579983}

When Download DB is enabled, there is no need to add an incomplete download
to history.
The only case we need to add it is when extension is used, or it is a save page
download.

Bug: 842245
Change-Id: I1a1ba64510a73c2ce70a6fd50709e238da6129cf
Reviewed-on: https://chromium-review.googlesource.com/1155795
Commit-Queue: Min Qin <qinmin@chromium.org>
Reviewed-by: Xing Liu <xingliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579982}

Deprecates obsolete histograms.
Adds integration tests for the data migration.

BUG=866550

Change-Id: I6fbce5a8725584aa0c550d28449b1c5a9d7a49f5
Reviewed-on: https://chromium-review.googlesource.com/1149013Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: David Tseng <dtseng@chromium.org>
Commit-Queue: Katie Dektar <katie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579981}

This seems to affect only the painting of the frame background and Linux caption
buttons.  In testing the first and from code inspection of the second, both seem
to want "the actual height above the toolbar", which doesn't include this
overlap.

This eliminates an ugly 1 DIP misalignment of the theme background image bottom
with the toolbar top in some themes.

Bug: 866671
Change-Id: I55d1aea4c3af656ae427373dff9bacc76bb932ab
Reviewed-on: https://chromium-review.googlesource.com/1157875
Commit-Queue: Bret Sepulveda <bsep@chromium.org>
Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579980}

Recently, Console message border colors became CSS variables, which
are preserved in dark theme by default. This CL fixes the regression
by giving explicit dark colors.

Screenshot: https://imgur.com/a/7Hj2GXb

Bug: none
Change-Id: Ib62c8ffa0454303e35699f1d1c70e398a185d52a
Reviewed-on: https://chromium-review.googlesource.com/1159208
Commit-Queue: Erik Luo <luoe@chromium.org>
Commit-Queue: Andrey Lushnikov <lushnikov@chromium.org>
Reviewed-by: Andrey Lushnikov <lushnikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579979}

BUG=762641
TBR=alemate@google.com

Change-Id: Id6046d0ff6de24fdc47bac127cf839954fac484b
Reviewed-on: https://chromium-review.googlesource.com/1159350Reviewed-by: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#579978}

This CL routes onBeforeShow event to the oobe-dialogs, that are not subnodes
of another Polymer object.

Bug: 828999
Change-Id: Id2cee750d2364e53052133bbea7d27ea2c1ca0a2
Reviewed-on: https://chromium-review.googlesource.com/1157912Reviewed-by: Yury Khmel <khmel@chromium.org>
Reviewed-by: Toni Barzic <tbarzic@chromium.org>
Commit-Queue: Alexander Alekseev <alemate@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579977}

Bug: 828999
Change-Id: I2be47264b2b3140e777b6d711e36b87bfa40daed
Reviewed-on: https://chromium-review.googlesource.com/1157914Reviewed-by: Toni Barzic <tbarzic@chromium.org>
Commit-Queue: Alexander Alekseev <alemate@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579976}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/af27deaf0199..0da902e4fde4


Created with:
  gclient setdep -r src-internal@0da902e4fde4

The AutoRoll server is located here: https://src-internal-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.


TBR=mmoss@chromium.org

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

I removed the ScreenProvider interface a while back, so naming the file
screen_provider doesn't make sense anymore.

BUG=none
test=none

Change-Id: Ie53dca7acd9aae61a1f196c240397c7fc78255bb
Reviewed-on: https://chromium-review.googlesource.com/1159264Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579974}

* Provide default implementations for newly added methods for dismissing
  and describing items.
* Split out base classes for SimpleListObservable
  and SimpleRecyclerViewMcp that support partial updates.
  SimpleListObservable and SimpleRecyclerViewMcp now internally use Void
  for the payload type to indicate that partial updates are not
  supported.
* Decouple ChildNode and InnerNode from the content suggestions code by
  parameterizing them. In a future CL they should be moved out of the
  ntp.cards package and renamed.

Bug: 805070
Change-Id: I1b996d8af4c85e07bdf45e435eb045a626669ba2
Reviewed-on: https://chromium-review.googlesource.com/1109973Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Bernhard Bauer <bauerb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579973}

css3/filters/effect-drop-shadow-hw.html is flaky on Linux (times out).
Disable it during investigation.

Bug: chromium:862806
Tbr: sugoi@chromium.org
Change-Id: If662eca90584c819efb002881ae17aef7e7be637
Reviewed-on: https://chromium-review.googlesource.com/1159272Reviewed-by: Peter Boström <pbos@chromium.org>
Commit-Queue: Peter Boström <pbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579972}

Bug: None
Test: Local compile
Change-Id: Id996eaa35211587410d4871c9ed55247683c6edc
Reviewed-on: https://chromium-review.googlesource.com/1159392Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Commit-Queue: Yue Li <updowndota@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579971}

https://android.googlesource.com/platform/external/perfetto.git/+log/6af2bfe03baf..3c868f436bc0


git log 6af2bfe03baf..3c868f436bc0 --date=short --no-merges --format='%ad %ae %s'
2018-08-01 treehugger-gerrit@google.com Merge "Propagate tracing session to the producers"


Created with:
  gclient setdep -r src/third_party/perfetto@3c868f436bc0

The AutoRoll server is located here: https://perfetto-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.


TBR=perfetto-bugs@google.com

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

Before this CL TimeDelta had saturation behavior for translating
from/to other values, but had clamping behavior for its computation.
That is, invariants like the following did not hold:

TimeDelta::Max() - TimeDelta::FromSeconds(1) == TimeDelta::Max()

This CL fully implements saturation behavior, such that TimeDelta::Max()
and TimeDelta::Min() are treated as positive and negative infinity
regardless, with all the expected mathematical consequences.

The one exception is that adding/subtracting a saturated TimeDelta to a
TimeClass is still undefined. This was left undefined because we are not
yet making a statement on whether TimeClass should be considered to have
clamping or saturating behavior for values outsied of range.

See the linked bug, or also the discussion at
https://groups.google.com/a/chromium.org/forum/#!topic/platform-architecture-dev/S4umX2sOvrk

Bug: 869387
Change-Id: I2b3f98c69e7fc5030a6e210d75409d667b73c5ac
Reviewed-on: https://chromium-review.googlesource.com/1155264
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579969}

https://pdfium.googlesource.com/pdfium.git/+log/2563fc3895f2..0562ff4f6e2e


git log 2563fc3895f2..0562ff4f6e2e --date=short --no-merges --format='%ad %ae %s'
2018-08-01 tsepez@chromium.org Bounds check lineSrc in JBig2_Image.cpp.
2018-08-01 rharrison@chromium.org Add in support for using .evt in make_expected.sh


Created with:
  gclient setdep -r src/third_party/pdfium@0562ff4f6e2e

The AutoRoll server is located here: https://pdfium-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.



BUG=chromium:867501
TBR=dsinclair@chromium.org

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

user queries.

Current iteration:
1. Autocomplete queries will only autocomplete if it is confident in a
   url or text query (no apps or answer cards).
2. Autocomplete is based off of the first result view in the
   SearchResultPageView.
3. Up/Down/Left/Right/Tab keys all trigger autocomplete.

Bug: 865543
Change-Id: I8be9ba36f4bb79bc250b64d289919bd898144862
Reviewed-on: https://chromium-review.googlesource.com/1141118
Commit-Queue: Daniel Zhang <oxyflush@google.com>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Alex Newcomer <newcomer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579967}

I am not aware of any features which still require this.

Bug: 836119
Change-Id: Id423a3dd6bafd6cbf11786a20e8e6776792ea739
Reviewed-on: https://chromium-review.googlesource.com/1131822Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Rahul Chaturvedi <rkc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579966}

Change-Id: I567c131eaedfe6c232afb61afb74b83da19c7017
Reviewed-on: https://chromium-review.googlesource.com/1150685
Commit-Queue: Ryan Hamilton <rch@chromium.org>
Reviewed-by: Zhongyi Shi <zhongyi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579965}

Tbr: atotic@chromium.org
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: I33fb8d23fbb36138045d3281442046992d9e69ee
Reviewed-on: https://chromium-review.googlesource.com/1159270Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579964}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/2d1c2ecd2d8c..3fe4043d9320


git log 2d1c2ecd2d8c..3fe4043d9320 --date=short --no-merges --format='%ad %ae %s'
2018-08-01 chrome-bot@chromium.org Update config settings by config-updater.
2018-08-01 dgarrett@google.com report_stage: Use Legoland for failed slave builders.
2018-08-01 chrome-bot@chromium.org Update config settings by config-updater.


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

The AutoRoll server is located here: https://chromite-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.


TBR=chrome-os-gardeners@chromium.org

Change-Id: I66f3c81c82c31c0f8aea1cb3bef7d7f85ccbbaf9
Reviewed-on: https://chromium-review.googlesource.com/1159029Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#579963}

* Mask images were the wrong size for some buttons, leading to background color
  bleed in custom themes.
* Mask images were inconsistent about which borders they included.
* Maximize/restore images had red on the right edges for no obvious reason.
* Close button images colored parts of the button border that no other images
  did.

Bug: none
Change-Id: I9a2e80bb07c3d883cfe104696039457828d07d7f
Reviewed-on: https://chromium-review.googlesource.com/1157702Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579962}

Since CompletionOnceCallback is non-copyable, therefore WaitingForRead
becomes non-copyable.  This Cl adds a move constructor so that
WaitingForRead can be put in a std::map.

Bug: 807724
Change-Id: I57dce65d46626ce0c39cd3e2e738ad9d6979165c
Reviewed-on: https://chromium-review.googlesource.com/1156862Reviewed-by: Ryan Hamilton <rch@chromium.org>
Commit-Queue: Bence Béky <bnc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579961}

Previously it was possible to have non-record shaders have a record,
which is invalid.  If these get written back out again, they are not
valid and will DCHECK.  We should just prevent these in the first place.

Bug: 868674
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I3da083024fcd47c4577b2a59c9a3014da2097e50
Reviewed-on: https://chromium-review.googlesource.com/1159113Reviewed-by: Khushal <khushalsagar@chromium.org>
Commit-Queue: enne <enne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579960}

Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Ic1203515dfdb853ff076aa838bc27ff008f1b187
Reviewed-on: https://chromium-review.googlesource.com/1150614
Commit-Queue: Ryan Hamilton <rch@chromium.org>
Reviewed-by: Abhishek Arya <inferno@chromium.org>
Reviewed-by: Zhongyi Shi <zhongyi@chromium.org>
Reviewed-by: Helen Li <xunjieli@chromium.org>
Reviewed-by: Ramin Halavati <rhalavati@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579959}

This patch cleans up how RunLoop is used in the test
MediaRouterMojoImplTest.RegisterAndUnregisterMediaSinksObserver, which
will fail with upcoming Mojo changes.

Tested with https://chromium-review.googlesource.com/c/chromium/src/+/1145692
applied.

Bug: 869550
Change-Id: I9a7b0d18d3422101a775490863d825df4fd51ec4
Reviewed-on: https://chromium-review.googlesource.com/1159271Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Derek Cheng <imcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579958}

Launch bug: 863984

Bug: 865140
Change-Id: I1b67dd974d2eb5e15965d830c2fb304f8e9501a8
Reviewed-on: https://chromium-review.googlesource.com/1153837
Commit-Queue: Jian Li <jianli@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Dmitry Titov <dimich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579957}

Test is flaky, disable during investigation.

Bug: chromium:868647
Tbr: skym@chromium.org
Change-Id: I23fdc1c1041b48806437e597a495783cf59e355d
Reviewed-on: https://chromium-review.googlesource.com/1159265Reviewed-by: Peter Boström <pbos@chromium.org>
Reviewed-by: Sky Malice <skym@chromium.org>
Commit-Queue: Peter Boström <pbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579956}

This CL changes the behavior to show dialog one by one,
not showing all of them at once.
This CL also fixes an issue that DownloadFilePicker is not
deleted in some cases.

BUG=868619

Change-Id: I71958b8c8d1383d95996d00c58c84c5523e08bd1
Reviewed-on: https://chromium-review.googlesource.com/1157141
Commit-Queue: Min Qin <qinmin@chromium.org>
Reviewed-by: Xing Liu <xingliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579955}

Move message text from title to body and add a Gpay logo in the title.

Updated mock go/autofill-paradise.

Bug: 852904
Change-Id: I94c18fbdc87fd527efb53b87a4e4190c83c0fcd5
Reviewed-on: https://chromium-review.googlesource.com/1157699Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Siyu An <siyua@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579954}

This adds support for:
1) Safe Search
2) YouTube restricted mode
3) restricting consumer accounts
through Group Policy.

The other supporting change is to make ThrottlingURLLoader handle a throttle changing the URL in WillStartRequest.

Bug: 841313
Cq-Include-Trybots: luci.chromium.try:linux_mojo
Change-Id: Ic98e14dd5fa7b5b00d4befd3314aca7a67e6ba5a
Reviewed-on: https://chromium-review.googlesource.com/1152507Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579953}