GitLab

The counterpart CL in downstream is
https://chrome-internal-review.googlesource.com/c/chrome/ios_internal/+/3180818

Bug: 1085419
Change-Id: I3e20df0bb93d47009cdaa30896c52c8c648b05a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315432Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Commit-Queue: Ganggui Tang <gogerald@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791487}

Applies the fix suggested by dbertoni@ on the bug:

Adds a TearDown method which calls
StoragePartition::WaitForDeletionTasksForTesting() to wait for all
deletion tasks to finish and make sure QuotaDatabase does not
run into out of disk space errors.

Bug: 930481
Change-Id: I1d2203d0b6d817ef84ccbda206ab216e54f4fd80
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307644Reviewed-by: Martin Šrámek <msramek@chromium.org>
Commit-Queue: Jarryd Goodman <jarrydg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791486}

Previously VideoCaptureDeviceFactory interface provided
GetDeviceDescriptors() and GetSupportedFormats(). Both were synchronous.
That hasn't worked well on some platforms, particularly on Fuchsia.
Replaced both methods with asynchronous GetDevicesInfo(). The new method
returns device descriptors as well as list formats supported by each
device.

Bug: 1072932
Change-Id: If76abbc66db9fee54140a5e352eb0f8fd39f3294
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2306918
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791485}

Bug: 1106608
Change-Id: Ie71fcdea1186761fd6cc7f32ebf38ee0e497d843
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316695
Commit-Queue: Dmitry Gozman <dgozman@chromium.org>
Auto-Submit: Nate Chapin <japhet@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791484}

https://chromium.googlesource.com/external/github.com/google/shaderc/+log/ff8fe2df3529..34c9aac3f30d

2020-07-23 dneto@google.com Start shaderc v2020.3 development
2020-07-23 dneto@google.com Finalize shaderc v2020.2
2020-07-23 dneto@google.com Update CHANGES
2020-07-23 dneto@google.com Roll third_party/glslang/ 9eef54b25..3ee5f2f1d (11 commits)

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/shaderc-chromium-autoroll
Please CC radial-bots+chrome-roll@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/+doc/master/autoroll/README.md

Tbr: radial-bots+chrome-roll@google.com
Change-Id: I4390ce79f9a9f989085929968a5502282eb37d87
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2319114Reviewed-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@{#791483}

Replace GridLayout with BoxLayout and FlexLayout in cases where
GridLayout is not used as a true grid, but only for alignment.

This CL is part of the changes to apply documented best practice to
examples.

Bug: 897377
Change-Id: I789da2ebaa083f149079c36134dc8a1f48dd093a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316455
Commit-Queue: Keren Zhu <kerenzhu@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791482}

The reporting service delays reports by 60s. This gives the opportunity
to group several reports into a single request.

However, when running web_tests, we can't afford spending 60s. So this
is reduced to 100ms to avoid timeout.

So far, so good. The problem is about a second timer that used to be
proportional: |endpoint_backoff_policy.initial_delay_ms|. They are both
set to 60s. However in --run-web-tests, only the first is reduced to
100ms.

This patch reduced the second one to 100ms as well, to keep them always
proportional.

After this patch, the configuration becomes:

[Normal mode]
reporting_policy.delivery_interval = 60s;
reporting_policy.endpoint_backoff_policy.initial_delay = 60s

[web-tests mode]
reporting_policy.delivery_interval = 100ms;
reporting_policy.endpoint_backoff_policy.initial_delay = 100ms.

Bug: 1109194
Change-Id: I068a772e9eb95ec4c61466e290c400867ffbb63e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316215Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: Lily Chen <chlily@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791481}

Meet gives an option to request video quality of 360. Not all cameras
will natively return a height-360 size, so Chrome will go with the
next-biggest capture size, and letterbox-and-scale the video frame.

On the machine where I reproduced this, the media::VideoFrame had the
following attributes.
- visible_rect:0,60 640x360
- natural_size:640x360
- coded_size:640x480

This exposed the following bug in the combination of the functions
VideoResourceUpdater::CreateForSoftwarePlanes and
PaintCanvasVideoRenderer::Copy.
* The function VideoResourceUpdater::CreateForSoftwarePlanes creates a
  resource of size |coded_size|, and expects that
  PaintCanvasVideoRenderer::Copy will populate the |visible_rect|
  sub-rectangle of that resource.
* PaintCanvasVideoRenderer::Copy actually copies not to |visible_rect|,
  but rather to rectangle at (0,0) that has the size of |visible_rect|.

The consequence is that we end up viewing the resource through a
misaligned letterbox.

The fix is is to inline PaintCanvasVideoRenderer::Copy (which is only a
few lines long) in VideoResourceUpdater::CreateForSoftwarePlanes, and
specify the correct destination rectangle.

Also add some comments to clarify the function's behavior. Note that
this behavior was switched in crrev.com/545920.

Bug: 1090435
Change-Id: Icef81728defc0cf46b35180dada5d68f24e6b21d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318313
Auto-Submit: ccameron <ccameron@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791480}

This CL changes the behavior of the dialog that pops up at
chrome://settings/clearBrowserData by setting the ignore-enter-key
attribute. The key is ignored because it results in destructive
action and is very easy to trigger by mistake.

Bug: 1108630
Change-Id: If557df2e741a981da1d983bea4fc87989e65bac7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316439
Auto-Submit: Orin Jaworski <orinj@chromium.org>
Reviewed-by: dpapad <dpapad@chromium.org>
Commit-Queue: Orin Jaworski <orinj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791479}

Bug: 1109466
TBR: vasilyt@chromium.org
Change-Id: Ie2ada7d94ed618caf3c96e20c543fc378fa0d975
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318927Reviewed-by: Peng Huang <penghuang@chromium.org>
Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791478}

The Chrome menu (the three dots at the right of the omnibar) stopped
being openable recently, because it shows up as a combo box. Modify
the combo box behavior to allow for some elements detected as combo
boxes to not be combo boxes.

This is a temporary fix; the long-term fix is to properly populate
the location for combo box pop-up windows.

AX-Relnotes: n/a.
Bug: 1106529
Change-Id: Ica0494ce85246abb73efb899d15abad38d700ebb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2300982
Commit-Queue: Anastasia Helfinstein <anastasi@google.com>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791477}

Bug: 1109316
Change-Id: I3dec74d1f9a8448602c5a5a5b998f344870605c9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317836Reviewed-by: Peter Boström <pbos@chromium.org>
Commit-Queue: Caroline Rising <corising@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791476}

This is approved and can be enabled.

Bug: 1084222
Change-Id: I4bcf0c0347e6eaa9ee7abb12dad54e4addda8aaf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2304773Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791475}

This test attempts to test a corrupted disk condition.  Unfortunately
it is exceptionally hard to make stable since the simple disk_cache
layer is between cache_storage and the disk.  The simple disk_cache
has its own set of threads and timeout mechanisms.

This CL removes the test since the marginal benefit of testing the
condition does not merit the cost of fixing the test.  The test
was already disabled.

Bug: 1041371
Change-Id: I311392fddf8691fd27c827e582d14756f1bce89f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316692Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Commit-Queue: Ben Kelly <wanderview@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791474}

This is the second of 2 changes that rename classes that use blacklist
in their class/variable/function names. There are no functional
differences here.

- Rename files with blacklist in their name to use blocklist instead.
- Update header guards to match the new filenames.
- Update all #includes that reference these files.
- Update BUILD.gn & DEPS files to use new filenames.

Bug: 1097278
Change-Id: If723c642a4f915be8f59ce0f4dbd8365c7073014
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2311061Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Reviewed-by: Owen Min <zmin@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Aaron Colwell <acolwell@chromium.org>
Commit-Queue: Aaron Colwell <acolwell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791473}

If a RemotePlayback availabilityCallback invokes watchAvailability(),
it may cause changes to the underlying |availability_callbacks_|. This
can invalidate the iterator we are using to loop over the callbacks.

This CL copies the callbacks to a vector before invoking them, allowing
them to add/remove callbacks without problem.

Bug: 1108497
Change-Id: I78220da0b8e10c1d6c0e4fa5e15ada81f10f8fc3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314981
Auto-Submit: Thomas Guilbert <tguilbert@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Commit-Queue: Thomas Guilbert <tguilbert@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791472}

Update Feed placeholder layout for a lighter border and
use the screen width to assign the width of placeholders.

Bug: 1076139
Change-Id: I6080cbf2362c701578004c091439be05c565420c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2311424
Commit-Queue: Hao Dong <spdonghao@chromium.org>
Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Reviewed-by: Xi Han <hanxi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791471}

Previously, when a same-doc navigation occurs before the user has
interacted with the page, we were simply leaving everything as it was
with the full URL showing. This worked fine until we removed the "edit
bump" (crbug.com/1101486), which involved setting the display rect on
page load to contain all of the URL except the scheme and trivial
subdomains. Now that the display rect is set on page load, we have to
make sure it's adjusted again on a same-doc navigation, in case the
URL has become longer. Otherwise the URL after the same-doc navigation
would be cut off where the previous URL ended.

Bug: 1108955
Change-Id: Id6240ef347e30ac061c4f7121b753233e6fe26d0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316792Reviewed-by: Tommy Li <tommycli@chromium.org>
Commit-Queue: Emily Stark <estark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791470}

See go/inclusive-codebase.

Bug: b/161801556
Test: Local compile
Change-Id: I6f489e910c4050dab71b2d2bc30fdfb6679fb6bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316450
Auto-Submit: Yue Li <updowndota@chromium.org>
Reviewed-by: Jeroen Dhollander <jeroendh@chromium.org>
Commit-Queue: Yue Li <updowndota@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791469}

Also adds device type and name to the ShareTarget mojo struct to pass
them along to the UI. ShareTarget is converted to a struct as we need to
modify the fields when deserializing from mojo.

Bug: 1108367
Change-Id: I1e9e38cad39b6a3b9f4ac8de528c92ed1a06c3a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314356Reviewed-by: Alex Gough <ajgo@chromium.org>
Reviewed-by: Alex Chau <alexchau@chromium.org>
Commit-Queue: Richard Knoll <knollr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791468}

Add an evaluator for "Str('')".

Tbr: jdarpinian@chromium.org
Tbr: shrekshao@google.com
Bug: 1097235
Change-Id: I9f35c8696215970e95d65dd476f312705fbf59d8
No-Try: True
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318651Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791467}

hr-timestamp/input-events.htmlEvent timestamp tests that the received
events on the page should be equal to the timestamp provided by the
eventSender's recorded last event. But we should deprecate eventSender in
the future, and GpuBenchmarking sends events based on the current system
time, which cannot be equal to the received events' timestamp.

Some Android bots such as android-pie-x86-rel have 1 ms difference, so
I add 1 ms error.

TBR=bokan@chromium.org，majidvp@chromium.org

Bug: 1047176
Change-Id: Ie2e52d0f097aa399823208cbb5ff2df24a23c56a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314687Reviewed-by: Lan Wei <lanwei@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791466}

On page refresh, signal that GDFGRP request can be made again,
regardless of timeout.

Bug: 949269
Change-Id: Idcf75c8125e6fd0ddd8c1ae06ccbb80385f57c65
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2276408Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Tommy Martino <tmartino@chromium.org>
Reviewed-by: Jared Saul <jsaul@google.com>
Commit-Queue: Manas Verma <manasverma@google.com>
Cr-Commit-Position: refs/heads/master@{#791465}

This change:
1. Adds logic for popup buttons to inherit setsize from a controlled
element. This is important because ChromeVox reports setsize when
focusing a popup button and we want to make sure it reports the correct
value.
2. Adds an AXTreeTest for new logic.
3. Adds ChromeVox test for new logic.
4. Splits flakey test, which was disabled, into two separate tests
which both pass.

expanded popup buttons.

Bug: 1108895
Change-Id: I45e70c8ec20123e0194159f9e884daf4413b6c23
AX-Relnotes: Fix issue where ChromeVox was reporting "0 items" for
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315352
Commit-Queue: Akihiro Ota <akihiroota@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791464}

It's not clear if these tests will still be flaky on the CI or not. We
made some changes that may have deflaked them.

Bug: 1103865, 1021474b
Change-Id: Icfe7ed6637868fc29e30c0d182f985a6b38aa000
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2311144
Commit-Queue: Nina Satragno <nsatragno@chromium.org>
Auto-Submit: Nina Satragno <nsatragno@chromium.org>
Reviewed-by: dpapad <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791463}

When in fullscreen, the soft keyboard doesn't adjust the window size,
so we need extra logic (copied from Chrome) to adjust the web contents
size in this case.

Bug: 1107651
Change-Id: Ieded2ca098cf4dd5ed210e2043f1b94667579071
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313979
Commit-Queue: Evan Stade <estade@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791462}

UI demo: https://screenshot.googleplex.com/PdYajrS8FfE.gif

Bug: 1070620, 1107807
Change-Id: I2fac517d4aefd5999449988cfe7d289f76e67563
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2303714Reviewed-by: Theresa  <twellington@chromium.org>
Reviewed-by: Natalie Chouinard <chouinard@chromium.org>
Reviewed-by: Martin Šrámek <msramek@chromium.org>
Commit-Queue: Andrey Zaytsev <andzaytsev@google.com>
Auto-Submit: Andrey Zaytsev <andzaytsev@google.com>
Cr-Commit-Position: refs/heads/master@{#791461}

The Chromium logging of SkDebugf messages was originally intended to be
INFO, but was sometimes changed to ERROR because otherwise the SkDebugf
in SK_ABORT was not logged, making crashes more difficult to diagnose.
This was done with https://crrev.com/c/1348630 but this leads to all
SkDebugf calls being logged as ERROR when DCHECK_IS_ON.

Instead, restore SkDebugf messages to INFO and define SK_ABORT directly
and define it to work the way it is expected to work, as a FATAL message
which aborts.

Bug: chromium:1050863
Change-Id: If4c5525cd3f0ee762ed9a95c22148970e6962dd5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316816
Commit-Queue: Ben Wagner <bungeman@chromium.org>
Reviewed-by: Brian Salomon <bsalomon@google.com>
Cr-Commit-Position: refs/heads/master@{#791460}

It now lives in variations_field_trial_creator.cc, so this copy
is not used.

Bug: none
Change-Id: I8bccc220e29b550a5b45ebd95aa557f3cf2ac64b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2305112
Auto-Submit: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Steven Holte <holte@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791459}

TBR=govind@chromium.org

Change-Id: Ia0c4797f00ad39ec656e1f36fa3c2042d9238424
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317828Reviewed-by: Ben Mason <benmason@chromium.org>
Reviewed-by: Krishna Govind <govind@chromium.org>
Commit-Queue: Krishna Govind <govind@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791458}

Pointed out in crrev.com/c/2315897 that this member name is
confusing, whether it is a frame rect used in layout, or ink
overflow.

Renamed to clarify it is a frame rect.

Bug: 1108580
Change-Id: I3cc1b32930c60068ac6a63514f6216c07b4b8129
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315462Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791457}

This CL makes sure the list of ports visible in the serial port chooser
is ordered by file paths so that users can quickly jump to the desired
serial port.
It is especially useful when system has plenty of tty ports.

Screenshot: https://i.imgur.com/MoRcx5z.png

Bug: 884928
Change-Id: Ib0efe74eb2bd03263b7bf8e2fc6b8a719c839410
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2312316
Commit-Queue: François Beaufort <beaufort.francois@gmail.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791456}

This CL fully deletes two Pedals that won't be launched, including
all data and related unit tests. This is done to simplify upcoming
changes to the full set of remaining Pedals (no sense maintaining
code that isn't going to fly).

Bug: 893183
Change-Id: I1687774557efe416f17b1da852e0e6e0da6e88d8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316950
Auto-Submit: Orin Jaworski <orinj@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Commit-Queue: Orin Jaworski <orinj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791455}

One call had some extra logic that was missing from the other
call. Most likely it didn't trigger a bug because it's unlikely we'd
ever have a scenario where the root object's AXRelativeBounds changes
but the root isn't serialized. Still, this is definitely the right
thing to do, and it makes the code in RenderAccessibilityImpl
simpler and more readable.

Bug: 1109081
Change-Id: If4ccb9d5dab5393c9b965af48943161c549fd272
AX-Relnotes: N/A
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314874
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791454}

It seems that resetting the alert coordinator is actually dismissing the
ReadingList ViewController.
This is not needed as nothing is relying on the coordinator to be nil,
so removing the nil assignment is working.

Fixed: 1105852
Change-Id: I1cf8c38e6f6b8d1f8456e6b2ed439e38c44db275
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316204
Commit-Queue: Gauthier Ambard <gambard@chromium.org>
Commit-Queue: Olivier Robin <olivierrobin@chromium.org>
Auto-Submit: Gauthier Ambard <gambard@chromium.org>
Reviewed-by: Olivier Robin <olivierrobin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791453}

https://pdfium.googlesource.com/pdfium.git/+log/9e1fc05ef7a2..df34e3c37407

2020-07-25 tsepez@chromium.org Make ownership of XML document slightly saner.
2020-07-24 tsepez@chromium.org Rename CFXA_DocumentParser to CXFA_DocumentBuilder.
2020-07-24 tsepez@chromium.org Make an XML-tree be the input to CFXA_DocumentParser().
2020-07-24 tsepez@chromium.org Retain layout items rather than raw widgets in CFXA_TabParam.
2020-07-24 tsepez@chromium.org Make CPDFXFA_Context::m_DocEnv into a pointer.
2020-07-24 tsepez@chromium.org Simplify ~CPDFXFA_Context(), part 2
2020-07-24 tsepez@chromium.org Slightly simplify ~CPDFXFA_Context().
2020-07-24 thestig@chromium.org Fix issue with FPDFText_GetLooseCharBox() and the tranformation matrix.
2020-07-24 thestig@chromium.org Add experimental APIs to get XFA data.
2020-07-23 tsepez@chromium.org Move fxv8_unittests.{cpp,h} and fxgc_unittests.{cpp,h} to testing/
2020-07-22 tsepez@chromium.org Make test environment setup consistent with gtest model.
2020-07-22 tsepez@chromium.org Move class EmbedderTestEnvironment to standalone V8TestEnvironment.

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pdfium-autoroll
Please CC pdfium-deps-rolls@chromium.org 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/+doc/master/autoroll/README.md

Bug: chromium:1109108
Tbr: pdfium-deps-rolls@chromium.org
Change-Id: I58d04da158120610f2cc3dbc3c36eec5a169c806
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318966Reviewed-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@{#791452}

Unable to produce this failure locally.

As discussed on the bug the reason for the failure is most probably
because SettingsActivity was not closed. Closing SettingsActivity should
resolve the failure.

The test will be enabled in a separate cl.

Bug: 1102296
Change-Id: I1cfae80f48dc84d04abb8d3e87ff7c7879987bd3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317207
Commit-Queue: Tanmoy Mollik <triploblastic@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791451}

Make sure this actually fails on posix, and return the correct error
code when trying to create a file or directory fails because the other
type already exists.

Bug: 1098001
Change-Id: I265c079a436e2107e1ee9c146e87c9e9ea3db7a1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317989
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791450}

Previously, private_membership was depending on specific
targets in abseil before facilitating the component build for it.
Now, it can directly depend on its component build.

Bug: 1094745
Change-Id: I1c4e57fa1686c899fe5cfb49423ad033e0f40d58
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2245613Reviewed-by: Amr Aboelkher <amraboelkher@google.com>
Reviewed-by: Amr Aboelkher <amraboelkher@chromium.org>
Reviewed-by: Mirko Bonadei <mbonadei@chromium.org>
Commit-Queue: Amr Aboelkher <amraboelkher@google.com>
Cr-Commit-Position: refs/heads/master@{#791449}

The problem was caused by the expansion of damage under the pixel-moving
backdrop filters didn't take into account the damage coming from an
earlier stage (cc) in the pipeline.

Bug: 1107376
Change-Id: Ie734cdbec910b17bb4b12fc9f209345e04ad12e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2310389
Commit-Queue: Jun Liu <yjliu@chromium.org>
Reviewed-by: kylechar <kylechar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791448}