- 10 Feb, 2018 40 commits
-
-
Charles Harrison authored
The CL also adds a microsecond histogram to the call, to see how often we'd get above the 10ms threshold in practice. A similar histogram exists (SubresourceFilter.SafeBrowsing.CheckDispatchTime), but it is only called for SubresourceFilter safe browsing checks on main frame navigations. Bug: 806981 Change-Id: If63590a4f543a1e65760ee5c7f35d8bc773cef10 Reviewed-on: https://chromium-review.googlesource.com/911750 Commit-Queue: Charlie Harrison <csharrison@chromium.org> Reviewed-by:
Varun Khaneja <vakh@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#535954}
-
Ken Rockot authored
TBR=dcheng@chromium.org TBR=jam@chromium.org Bug: 806965 Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs Change-Id: Ifb8c81ad55ebef52a93cff1f85a1d6e125fd4224 Reviewed-on: https://chromium-review.googlesource.com/912313 Commit-Queue: Ken Rockot <rockot@chromium.org> Reviewed-by:
Ken Rockot <rockot@chromium.org> Cr-Commit-Position: refs/heads/master@{#535953}
-
https://skia.googlesource.com/skia.git/+log/308150821517..0a5f99ccdfa6 $ git log 308150821..0a5f99ccd --date=short --no-merges --format='%ad %ae %s' 2018-02-09 reed can't cheat on contains due to underflow 2018-02-09 angle-skia-autoroll Roll skia/third_party/externals/angle2/ 3e520b6f4..6108b766b (4 commits) Created with: roll-dep src/third_party/skia BUG=810411 The AutoRoll server is located here: https://autoroll.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=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel TBR=bsalomon@chromium.org Change-Id: I30dd6ced4cc5d8519df8624b55b6a7171495e5d1 Reviewed-on: https://chromium-review.googlesource.com/912756 Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#535952}
-
Sidney San Martín authored
- Like a Cocoa build, the work is done by a custom frame view class. - MacViews browser will target macOS 10.10+, so don't bother emulating NSFullSizeContentViewWindowMask or positioning the full screen button. (There's one @available guard because Chrome's deployment target is still 10.9). Bug: 737957 Change-Id: I6b9a848b750c3fda5a7b172da8f7b78d5e2b033d Reviewed-on: https://chromium-review.googlesource.com/912628 Commit-Queue: Sidney San Martín <sdy@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#535951}
-
https://webrtc.googlesource.com/src.git/+log/2b67f5c65f7a..8acdd1a1dc9f $ git log 2b67f5c65..8acdd1a1d --date=short --no-merges --format='%ad %ae %s' Created with: roll-dep src/third_party/webrtc BUG=none,None,None,None 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=master.tryserver.chromium.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng;master.tryserver.chromium.win:win-msvc-dbg TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I09b055d8ba5bb89bc28c95a78cdacb6a52b70e0a Reviewed-on: https://chromium-review.googlesource.com/912278Reviewed-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@{#535950}
-
Noel Gordon authored
Bug: 796178 Change-Id: I3850e783f79a70ea13d275875fa77ae35faa06ba Reviewed-on: https://chromium-review.googlesource.com/911228Reviewed-by:
Chris Blume <cblume@chromium.org> Commit-Queue: Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#535949}
-
Alexei Filippov authored
BUG=803276 Change-Id: I296f73a684ba291cc26570a91afd9ced100c43fb Reviewed-on: https://chromium-review.googlesource.com/911876Reviewed-by:
Pavel Feldman <pfeldman@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Alexei Filippov <alph@chromium.org> Cr-Commit-Position: refs/heads/master@{#535948}
-
Sergey Ulanov authored
Bug: 778467 Change-Id: I4d5c662915b34237f706abdccd110748f1dbabcc Reviewed-on: https://chromium-review.googlesource.com/912669Reviewed-by:
Antoine Labour <piman@chromium.org> Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> Cr-Commit-Position: refs/heads/master@{#535947}
-
Steve Kobes authored
Clamping the root PLSA should be done after the FrameView is resized, because the size of the FrameView determines the scroll bounds of the layout viewport (through LayoutView::OverflowClipRect). This fixes two symptoms: - incorrect initial scroll offset on Android, where the FrameView's width at construction time is the 980px layout fallback width - failure to preserve scroll offset during window resize on desktop, since the clamping was based on the previous size Bug: 807987 Change-Id: I6a6d2a25879fe8e89d3e1d6b958b3e6754c0108e Reviewed-on: https://chromium-review.googlesource.com/911946Reviewed-by:
David Bokan <bokan@chromium.org> Commit-Queue: Steve Kobes <skobes@chromium.org> Cr-Commit-Position: refs/heads/master@{#535946}
-
Michael Giuffrida authored
Removes some unused arguments, corrects comments, fixes up includes Change-Id: I908530b5c827c611eafb4403a6e674d25a28414b Reviewed-on: https://chromium-review.googlesource.com/912275Reviewed-by:
Karan Bhatia <karandeepb@chromium.org> Commit-Queue: Michael Giuffrida <michaelpg@chromium.org> Cr-Commit-Position: refs/heads/master@{#535945}
-
Victor Miura authored
BUG=799458 Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Change-Id: Ib2898c97168b164c718dcc3c0303950c4c271659 Reviewed-on: https://chromium-review.googlesource.com/852639Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
-
https://skia.googlesource.com/skia.git/+log/549de6c21d07..308150821517 $ git log 549de6c21..308150821 --date=short --no-merges --format='%ad %ae %s' 2018-02-09 egdaniel Remove unused code resulted from deleting DeferredTextureImage 2018-02-09 bsalomon Move default init of tmp draw params out of subclasses into GrGpu 2018-02-09 reed add helper to know when a colortype is always opaque 2018-02-09 halcanary BUILD: link and solink uses rsp file 2018-02-09 skcms-skia-autoroll Roll skia/third_party/externals/skcms/ 88dee8ac3..3dec63698 (1 commit) 2018-02-09 rmistry [Android Compile Bot] Print every minute 2018-01-03 mtklein yet another approach to unpremul scale pixels 2018-02-09 bungeman Fix api METADATA json. 2018-02-07 halcanary Android Tools: build x86_64 correctly. 2018-02-09 reed move a bunch of helpers from SkImageInfo.h into priv 2018-02-09 mtklein Revert "alternate approach to unpremul scalePixels()" 2018-02-09 halcanary SkShaper: make build target 2018-02-09 robertphillips Re-enable explicit GPU resource allocation 2018-02-09 benjaminwagner Upgrade Mac bots. 2018-02-08 bungeman Order the API reference. 2018-02-09 fmalita [skottie] Fix viewer slide sizing on Android 2018-02-09 robertphillips Make atlases instantiate themselves at flush time 2018-02-09 skcms-skia-autoroll Roll skia/third_party/externals/skcms/ 5884a65a6..88dee8ac3 (1 commit) 2018-02-09 halcanary Documentation Fixes: Viewer on Android needs SDK 2018-02-09 benjaminwagner Add CPU dimension for MacMini7.1. 2018-02-09 egdaniel When querying mipmapped on proxies return targets state if possible 2018-02-09 bsalomon Track dirty rects on GrRenderTargets in native space rather than origin-relative 2018-02-08 benjaminwagner Add MacBook10,1 jobs. 2018-02-09 brianosman Create sksl_enums.inc with UNIX line endings (even on Windows) 2018-02-09 brianosman Remove (unused) NV_bindless_texture from GL interface 2018-02-09 brianosman Add missing include (to get std::min on MSVC) 2018-02-08 kjlubick Break some fuzzer targets out so oss-fuzz can use them 2018-02-09 bsalomon Revert "Revert "Remove SkImage deferred texture image data APIs."" 2018-01-03 mtklein alternate approach to unpremul scalePixels() 2018-02-08 brianosman Remove EXT_direct_state_access (unused) Created with: roll-dep src/third_party/skia The AutoRoll server is located here: https://autoroll.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=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel TBR=bsalomon@chromium.org Change-Id: I2accacdd1ea210101e5955deca88cc0c68fe5c12 Reviewed-on: https://chromium-review.googlesource.com/912668 Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
-
v8-autoroll authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/68fdc80c..3331abf8 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;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org Change-Id: I9897e9b773c99fe1fe8f55c84e15a09d3e93498e Reviewed-on: https://chromium-review.googlesource.com/912569Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#535942}
-
Esmael El-Moslimany authored
Regardless of which "On startup" radio option is selected, always show ntp extensions. This makes it easier to disable the ntp extension. R=dpapad@chromium.org, scottchen@chromium.org Bug: 798802 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: Icb50e9d1f563d11ccded31468ec8f145ea774d45 Reviewed-on: https://chromium-review.googlesource.com/912229 Commit-Queue: Esmael El-Moslimany <aee@chromium.org> Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Reviewed-by:
Scott Chen <scottchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#535941}
-
Xing Liu authored
Disable a flaky test. TBR=dtrainor@chromium.org Bug: 810982 Change-Id: I0ea6a3143392e2bda7fd9682a3c3af3e8fd70b09 Reviewed-on: https://chromium-review.googlesource.com/912552Reviewed-by:
Xing Liu <xingliu@chromium.org> Commit-Queue: Xing Liu <xingliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#535940}
-
https://chromium.googlesource.com/angle/angle.git/+log/617736404a62..8f27b0509264 $ git log 617736404..8f27b0509 --date=short --no-merges --format='%ad %ae %s' 2018-02-08 ynovikov Update Android build instructions 2018-02-08 ynovikov Remove angle::Library and its usages 2018-02-09 thakis Prepare for -Wimplicit-fallthrough in ANGLE. Created with: roll-dep src/third_party/angle 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=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel TBR=cwallez@chromium.org Change-Id: Ie536f6570441e9079f6444c45d5e3435e9c12765 Reviewed-on: https://chromium-review.googlesource.com/912612 Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#535939}
-
Tom Anderson authored
Glibc 2.27 introduced some new optimizations to several math functions, but it will be a while before it makes it into all supported distros. Luckily, glibc maintains ABI compatibility with previous versions, so the old symbols are still there. This CL modifies mathcalls.h so that the old version of the symbol is always used. Alternatives considered: 1. Add the __asm__ statements that this CL adds into libm_versioning.h and add "-include libm_versioning.h" to //build/config/linux:compiler. This path was not taken since it would add the new flags to every file in the build. 2. Create wrapper functions like __wrap_expf() that call to the glibc 2.2.5 expf(). Add the wrapper file to a source_set and make it a dependency of exe_and_shlib_deps. Add a config all_dependent_configs to set up the wrapper "-Wl,--wrap=expf". This was not done since it would add a new dependency to all executables and shared libraries. 3. Create our own math.h that has the __asm__ statements and "#include_next<math.h>". Add this to the beginning of the system search path. This was not done since it's basically a crappier version of (1). R=thestig Change-Id: I06b4ab0621592ed58563d10d566d49e3c017b880 Reviewed-on: https://chromium-review.googlesource.com/907794 Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#535938}
-
Tom Anderson authored
BUG=789768 R=dpranke@chromium.org Change-Id: Ic76ef362957eb017ac16f01cc53d04412c187373 Reviewed-on: https://chromium-review.googlesource.com/798631 Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Cr-Commit-Position: refs/heads/master@{#535937}
-
Chris Harrelson authored
This expectation regressed when turning on root layer scrolling. It was changed to the current value in this patch: https://chromium-review.googlesource.com/c/chromium/src/+/858299 Change-Id: Ic3efc1990da93bbb00ff3ab84236ee86cfd1db44 Reviewed-on: https://chromium-review.googlesource.com/912279Reviewed-by:
Steve Kobes <skobes@chromium.org> Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#535936}
-
bsheedy authored
This reverts commit eb57a3a3. Reason for revert: "Reland" button isn't working, so revert the revert Original change's description: > Revert "Deduplicate WebXR tests" > > This reverts commit 173bbfd7. > > Reason for revert: one of the new tests is failing on the chromium.gpu.fyi waterfall; see https://bugs.chromium.org/p/chromium/issues/detail?id=804043#c6 . > > Original change's description: > > Deduplicate WebXR tests > > > > Deduplicates most WebVR/WebXR tests into one test implementation that > > takes different arguments for WebVR and WebXR. > > > > Bug: 804043 > > Change-Id: I1486a4d8e75d91fe98c1298f3b528df4bc01d938 > > Reviewed-on: https://chromium-review.googlesource.com/896800 > > Commit-Queue: Brian Sheedy <bsheedy@chromium.org> > > Commit-Queue: Michael Thiessen <mthiesse@chromium.org> > > Reviewed-by: Michael Thiessen <mthiesse@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#533890} > > TBR=mthiesse@chromium.org,bsheedy@chromium.org > > # Not skipping CQ checks because original CL landed > 1 day ago. > > Bug: 804043 > Change-Id: I1ec02deb49bcdbb26940f95b80a9df45ba63d585 > Reviewed-on: https://chromium-review.googlesource.com/900463 > Reviewed-by: Kenneth Russell <kbr@chromium.org> > Commit-Queue: Kenneth Russell <kbr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#534248} # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 804043 Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_vr;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Change-Id: Ia0c62c6f826885c56ef6a0425ddd47677e17f8c2 Reviewed-on: https://chromium-review.googlesource.com/906839 Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Reviewed-by:
Yash Malik <ymalik@chromium.org> Reviewed-by:
Brian Sheedy <bsheedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#535935}
-
Bill Budge authored
This reverts commit cd23fc50. Reason for revert: Performance regression: https://bugs.chromium.org/p/chromium/issues/detail?id=809546 Original change's description: > [ArrayBuffer] Fix a data race when allocating array buffers. > > - The vector of partitions may iterated on one thread, while another > thread is mutating it. Use a mutex to prevent that. > > Bug: chromium:808427 > Change-Id: I4cfee3ad9adeeba6e108f8a79dd1ddef9c418de0 > Reviewed-on: https://chromium-review.googlesource.com/899778 > Reviewed-by: Kentaro Hara <haraken@chromium.org> > Commit-Queue: Bill Budge <bbudge@chromium.org> > Cr-Commit-Position: refs/heads/master@{#534532} TBR=bbudge@chromium.org,haraken@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: chromium:808427 Change-Id: I5ec463ac45afa88c4bf975cbe353e2a46b1dd8ea Reviewed-on: https://chromium-review.googlesource.com/912088Reviewed-by:
Bill Budge <bbudge@chromium.org> Reviewed-by:
-
Kinuko Yasuda authored
Moves: - client_hints/client_hints.h - device_memory/approximated_device_memory.h - feature_policy/feature_policy.h - message_port/message_port_channel.h - message_port/cloneable_message.h - message_port/transferable_message.h R=haraken@chromium.org,jam@chromium.org Bug: 809983 Change-Id: I5bde75652c26f3fdfc0f48ceb242aaa5c4cf7272 Reviewed-on: https://chromium-review.googlesource.com/910733Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Commit-Queue: Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#535933}
-
Zhongyi Shi authored
Bug: 650509 Change-Id: Ie5bb461a6094a33c50605a4735675b6552738b65 Reviewed-on: https://chromium-review.googlesource.com/898502Reviewed-by:
Ryan Hamilton <rch@chromium.org> Reviewed-by:
Nick Harper <nharper@chromium.org> Commit-Queue: Zhongyi Shi <zhongyi@chromium.org> Cr-Commit-Position: refs/heads/master@{#535932}
-
Chris Harrelson authored
When ancestors change their paint properties, the LocalBorderBoxProperties of a descendant can update. In SPv175 we need this to cause a repaint, because the descendant's paint chunks depend on the LocalBorderBoxProperties. This is only reproducible in SPv175 with a composited child layer, because otherwise a recursive setNeedsRepaint would apply during style update; that recursive update does not recurse into composited children. In SPv2 mode it should reproduce regardless. Bug: 810684 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: Ic2f7303cde077ff7ae3fdf078d7aac1901a1b25f Reviewed-on: https://chromium-review.googlesource.com/912458Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#535931}
-
Devlin Cronin authored
The externally_connectable entry in the manifest specifies which sites can message a given extension. By default, we require that these sites be listed at a somewhat specific level (we allow subdomains, but not (e)TLD wildcards). Extensions whitelisted for the externally_connectable.all_urls permission (and with that permission present) can use externally_connectable to list all_urls. This is used by the cryptotoken extension in order to allow any arbitrary site to initiate the u2f checks. However, there's no point in allowing an http site to connect to the extension, because https is a requirement for using u2f. As a first step to reducing the u2f extension to only whitelisting https sites, allow extensions whitelisted to specify all_urls in the externally_connectable entry to also be able to specify patterns with empty hosts like https://*/*. Bug: 810553 Change-Id: I3ff34ba8ce0126a777f52648245b0a85052511b1 Reviewed-on: https://chromium-review.googlesource.com/910037Reviewed-by:
-
Andrey Kosyakov authored
Change-Id: Ib656c9f22d696f516eba9a2ac5b6ea0d98c45e1a Reviewed-on: https://chromium-review.googlesource.com/912670Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Andrey Kosyakov <caseq@chromium.org> Cr-Commit-Position: refs/heads/master@{#535929}
-
Joshua Bell authored
Bug: 729800 Change-Id: If6cfed3427f778cf990721214240757cb06f320a Reviewed-on: https://chromium-review.googlesource.com/912242 Commit-Queue: Joshua Bell <jsbell@chromium.org> Commit-Queue: Victor Costan <pwnall@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#535928}
-
Sylvain Defresne authored
The EnableNewClearBrowsingDataUI flag has been disabled for one year, remove the code that can now be considered dead. Bug: 760084 Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs Change-Id: I22502beef12c2ce121cfcd896f1593829ecc140b Reviewed-on: https://chromium-review.googlesource.com/903245 Commit-Queue: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Martin Šrámek <msramek@chromium.org> Cr-Commit-Position: refs/heads/master@{#535927}
-
Abhishek Arya authored
This reverts commit 6ed531bd. Reason for revert: Caused multiple security regressions, see bug 810368. Original change's description: > dom: Remove PresentationAttributeCacheCleaner > > PresentationAttributeCacheCleaner was introduced before purging memory > was introduced. > > This CL removes PresentationAttributeCacheCleaner to clear cache soon > instead of delyaing with timers. > > This is part of efforts to replace default timer task runners with > other appropriate task runners in the renderer. > > Bug: 624694, 804694 > Change-Id: I7ed775d4b998be82e35d8eefe1f7bd4e0d0145a2 > Reviewed-on: https://chromium-review.googlesource.com/903942 > Reviewed-by: Alexander Timin <altimin@chromium.org> > Reviewed-by: Hayato Ito <hayato@chromium.org> > Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org> > Cr-Commit-Position: refs/heads/master@{#535306} TBR=jbroman@chromium.org,hayato@chromium.org,hajimehoshi@chromium.org,altimin@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 624694, 804694 Change-Id: I921fea361197deefd45968c07917cb5bc6fae0a4 Reviewed-on: https://chromium-review.googlesource.com/912091Reviewed-by:
Abhishek Arya <inferno@chromium.org> Commit-Queue: Abhishek Arya <inferno@chromium.org> Cr-Commit-Position: refs/heads/master@{#535926}
-
Dave Tapuska authored
- Add runtime setting to disable/enable WM_POINTER for touch. Defaults to disabled in this patch. Will be enabled as a followup change. - Fix min/max/exit buttons for touch. For unhandled events do a hit test and check if they are in the client area. If they are mark them as handled as we don't want windows to send us compatibility events if we've already dispatched them from the pointer events. - Set the last_touch_or_pen_message_time for touch events via WM_POINTER. BUG=792892,763223 Change-Id: I4350c7e84f96271b9ec27119815bf37a9461d489 Reviewed-on: https://chromium-review.googlesource.com/911752 Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#535925}
-
Simeon Anfinrud authored
This is needed to for the Android implementation of AvSettings. Bug: Internal b/68777468 Test: internal patch that uses this Change-Id: Ia99222e9cfe1deb92639e15ec331e9e5b9fbd568 Reviewed-on: https://chromium-review.googlesource.com/911932Reviewed-by:
Luke Halliwell <halliwell@chromium.org> Commit-Queue: Simeon Anfinrud <sanfin@chromium.org> Cr-Commit-Position: refs/heads/master@{#535924}
-
https://chromium.googlesource.com/catapult.git/+log/2b59889bc5fe..c60b98d9fa86 $ git log 2b59889bc..c60b98d9f --date=short --no-merges --format='%ad %ae %s' 2018-02-09 dtu [pinpoint] Fixes for results2 handler. Created with: roll-dep src/third_party/catapult The AutoRoll server is located here: https://catapult-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=master.tryserver.chromium.android:android_optional_gpu_tests_rel TBR=sullivan@chromium.org Change-Id: I4961a8270d19ded82d2b1fa6d3ef3fc735449c51 Reviewed-on: https://chromium-review.googlesource.com/911877Reviewed-by:
catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#535923}
-
Noel Gordon authored
Patches are no longer a thing. Remove the patch file for alder32 SIMD change since it mostly touched files that are not part of upstream. One upstream file adler32.c was touched but it has feature guards, so we should be good when merging in any upstream changes. Bug: 762564 Change-Id: Iad8e389667189300fa180755bc2ddc0187138bc0 Reviewed-on: https://chromium-review.googlesource.com/910539Reviewed-by:
-
Ken Rockot authored
TBR=dcheng@chromium.org TBR=jam@chromium.org Bug: 806965 Change-Id: Ic5256c9e50d4f483a140a207ec08b10c9cb29dd2 Reviewed-on: https://chromium-review.googlesource.com/912314Reviewed-by:
-
bsheedy authored
Fixes VrShellTransitionTest#testEnterVrInOverviewMode being flaky due to trying to call launchInVr with a null pointer for the launch intent. Change-Id: Ic4b661fbf430e65a2a51923c2652a18acf11ac86 Reviewed-on: https://chromium-review.googlesource.com/912610Reviewed-by:
Bill Orr <billorr@chromium.org> Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#535920}
-
Noel Gordon authored
Patch files are no longer needed per the README.chromium guidelines. Bug: 764431 Change-Id: I7cbfb9e51f74a7499697e6ff541bb02e30572c5b Reviewed-on: https://chromium-review.googlesource.com/910870Reviewed-by:
-
Ken Rockot authored
TBR=dcheng@chromium.org TBR=jam@chromium.org Bug: 806965 Change-Id: I7b4053e39cc589c96e9b64c991c0226fb1550563 Reviewed-on: https://chromium-review.googlesource.com/911945Reviewed-by:
-
Vladimir Levin authored
This patch makes PaintChunkProperties ctor explicit so that PropertyTreeState cannot be accidentally converted to it, instead requiring explicit construction. R=chrishtr@chromium.org Bug: 810958 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: Id3637eb7aea213af42f1802fcba907e1806bc3c1 Reviewed-on: https://chromium-review.googlesource.com/912463Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Commit-Queue: vmpstr <vmpstr@chromium.org> Cr-Commit-Position: refs/heads/master@{#535917}
-
Jiaquan He authored
This regression was introduced since ec4e7f70. While migration the app list ui to ash, we're showing dialogs in chrome without setting their parent. A nullptr parent will cause a breakage in |GetExtensionAnchorView|. Bug: 810665 Bug: 733662 Change-Id: Ifc8a38ec50a62a12c54e6d4503c3a2561f7ebd67 Reviewed-on: https://chromium-review.googlesource.com/911619Reviewed-by:
-
Avi Drissman authored
While the "hung page" dialog is up, the [X] button has the same effect as the "Wait" button. However, when the hung process goes away, the "hung page" dialog tries to silently close itself with no effect, but calling Close() on itself ends up calling through to the function handling the [X] button, which tries to take an action on a dead process. The "hung page" dialog closes itself, without taking any action, in two cases. The first case was when the render process became responsive again. In that case, internal pointers were nulled out so that no action would be taken when the dialog closed. This is the second case, where the process died for other reasons. In this case too, now, the internal pointers are nulled out to ensure no action (and no crash). BUG=810750 Change-Id: Ifc65c44003457fba87abf1e9977cdfe4218af168 Reviewed-on: https://chromium-review.googlesource.com/911729 Commit-Queue: Avi Drissman <avi@chromium.org> Reviewed-by:
Bret Sepulveda <bsep@chromium.org> Cr-Commit-Position: refs/heads/master@{#535915}
-
