GitLab

Mark virtual/scroll_customization/fast/scroll-behavior/scroll-customization/scroll-customization-property.html as failing

Bug: 864891
Change-Id: Iff16e5ae02793ffb9d0afb0a806b92ea0ea08b1b
Tbr: ekaramad@chromium.org
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/1141458Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575950}

This patch rebaselines one text dump differences which is as
intended, and two 1px line position differences in vertical
flows. From the manual review of build 8046.

TBR=cathiechen@tencent.com
NOTRY=true

Bug: 591099
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: I4de0239b88bb3f7bf06e829c0f9f5a3e62f20000
Reviewed-on: https://chromium-review.googlesource.com/1141457
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575949}

This patch implements |std::string DumpSelectionInfo()| so that
we can check a SelectionStatus tree with text diff.

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: Ib42cebfc5a7f1908a4e748f622bbdae9c24987c6
Reviewed-on: https://chromium-review.googlesource.com/1136335Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Commit-Queue: Yoichi Osato <yoichio@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575948}

Bug: 864888
Change-Id: I2cd98b7c79479f7a5965fdbf9ef2182cb578d5a2
Tbr: yosin@chromium.org
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/1141455Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575947}

https://pdfium.googlesource.com/pdfium.git/+log/8e0c0dbc4876..89063ecda876


git log 8e0c0dbc4876..89063ecda876 --date=short --no-merges --format='%ad %ae %s'
2018-07-18 thestig@chromium.org Improve image size validation in CPDF_ScaledRenderBuffer.
2018-07-18 thestig@chromium.org Simplify CPDF_Creator::InitID().


Created with:
  gclient setdep -r src/third_party/pdfium@89063ecda876

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.


TBR=dsinclair@chromium.org

Change-Id: I095055060147434724d4269cbac046344fb3e385
Reviewed-on: https://chromium-review.googlesource.com/1141464Reviewed-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@{#575946}

Bug: 864887
Change-Id: I9210134ed670cd46026cd6f9d83a6336460ea140
Tbr: sunyunjia@chromium.org
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/1141453Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575945}

As a known issue, this doesn't respond to turning on/off the docked
magnifier.

Test: manually verified by rotating screen and zooming by ctrl-shift-+.
Bug: 862575
Change-Id: I7e74b4ce701c017b77df59cce00a30b0c3ebc821
Reviewed-on: https://chromium-review.googlesource.com/1134633Reviewed-by: Yoshiki Iguchi <yoshiki@chromium.org>
Commit-Queue: Tatsuhisa Yamaguchi <yamaguchi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575944}

When an onDirectoryChanged event is received for that grand root, rescan
the grand root and update its visiblity in the UI.

Bug: 854153
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: Ie36dabdd9348e7c174a22438b29ce8953c81d68e
Reviewed-on: https://chromium-review.googlesource.com/1136332Reviewed-by: Sasha Morrissey <sashab@chromium.org>
Commit-Queue: Sam McNally <sammc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575943}

Remove the constants kMaximumValidPortNumber and kInvalidPortNumber from
kurl.cc as they are confusing and don't actually do anything.

Also change remaining CHECKs in KURL::Port back to DCHECKs now that we
have confidence the change is safe.

Also make the method comment less confusing.

BUG=606462

Change-Id: I4719b8611cc6f3f0c5f488d8c86f3b6b8ad6d88f
Reviewed-on: https://chromium-review.googlesource.com/1127083
Commit-Queue: Adam Rice <ricea@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Eric Roman <eroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575942}

# This is an automated release commit.
# Do not revert without consulting chrome-pmo@google.com.
NOAUTOREVERT=true
TBR=amineer@chromium.org

Change-Id: I68c759b8cb4d6672e58699454053481adf6c7afd
Reviewed-on: https://chromium-review.googlesource.com/1141273Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575941}

Tab focusing to notification control buttons was broken in
UnifiedSystemTray because UnifiedMessageCenterView did not implement the
same OnDidChangeFocus logic as MesageCenterView did.

TEST=manual
BUG=862506

Change-Id: Ide2d9e170ecefcc87db2d43b6d8d3b1042492374
Reviewed-on: https://chromium-review.googlesource.com/1132907Reviewed-by: Yoshiki Iguchi <yoshiki@chromium.org>
Commit-Queue: Tetsui Ohkubo <tetsui@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575940}

This patch changes ascent and descent from LayoutUnit to
integer, so that the use is consistent.

In future, we'll want to switch to LayoutUnit, but
inconsitent use is likely to be a source of problems
than to help the migration.

Bug: 636993
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: I81bb766eaf4579b50bbe1896e48018b3aea81c20
Reviewed-on: https://chromium-review.googlesource.com/1075909
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575939}

When we set compositor_will_send_main_frame_not_expected flag when no PageSchedulers exist, MainThreadSchedulerImpl::BeginMainFrameNotExpectedUntil() never gets called. This means that StartIdlePeriod rarely gets called and the idle tasks may not be executed for a long time.

After this CL, compositor_will_send_main_frame_not_expected will not be set when no PageSchedulers exist, so MainThreadSchedulerImpl will try calling RequestBeginMainFrameNotExpected next time.

Bug: 862589
Change-Id: I06f9c813df6cc7270269d9ffb3a01f24b9c911ce
Reviewed-on: https://chromium-review.googlesource.com/1134630
Commit-Queue: Keishi Hattori <keishi@chromium.org>
Reviewed-by: Sami Kyöstilä <skyostil@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575938}

Change-Id: Ie3ad5785f82ccafdbcc630a5a26423ecc0b6c4bc
Reviewed-on: https://chromium-review.googlesource.com/1137846
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Chris Mumford <cmumford@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575937}

https://chromium.googlesource.com/webm/libvpx.git/+log/829d1b2098b5..2c45cd174a95

$ git log 829d1b209..2c45cd174 --date=short --no-merges --format='%ad %ae %s'
2018-07-11 marpan vp9: Force hybrid_intra on scene change
2018-07-15 jingning Account for quantization effect in the tpl model
2018-07-16 jingning Assign estimate qp for overlay frame
2018-07-16 johannkoenig Revert "Enable tpl model for speed 0"
2018-07-13 jingning Use the estimate qp to set motion search control
2018-07-13 jingning Set the estimate frame qp in tpl_frame
2018-07-13 jingning Estimate the frame qp in a gop
2018-07-12 marpan vp9: Enforce intra search on scene_change
2018-07-12 jingning Refactor rc_pick_q_and_bounds_two_pass parameters
2018-07-11 wtc Backport libaom bug fixes.
2018-07-12 jingning Enable tpl model for speed 0
2018-07-12 jingning Use regular filter type for tpl model motion compensation
2018-07-11 jingning Clean up mc_flow_dispenser()
2018-07-09 jingning Add 32x32 Hadamard transform
2018-07-10 jingning Relax multiplier adjustment limit
2018-07-06 jingning Change the tpl model operating block size to 32x32
2018-07-06 paulwilkins Delete invalid assert.

Created with:
  roll-dep src/third_party/libvpx/source/libvpx
R=johannkoenig@google.com

Change-Id: I2c82f58f662c09c00139f5bd62f13888a94c7956
Reviewed-on: https://chromium-review.googlesource.com/1140786Reviewed-by: Johann Koenig <johannkoenig@google.com>
Commit-Queue: Jerome Jiang <jianj@google.com>
Cr-Commit-Position: refs/heads/master@{#575936}

While investigating issue 794625, I noticed that it is possible for
RFHI::SwapOut to not actually create the proxy.  This happens if (1)
the RFHI to be swapped out is already pending deletion, and (2) the
RFHI to be swapped out is not live.  Nonetheless, the sole caller of
RFHI::SwapOut, RenderFrameHostManager::SwapOutOldFrame, assumes that a
replacement proxy is always created and unconditionally calls
proxy->set_render_frame_proxy_created(true) afterward.  This seems
wrong - instead, the proxy should be set to be live if the IPC to
create it was actually sent, which is what this CL does.

I can't pinpoint any specific issues this might lead to, so this is
more of a speculative/preventative fix for problems in this
area. There's a chance it might be related to issue 794625, though in
that issue, I'd expect the problem to be that we send a message to
create a proxy to a process where the proxy had already been created,
and here, the resulting problems would be from a proxy being marked
as live without actually having been created.

Bug: 794625
Change-Id: I7e3f53c17b541f9d5796714ef7c530a7955cf143
Reviewed-on: https://chromium-review.googlesource.com/1139215
Commit-Queue: Charlie Reis <creis@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575935}

This CL changes the non-DICE welcome page to a custom element in order
to reuse paper-button-style.

This CL also updates the win10 welcome page's paper-button to use
paper-button-style.

Bug: 860274
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: I8678e89fb99fda64c0e5f1f54b53f2edeb14e3a9
Reviewed-on: https://chromium-review.googlesource.com/1138984Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: Scott Chen <scottchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575934}

R=pwnall@chromium.org

Bug: 857464
Change-Id: I7f9206e1ac75c905ae35c44e44edfca0e8b82e0f
Reviewed-on: https://chromium-review.googlesource.com/1140518
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575933}

https://webrtc.googlesource.com/src.git/+log/dbdb3a00797d..0f5400acfa40


git log dbdb3a00797d..0f5400acfa40 --date=short --no-merges --format='%ad %ae %s'
2018-07-17 steveanton@webrtc.org [Unified Plan] Implement FiredDirection for RtpTransceiver


Created with:
  gclient setdep -r src/third_party/webrtc@0f5400acfa40

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

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng
TBR=webrtc-chromium-sheriffs-robots@google.com

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

Empty <input type=file> is represented incorrectly in FormData.
If there are no selected files, then append an entry to entry
list with name and a new File object with an empty name,
application/octet-stream as type, and an empty body [1].

[1] https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#constructing-form-data-set

Bug: 840714
Change-Id: Ifadade1e260e0314664549df2d35f0cd38c76bea
Reviewed-on: https://chromium-review.googlesource.com/1140236Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575931}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/3df683e6..65ea3e26

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

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

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_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;luci.chromium.try:android_optional_gpu_tests_rel

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

Change-Id: Ib0d8e2febefd2f3b42417184c8304859fc87bdb2
Reviewed-on: https://chromium-review.googlesource.com/1141089Reviewed-by: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#575930}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/82b059ecb6a4..1b00ba716473


git log 82b059ecb6a4..1b00ba716473 --date=short --no-merges --format='%ad %ae %s'
2018-07-17 dgarrett@google.com chrome_committer: Select service account per builder.


Created with:
  gclient setdep -r src/third_party/chromite@1b00ba716473

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: If19ec61c67987901f6ba8917e64fd971c4d0c128
Reviewed-on: https://chromium-review.googlesource.com/1141137Reviewed-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@{#575929}

If two parallel gethash requests are running and the first fails but the
second succeeds, then gethash error counters are reset and
next_gethash_time_ is not. In this case all following GetFullHashes
calls (until time is out) does not incur actual network requests and
gethash result is improperly reported as MIN_WAIT_DURATION_ERROR, even
though server did not sent min_wait_duration to the client.

Example steps (implemented in unit test):
- Initiate two separate full hash requests.
- Make the first request fail.
- Make the second request succeed.
- Call GetFullHashes method.
Expected result:
- As long as the second request was successful, the following requests
  are run as usual.
Actual Result:
- Network request is not issued.
- MIN_WAIT_DURATION_ERROR is reported to SafeBrowsing.V4GetHash.Result

Change-Id: Ieeb08046515f87239ec00d9ad13b80c257b59435
Reviewed-on: https://chromium-review.googlesource.com/1119908
Commit-Queue: Alexander Kalugin <akalugin@yandex-team.ru>
Reviewed-by: Varun Khaneja <vakh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575928}

Bug: 863093
Change-Id: I3307df10ca8c438c3683418f3e50c9e4859918bd
Reviewed-on: https://chromium-review.googlesource.com/1136530Reviewed-by: Dan Erat <derat@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575927}

These will be used in https://chromium-review.googlesource.com/c/chromium/src/+/1139108.

Bug: 851293
Change-Id: I246bae76d785bea6426bbe6a170272cebcdcc079
Reviewed-on: https://chromium-review.googlesource.com/1141120Reviewed-by: agrieve <agrieve@chromium.org>
Commit-Queue: Kristi Park <kristipark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575926}

https://chromium.googlesource.com/angle/angle.git/+log/252ec9191125..e2c00841a55f


git log 252ec9191125..e2c00841a55f --date=short --no-merges --format='%ad %ae %s'
2018-07-18 yizhou.jiang@intel.com GenerateMipmaps should generate INVALID_OPERATION in ES 2.0 with EXT_sRGB
2018-07-17 geofflang@chromium.org Vulkan: Expose an unimplemented EGL_ANGLE_robust_resource_initialization.


Created with:
  gclient setdep -r src/third_party/angle@e2c00841a55f

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

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
TBR=cwallez@chromium.org

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

Change-Id: I339695d5f7f2a733c09d5d19a167c7fa2ed02d35
Reviewed-on: https://chromium-review.googlesource.com/1140344Reviewed-by: Tatsuhisa Yamaguchi <yamaguchi@chromium.org>
Reviewed-by: calamity <calamity@chromium.org>
Commit-Queue: Joel Hockey <joelhockey@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575924}

We'd like to fix a confusing UI issue, and to know the impact
of a possible fix.

This relands #575575, which caused node leaks.
If a document is navigated out while a file chooser is opening,
ChromeClientImpl holded a strong reference to a FileInputType and the
whole document leaked.
This CL changes the reference from strong one to weak one.

Bug: 637639
Change-Id: I5dccade80e433ac53de4bb205abab58380b0a5f2
Reviewed-on: https://chromium-review.googlesource.com/1140339Reviewed-by: Keishi Hattori <keishi@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575923}

This CL moves RTL mirroring logic out of FrameHeader::GetTitleBounds() and
closer to where it's necessary. This fixes uses of GetTitleBounds() that
shouldn't use mirrored coordinates.

Before: https://bugs.chromium.org/p/chromium/issues/attachment?aid=347205&signed_aid=BHR4RQzcQgoqMRZiktSbrA==&inline=1
After: https://bugs.chromium.org/p/chromium/issues/attachment?aid=347206&signed_aid=_yNGcCCrQWXCWUB5bjJwSQ==&inline=1

Bug: 860590
Change-Id: Ie58194b4cf5e397967bf376d368146f180e7220e
Reviewed-on: https://chromium-review.googlesource.com/1127212
Commit-Queue: Alan Cutter <alancutter@chromium.org>
Reviewed-by: Jungshik Shin <jshin@chromium.org>
Reviewed-by: Dan Erat <derat@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575922}

R=nektar@chromium.org,dmazzoni@chromium.org

Bug: 847971
Change-Id: Id18111cedd06a6c5964682e114de03fc9c0d9567
Reviewed-on: https://chromium-review.googlesource.com/1130161Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Commit-Queue: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575921}

It wasn't used since inception in commit 292a9172.

Change-Id: Ib64e6f70a1779a6710dfcabb989089f3f598d8a7
Reviewed-on: https://chromium-review.googlesource.com/1126180
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575920}

An implementation of BackgroundFetchDelegate has been provided to
content shell which enables Background Fetches, without UI, to finish.
It uses the Download Service through a new dependency. This dependency
will be removed once the Download Service has been servicified, as
//content can depend on it directly from that point forward.

In context of the WPT tests, additional machinery has been added to
enable communication with the Service Worker, required for it to tell
the test about the result of the various Background Fetch events. The
"fetch.https.window.js" file now verifies the behaviour and results
of a single fetched file.

Bug: 864561

Change-Id: If53e6755ae8ea924712f5bdace4df4f658bc53d7
Reviewed-on: https://chromium-review.googlesource.com/1135536
Commit-Queue: Peter Beverloo <peter@chromium.org>
Reviewed-by: Xing Liu <xingliu@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575919}

This CL adds the checks_only flag to JS Closure Compilations that are only
doing type checking to improve build time.

Before:
5869.41s user 189.50s system 3350% cpu
5861.34s user 190.37s system 3284% cpu

After:
4143.98s user 159.46s system 3020% cpu
4184.40s user 158.95s system 3073% cpu

Bug: 632206
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: I68ebdce5a4cf98176d3f55b971e33fc62848d2d4
Reviewed-on: https://chromium-review.googlesource.com/1139840Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: calamity <calamity@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575918}

https://pdfium.googlesource.com/pdfium.git/+log/d563855ac72b..8e0c0dbc4876


git log d563855ac72b..8e0c0dbc4876 --date=short --no-merges --format='%ad %ae %s'
2018-07-17 asweintraub@google.com Add Deleter and Scoper for FPDF_PAGELINK.
2018-07-17 hnakashima@chromium.org Limit recursion depth for CXFA_DocumentParser::NormalLoader().


Created with:
  gclient setdep -r src/third_party/pdfium@8e0c0dbc4876

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:849143
TBR=dsinclair@chromium.org

Change-Id: I690589dba2241ff7f211a6c753a0ed74c57bd0a3
Reviewed-on: https://chromium-review.googlesource.com/1140539Reviewed-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@{#575917}

The URL path, parameters, etc. (LOCATION_BAR_TEXT_DIMMED)
were being lightened to GG700 but now get GG600 per spec.
The RESULTS_ICON and RESULTS_TEXT_DIMMED using the same
colors remain intact.

Bug: 863474
Change-Id: I1dc2efb763642d88cbc27d832b0411a10c3310c8
Reviewed-on: https://chromium-review.googlesource.com/1141294
Commit-Queue: Orin Jaworski <orinj@chromium.org>
Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575916}

Prefer signing smaller SHA-2 hashes over larger ones. This aligns with
BoringSSL's current defaults. In particular, we got a report of problems
with TPM-protected client certificates on Windows that cannot sign
SHA-512. Absent a way to reliably query hash preferences, SHA-256 is
more likely to be compatible.

Bug: 863147
Change-Id: Icaef85a2639ba3cc95846ff932bd829226e7aa7b
Reviewed-on: https://chromium-review.googlesource.com/1135299Reviewed-by: Steven Valdez <svaldez@chromium.org>
Commit-Queue: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575915}

Rename the load flag LOAD_DISABLE_CONNECTION_MIGRATION_TO_CELLULAR to LOAD_DISABLE_CONNECTION_MIGRATION_TO_CELLULAR.

This CL does not change the behavior of the flag, it merely renames the flag to reflect the semantics we would like it to have. A subsequent CL will make the behavior changes.

Bug: 769526
Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I6261e60fb44661a9b3de944e8f87bd660caeb761
Reviewed-on: https://chromium-review.googlesource.com/1136972
Commit-Queue: Zhongyi Shi <zhongyi@chromium.org>
Reviewed-by: Ryan Hamilton <rch@chromium.org>
Reviewed-by: Misha Efimov <mef@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575914}

I add this every time I'm debugging an a11y issue, let's save me and
everyone else some time :)

Change-Id: I12ee9d4bfb320f5da067d63f038d1f4d393975ce
Reviewed-on: https://chromium-review.googlesource.com/1131572
Commit-Queue: Nektarios Paisios <nektar@chromium.org>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575913}

FrameTaskQueueController creates and manages the task queues used by
FrameSchedulerImpl. It is responsible for tracking the mappings from
QueueTraits to MainThreadTaskQueues.

This CL adds FrameTaskQueueController and basic task queue management.
Refactoring FrameSchedulerImpl to use this new class will be added in
a follow-up CL.

Design Doc:
https://docs.google.com/document/d/1Jm4xLPqv013VfZswgmnoQ7-ghJK92Uf3hIT7WcNcFck/edit?usp=sharing

Bug: 859963
Change-Id: Ie9fefaaad83c30f06a13c427e38d54089fc362a4
Reviewed-on: https://chromium-review.googlesource.com/1132691
Commit-Queue: Scott Haseley <shaseley@google.com>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575912}

environmentIntegration is the new flag, which is now queried when
requesting sessions.  Plumbing to the browser process will happen in
a followup.

Now that both AR and VR can be supported simultaneously in tests,
WebXRHitTest is made experimental and the ar_hittest layout test passes.

BUG=828321

Change-Id: I4d8f13cc7c836c608d1f4d69d07813d163cea18f
Reviewed-on: https://chromium-review.googlesource.com/1132427
Commit-Queue: Bill Orr <billorr@chromium.org>
Reviewed-by: David Dorwin <ddorwin@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Reviewed-by: Ian Vollick <vollick@chromium.org>
Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575911}