GitLab

Remove references to shadow stacks from the profiling documentation and
from the shutdown signal handler.
The only remaining references are in the old tcmalloc implementation, which
will eventually be removed.

BUG=724399,b:70905156

Change-Id: I2b1a854dc2eb081ec9bfb5401fc2c5ebd1860c4e
Reviewed-on: https://chromium-review.googlesource.com/1239442Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Alexander Potapenko <glider@chromium.org>
Reviewed-by: Will Harris <wfh@chromium.org>
Commit-Queue: Gabriel Marin <gmx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593639}

This reverts commit 95797d79.

Reason for revert: will limit the workaround to AMD gpus only, so we could merge back to Beta affecting less machines.

Original change's description:
> Disable DirectComposition on everywhere except for Intel GPUs
> 
> We only need it if hardware overlays can be used.
> 
> BUG=800950
> TEST=bots
> R=​sunnyps@chromium.org
> 
> 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: Id1a00799ee77f942183b55327ba21c7af65165b5
> Reviewed-on: https://chromium-review.googlesource.com/1232153
> Commit-Queue: Zhenyao Mo <zmo@chromium.org>
> Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#592267}

TBR=zmo@chromium.org,sunnyps@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 800950
Change-Id: I8bfe7d77c40a6754577719f853a3df4baf508d09
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
Reviewed-on: https://chromium-review.googlesource.com/1240509Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: Zhenyao Mo <zmo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593638}

This CL uses ScopedBlockingCall to mark blocking calls in /chrome/browser/extensions/api/storage.

This CL was created by replacing calls to AssertBlockingAllowed()
with instantiations of ScopedBlockingCall(MAY_BLOCK).
I kindly ask the reviewer to make sure of the following:
  - ScopedBlockingCall is instantiated in a scope with minimal CPU usage.
    If this is not the case, ScopedBlockingCall should be instantiated
    closer to the blocking call. See scoped_blocking_call.h for more
    info. Please let me know when/where the blocking call happens if this needs
    to be changed.
  - Parameter |blocking_type| matches expectation (MAY_BLOCK/WILL_BLOCK). See
    BlockingType for more info. While I assumed MAY_BLOCK by default, that might
    not be the best fit if we know that this callsite is guaranteed to block.
  - The ScopedBlockingCall's scope covers the entirety of the blocking operation
    previously asserted against by the AssertBlockingAllowed().

This CL was uploaded by git cl split.

R=rdevlin.cronin@chromium.org

Bug: 874080
Change-Id: I4de4dd7b51419500492ecce093c5e82cd9fe6b35
Reviewed-on: https://chromium-review.googlesource.com/1191809Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593637}

Bug: 880973
Change-Id: I905435107c3568d6e9f6c8eaf4c5fc9ec1173746
Reviewed-on: https://chromium-review.googlesource.com/1239622
Commit-Queue: Stephen Martinis <martiniss@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593636}

This was mistakenly added in crrev/c/1228308.

Bug: 888659
Change-Id: I949e02e39a3a3650fecbb464d7e2b7ea1b14eddc
Reviewed-on: https://chromium-review.googlesource.com/1240859Reviewed-by: agrieve <agrieve@chromium.org>
Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593635}

+ Record dialog dismissal on Android side as kDialogClosed
+ Add metrics recording support for modal dialogs, and remove onCancel
  callback

Bug: 873236
Change-Id: Idbe990f2c70883f851bf5214dbf0a3e7b96f4260
Reviewed-on: https://chromium-review.googlesource.com/1222990Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Becky Zhou <huayinz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593634}

aura::Env::GetInstance() means the Env in the client in
SingleProcessMash, which means this PreTargetHandler might not
be invoked in SingleProcessMash.

This is primarily for fixing test failures of BookmarkBarViewTest
and MenuItemViewTestRemoveWithSubmenu in interactive_ui_tests,
but I guess this will fix some keyboard operations on menu
items in normal chrome.

Bug: 883523
Test: interactive_ui_tests --enable-features=SingleProcessMash
Change-Id: I4f081b290bf6468318df3a77844efaf8410d05b7
Reviewed-on: https://chromium-review.googlesource.com/1237540
Commit-Queue: Jun Mukai <mukai@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593633}

https://android.googlesource.com/platform/external/perfetto.git/+log/e2ea26c8b521..80983c737e5b


git log e2ea26c8b521..80983c737e5b --date=short --no-merges --format='%ad %ae %s'
2018-09-24 lalitm@google.com Merge changes I8aec6ee1,I25f017c0,I4e49a5f0,Ie794521a,I22340a55, ...
2018-09-24 gkaiser@google.com trace_processor: Fix deallocation mismatch


Created with:
  gclient setdep -r src/third_party/perfetto@80983c737e5b

The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-chromium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=perfetto-bugs@google.com

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

PointerWatchers aren't necessary in ash anymore. ui::EventHandler does
everything that PointerWatcher can do, plus can mutate events. Once
we eliminate PointerWatcher from ash we can delete some glue code I
added to make them work.

Also drop support for ui::EventPointerType::POINTER_TYPE_UNKNOWN,
which is never recorded in practice. (I don't think we ever generate
events with this type.)

Bug: 872450, 786214
Test: ash_unittests
Change-Id: I08f781dd6e26b34870e7947c3a14e42edaf91080
Reviewed-on: https://chromium-review.googlesource.com/1239455Reviewed-by: Xiaoyin Hu <xiaoyinh@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593631}

Bug: 888225
Change-Id: Ife7943d9e409c9cb6441ad8b83046de14ad1a3ca
No-Try: true
Tbr: jbroman@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/1241093Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593630}

From the stack traces for this bug, it looks like we're trying to access
an optional value that isn't set. While we investigate why this is
happening, let's explicitly check the value exists before accessing.

Bug: 888143
Change-Id: Ifc1e47cc26e601c450f70b07dc37e764f6543802
Reviewed-on: https://chromium-review.googlesource.com/1240129Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Commit-Queue: James MacLean <wjmaclean@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593629}

These were added for deprecated Mash architecture plans.
Inline calls to [Add/Remove]PreTargetHandler instead.

Bug: 866529
Test: No shelf tooltip nor double-click-to-resize-window changes.
Change-Id: Ic4d376652e1e128c979cfdb6f5f219a2ed76f6ad
Reviewed-on: https://chromium-review.googlesource.com/1240212Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593628}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/d786acd3..3e22586a

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: I7cc513be0fa5ea1955573ca6077f9ea48b062c0b
Reviewed-on: https://chromium-review.googlesource.com/1240207Reviewed-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@{#593627}

Because: https://wicg.github.io/origin-policy/#monkey-patching-fetch, 3.4.2 #8

This addresses deferred feedback from https://crrev.com/c/1148395

Bug: 751996
Change-Id: Iac7756bf7c6b126711f002fd94b82bfd5fcae522
Reviewed-on: https://chromium-review.googlesource.com/1221146
Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593626}

This change sets up the ImageLoader to be backed by the
haredImageCache when it becomes available. In the short term, this
change all fixes the order the urls are tried such that we strictly
respect the order provided by the Feed. One downside is that more JNI
calls are made.

Bug: 840578
Change-Id: Ie3309005c995ff9e800add44de6e189752722b78
Reviewed-on: https://chromium-review.googlesource.com/1237333Reviewed-by: Filip Gorski <fgorski@chromium.org>
Reviewed-by: Gang Wu <gangwu@chromium.org>
Commit-Queue: Sky Malice <skym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593625}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/43650198eae8..96954b704ff5


Created with:
  gclient setdep -r src-internal@96954b704ff5

The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=mmoss@chromium.org

Change-Id: I888ae43cdbbea3b7fba713172443dfc85f0a429a
Reviewed-on: https://chromium-review.googlesource.com/1240533Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#593624}

Split raster PDF creation into its own function. Also add a helper
function to consistently check for PDFs with no pages.

Change-Id: I693282460b4da0e80bd1c5f2c022372bb7d58bb1
Reviewed-on: https://chromium-review.googlesource.com/1238353
Commit-Queue: Lei Zhang <thestig@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593623}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/baf09271514c..8bdc1b8a0433


git log baf09271514c..8bdc1b8a0433 --date=short --no-merges --format='%ad %ae %s'
2018-09-24 tandrii@chromium.org my_activity: add --completed-issues option.


Created with:
  gclient setdep -r src/third_party/depot_tools@8bdc1b8a0433

The AutoRoll server is located here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=agable@chromium.org

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

This CL removes the min-height CSS properties for audio elements and
video elements acting as audio elements. We had these rules to handle
the width/height-zero elements in the MediaDocument, but we have
changed how the MediaDocument sizing works, so they're no longer
needed.

Bug: 842900
Change-Id: I050aba4786f84754843ee611ead1dabe220381cb
Reviewed-on: https://chromium-review.googlesource.com/1239725Reviewed-by: Becca Hughes <beccahughes@chromium.org>
Commit-Queue: Tommy Steimel <steimel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593621}

These are modelled after the similar tests that exist for AnimationEvent
in css/css-animations, except written using more modern WPT style.

Bug: 695504
Change-Id: I63573cf48aba6821f5e22486ef18217d0f2828ee
Reviewed-on: https://chromium-review.googlesource.com/1239457Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593620}

We shouldn't propagate keydown events so that it can
behave modally.

Bug: 883221
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: I4aa5257b4bf6c417123d659ba911cb01641a4cc7
Reviewed-on: https://chromium-review.googlesource.com/1230493Reviewed-by: Scott Chen <scottchen@chromium.org>
Commit-Queue: Sang Woo Ko <sangwoo108@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593619}

BUG=867155
TEST=manual
R=kbr@chromium.org

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: Idafc99cf9a486cc23751eff36084d63115b5d87f
Reviewed-on: https://chromium-review.googlesource.com/1239733Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Zhenyao Mo <zmo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593618}

The policies don't exist on ChromeOS, and the 'enterprise default' only
applies to ChromeOS. This caused policies to get set, and appear in
`about:policy`, even though they were not supported on that platform.

Bug: 882533
Change-Id: Ibc17dc4254812fb39048d97ea4b6e45dae7f4380
Reviewed-on: https://chromium-review.googlesource.com/1240494Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Commit-Queue: Nicolas Ouellet-Payeur <nicolaso@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593617}

In order to disable the keyboard accessory within the contextual search
panel,the ManualFillingMediator calls isSearchPanelOpened() on the
ContextualSearchManager that it gets from the acivity. Since the
contextual search manager can be null, a check is required prior
to calling that method.

Bug: 887833
Change-Id: I85203cbb233a2ae7eec8a008ebd63c40bbd1a170
Reviewed-on: https://chromium-review.googlesource.com/1238473Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Commit-Queue: Ioana Pandele <ioanap@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593616}

The work done in crbug.com/833380 to address flakiness in
SitePerProcessHitTestBrowserTests likely resolves the source of flakiness
for this test.

Bug: 833380
Change-Id: Idd54686f2ad3294ae9daca4faf43945dc428afb0
Reviewed-on: https://chromium-review.googlesource.com/1236835Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593615}

Adds a WasActivatedOption to allow embedders to override the
`was_activated` logic for browser initiated navigations.

This is for when a user activation occurs on a surface outside
of the page and we want this to be passed to a navigation as if
this had occured on a previous page.

BUG=884777

Change-Id: Ifc7ce9352c3736d9e5c5c7d6909b3c5b2ead0cd8
Reviewed-on: https://chromium-review.googlesource.com/1228502Reviewed-by: Camille Lamy <clamy@chromium.org>
Reviewed-by: Greg Kerr <kerrnel@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Commit-Queue: Becca Hughes <beccahughes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593614}

With the new v8 interface for externalizing array buffer contents, we
no longer need to store the kind or allocation_base/size on the blink
side. Hence, this change removes those fields completely.

Furthermore, gin now also uses the custom deleter based interface.

Change-Id: Ifa1a1900e83e7f9fab859672edc8fe54ad7e647e
Reviewed-on: https://chromium-review.googlesource.com/1235937Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Commit-Queue: Stephan Herhut <herhut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593613}

Bug: chromedriver:2016
Change-Id: I9a5d54fdec6b8750d9893382c927435ad1200ae6
Reviewed-on: https://chromium-review.googlesource.com/1240196Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: Tatiana Buldina <buldina@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593612}

Bug: 887404
Change-Id: Ice13eb0166da5590170e7cc7d152d58ee64f0248
Reviewed-on: https://chromium-review.googlesource.com/1235938Reviewed-by: Jun Choi <hongjunchoi@chromium.org>
Commit-Queue: Balazs Engedy <engedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593611}

This CL updates the milestone selection page. Details:
* Add small drop-down to select between "compare" or "view" mode.
  "Compare" is the old behavior, and "view" shows only one select box.
* Under view mode, clicking "Open report" will open report to view
  single milestone.
* Opened report now appears on new tab.
* For "compare" mode with incompatible changes (version 1 equal or newer
  than version 2): Old behavior of graying out options was non-robust.
  This is repalced with disabling "Open report" button and showing error
  message.
* Extra change: generate_milestone_report.py: Correct gsutil.py rsync
  parameter.

Bug: 880671
Change-Id: Ie3c1e23c2f78ea4818f86f71954cf3ece0bea513
Reviewed-on: https://chromium-review.googlesource.com/1240503
Commit-Queue: Samuel Huang <huangs@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Reviewed-by: Samuel Huang <huangs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593610}

https://chromium.googlesource.com/webm/libvpx.git/+log/282087a14c84..3448987ab20a

$ git log 282087a14..3448987ab --date=short --no-merges --format='%ad %ae %s'
2018-09-22 jzern Revert "Revert "Revert "Loopfilter MultiThread Optimization"""
2018-09-21 johannkoenig Revert "third_party/googletest: update to v1.8.1"
2018-09-20 theonetruecamper better-hw-compatibility: fix out of bounds access
2018-09-21 jianj vp8: exit with bad fragment size in decoder.
2018-09-21 jingning Rework is_compound_allowed logic at encoder
2018-09-21 theonetruecamper internal stats: fix mem leak and initialize memory
2018-09-21 theonetruecamper sanitizer: fix unaligned loads
2018-09-20 angiebird Use different corner detection score
2018-09-17 johann.koenig third_party/googletest: update to v1.8.1
2018-09-20 jingning Generalize encoder comp_var_ref setting
2018-09-18 jingning Skip checking compound modes with same sign bias for sub8x8
2018-09-18 jingning Update the comp_refs counts
2018-09-18 jingning Skip RD check for compound modes that have same sign bias
2018-09-18 jingning Sync ref frame writing with decoder
2018-09-18 jingning Add frame_start/end to gf_group

Created with:
  roll-dep src/third_party/libvpx/source/libvpx
R=johannkoenig@chromium.org, tomfinegan@chromium.org

Bug: webm:1562
Change-Id: I3225512a15061b4f456b3a969a4a23a9cdf18b0d
Reviewed-on: https://chromium-review.googlesource.com/1239993Reviewed-by: Johann Koenig <johannkoenig@google.com>
Commit-Queue: James Zern <jzern@google.com>
Cr-Commit-Position: refs/heads/master@{#593609}

Bug: 832676
Change-Id: If732ef321da1a440003906763d5c8c64b3d4ba5f
Reviewed-on: https://chromium-review.googlesource.com/1239637Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593608}

A subsequent CL will plumb this out to the chrome://discards page.

Bug: 874968
Change-Id: I18496f73a4a76cfe05151b67fb7cce4d9e256064
Reviewed-on: https://chromium-review.googlesource.com/1239002
Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org>
Reviewed-by: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593607}

https://pdfium.googlesource.com/pdfium.git/+log/e65756725f82..97f4483de007


git log e65756725f82..97f4483de007 --date=short --no-merges --format='%ad %ae %s'
2018-09-24 hnakashima@chromium.org Revert "Make potentially dangerous Actions require a user click."
2018-09-22 thestig@chromium.org Remove useless charset data in CFGAS_FontMgr.
2018-09-22 thestig@chromium.org Roll build/ f53effa79..dfca77bb0 (53 commits)
2018-09-22 thestig@chromium.org Move some CFGAS_FontMgr methods into an anonymous namespace.
2018-09-22 thestig@chromium.org Change CBC_QRCoderMatrixUtil::BuildMatrix() to return a bool.
2018-09-22 thestig@chromium.org Encapsulate CBC_QRCoderMatrixUtil code.
2018-09-22 thestig@chromium.org Remove CBC_CommonByteArray and CBC_QRCoderBlockPair.
2018-09-21 npm@chromium.org Cleanup in CCodec_FaxModule
2018-09-21 tsepez@chromium.org Replace CPDF_Color::Copy() with honest-to-goodness operator=().
2018-09-21 npm@chromium.org Make OutputIndex() a void method
2018-09-21 thestig@chromium.org Fix destruction order with CPDF_StreamAcc.
2018-09-21 thestig@chromium.org Remove unreachable code in CPDF_DIBBase.
2018-09-21 thestig@chromium.org Validate more image values in CPDF_DIBBase.
2018-09-20 hnakashima@chromium.org Make potentially dangerous Actions require a user click.


Created with:
  gclient setdep -r src/third_party/pdfium@97f4483de007

The AutoRoll server is located here: https://autoroll.skia.org/r/pdfium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.



BUG=chromium:851821,chromium:887626,chromium:851821
TBR=dsinclair@chromium.org

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

Bug: 888634
Change-Id: I81df8a179f925e6dcb07bbdec118f407f3395567
No-Try: true
Tbr: jbroman@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/1240520Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593605}

Use wtf_size_t when dealing with WTF types.

BUG=879657

Change-Id: I7c36518c6b88f5d8b8b3ea3f90551eed3177d85a
Reviewed-on: https://chromium-review.googlesource.com/1240496Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593604}

Currently fingerprint attempts are not treated as user activities.
So when the screen is off, user touch the sensor with an enrolled finger
will silently unlock the screen, with the screen remains off.
And after hitting a key, the screen turns on and already unlocked which
makes user think the screen is never locked.

This CL reports fingerprint attempts as user activity so when user touch
the sensor, the screen will be turned on.


Bug: b:115779078
Change-Id: I10acd8cc3eccb7d594465573fecf9f3099a65f8d
Reviewed-on: https://chromium-review.googlesource.com/1236556
Commit-Queue: Xiaoyin Hu <xiaoyinh@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Dan Erat <derat@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593603}

- Changes the option displayed in the files app "add new services menu"
from"SMB Shares" to "SMB file share"

Bug: chromium:887132
Change-Id: I066e36e1ec992dce40971eced993b9aea5a0b7c8
Reviewed-on: https://chromium-review.googlesource.com/1239213Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Commit-Queue: Bailey Berro <baileyberro@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593602}

The interface RenderWidgetHostNSViewLocalClient provides a set of helper
functions that add functionality to a RenderWidgetHostNSViewClient.
These functions may be implemented directly using that Client, or using
a side-channel.

The naming of this class is very confusing as we add the ability to have
local (in-process) and remote (out-of-process) clients. To this end,
rename this to a name that more closely mirrors the names in ui/views
and doesn't these naming ambiguities.

Move the ForwardingLocalClient from render_widget_host_view_cocoa.mm
over to a new render_widget_host_ns_view_client_helper.mm. Change
the instance which is created as a dummy pipe to always be identified
as a dummy pipe.

Bug: 821651
Change-Id: I1dd130ddbed46d4854a065fa3d629b7f9833824c
Reviewed-on: https://chromium-review.googlesource.com/1239641Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593601}

Bug: 884062
Change-Id: I584dda328551a10db2100d493e802f42da83c1e5
Reviewed-on: https://chromium-review.googlesource.com/1237262
Commit-Queue: Ryan Meier <rameier@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593600}