- 17 Nov, 2017 32 commits
-
-
Xiaochu Liu authored
This reverts commit b8a20799. Reason for revert: it turns out that dbus method call in chrome requires UI thread (a DCHECK is broken). my initial plan to do blocking dbus call in OnCustomInstall is no longer viable. OnCustomInstall still needs to block its calling thread: crbug.com/783495 and i will investigate change in component updater to achieve this. more discussions regarding dbus blocking method call are here: https://chromium-review.googlesource.com/c/chromium/src/+/762080 Original change's description: > Move OnCustomInstall body to SequencedTaskRunner > > Currently, OnCustomInstall is invoked in a background thread but it > invokes imageloader on UI thread which does not bring any known benefits. > > We move imageloader operation from UI thread over a SequnecedTaskRunner. > > BUG=chromium:780201 > TEST=install is successful on DUT > > Change-Id: I8deb2ebae9ff22fcf992f4c34d6198ddbcad0c70 > Reviewed-on: https://chromium-review.googlesource.com/752622 > Reviewed-by: Joshua Pawlicki <waffles@chromium.org> > Reviewed-by: Greg Kerr <kerrnel@chromium.org> > Reviewed-by: Dan Erat <derat@chromium.org> > Commit-Queue: Xiaochu Liu <xiaochu@chromium.org> > Cr-Commit-Position: refs/heads/master@{#515291} TBR=derat@chromium.org,waffles@chromium.org,ejcaruso@chromium.org,kerrnel@chromium.org,xiaochu@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: chromium:780201 Change-Id: Ieb0b29ee30dcbd6208bd1c2fcd176cbb10ad48d4 Reviewed-on: https://chromium-review.googlesource.com/775561 Commit-Queue: Xiaochu Liu <xiaochu@chromium.org> Reviewed-by:
Dan Erat <derat@chromium.org> Cr-Commit-Position: refs/heads/master@{#517257}
-
Yuwei Huang authored
* Fix the issue of |input_entry_method_| not being reset to NOT_ACTIVE when the popup is hidden. * Use ET_GESTURE_LONG_PRESS instead of ET_GESTURE_LONG_TAP so that animation is triggered before the tap is released. * Add auto timeout to the popup when it is triggered by touch. * Hide the popup when it is triggered by touch and the user touches outside of the popup. Bug: 758456 Change-Id: Id2cb6642a4e9129a096c5025d5695aeacf304717 Reviewed-on: https://chromium-review.googlesource.com/775734Reviewed-by:
Robert Liao <robliao@chromium.org> Commit-Queue: Yuwei Huang <yuweih@chromium.org> Cr-Commit-Position: refs/heads/master@{#517256}
-
Chris Palmer authored
Bug: None Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs Change-Id: Ie390572e7a57e4fd7d691e615955a14520850767 Reviewed-on: https://chromium-review.googlesource.com/775907Reviewed-by:
Adrienne Porter Felt <felt@chromium.org> Commit-Queue: Chris Palmer <palmer@chromium.org> Cr-Commit-Position: refs/heads/master@{#517255}
-
Philip Rogers authored
When the LayoutView uses a background from the document element, and one of the background layers uses local geometry, a change in the document element's layout overflow, not size, should invalidate the background. Using ShouldFullyInvalidateBackgroundOnLayoutOverflowChange generates invalidations on layout overflow location changes which is new for the LayoutView and fixes an existing invalidation bug. This patch adds an invalidation test where the layout overflow changes but the size remains static. Before this patch, the test would crash with root layer scrolling due to underinvalidation. This patch also adds an invalidation test where the layout location changes but the size remains static. Before this patch, the test would fail with and without root layer scrolling. The change in BoxPaintInvalidatorTest.NonCompositedLayoutViewGradientResize from kBackground to kGeometry is not obvious. Before this change, the size change was detected in ViewBackgroundShouldFullyInvalidate even though the background did not need to be fully invalidated, which resulted in kBackground. With this change, the background does not need an invalidation and the size change is detected later in ComputePaintInvalidationReason which results in kGeometry. Bug: 781419 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_root_layer_scrolls;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: I01cbc5cc173a51be8a998cd2e49b8b2fae915dc2 Reviewed-on: https://chromium-review.googlesource.com/770603 Commit-Queue: Philip Rogers <pdr@chromium.org> Reviewed-by:
Steve Kobes <skobes@chromium.org> Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#517254}
-
Fady Samuel authored
SurfacesInstance's CompositorFrame always reported a device scale factor of 1. When surface scaling was moved to SurfaceAggregator, viz started scaling surfaces relative to their parent. The renderer's CompositorFrame correctly reported a DSF of 2. However, as the top level CF reported a DSF of 1, SurfaceAggregator scaled the renderer down. This CL fixes the problem by making surface the top level CompositorFrame reports the right device scale factor. Bug: 785596, 672962 Change-Id: Ife0668ae3f7c531265119d2b37954918504444ae Reviewed-on: https://chromium-review.googlesource.com/776078 Commit-Queue: Fady Samuel <fsamuel@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#517253}
-
Tsuyoshi Horo authored
Bug=786235 TBR=ricea@chromium.org Change-Id: I8f8540e451473ec7fdc0b4176f651e527cc0d599 Reviewed-on: https://chromium-review.googlesource.com/776253Reviewed-by:
Tsuyoshi Horo <horo@chromium.org> Cr-Commit-Position: refs/heads/master@{#517252}
-
Wez authored
elfinfo.py is a direct fork of mcgrathr@'s implementation: https://fuchsia.googlesource.com/packages/+/master/gn/elfinfo.py For simplicity the runner script now uses elfinfo to strip binaries regardless of the target architecture. Bug: 773444 Change-Id: Ic9dcc0298b69da05dcea1e178c3539bdfa1dccbe Reviewed-on: https://chromium-review.googlesource.com/750238 Commit-Queue: Wez <wez@chromium.org> Reviewed-by:
Scott Graham <scottmg@chromium.org> Reviewed-by:
Roland McGrath <mcgrathr@chromium.org> Cr-Commit-Position: refs/heads/master@{#517251}
-
Kevin Bailey authored
Bring in left edge of tab switch suggestion icon. Bug: 780835 Change-Id: Iec584365bdfcaadcc0d07b700297c190d5345628 Reviewed-on: https://chromium-review.googlesource.com/775029Reviewed-by:
Justin Donnelly <jdonnelly@chromium.org> Commit-Queue: Kevin Bailey <krb@chromium.org> Cr-Commit-Position: refs/heads/master@{#517250}
-
Will Chen authored
This converts a batch of tests from the old test framework (html file) into the new test framework (js file). Most of it was done through an automated transformation script, with a small amount of manual clean-up. Bug: 667560 Change-Id: I2171de04cddd60141504bd573c47fadeaeda7906 Reviewed-on: https://chromium-review.googlesource.com/769660 Commit-Queue: Will Chen <chenwilliam@chromium.org> Reviewed-by:
Andrey Kosyakov <caseq@chromium.org> Cr-Commit-Position: refs/heads/master@{#517249}
-
Tom Anderson authored
BUG=webrtc:8535 R=thestig@chromium.org NOTRY=true Change-Id: Iab5d7e16c88eec2f856d7c7d2e534c869bfcba9f Reviewed-on: https://chromium-review.googlesource.com/775573 Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#517248}
-
Kenneth Russell authored
This reverts commit d9e35229. Reason for revert: Caused http://crbug.com/786194 . Original change's description: > Move out threading DCHECK from WTF::Function. > > This patch is largely based on tzik's WIP patch: > https://chromium-review.googlesource.com/c/chromium/src/+/742824 > > Bug: 771087 > Change-Id: I20e2eb5ef09911a19e3b268e45ce6187d8edeffa > Reviewed-on: https://chromium-review.googlesource.com/765749 > Commit-Queue: Yuta Kitamura <yutak@chromium.org> > Reviewed-by: Kentaro Hara <haraken@chromium.org> > Reviewed-by: Taiju Tsuiki <tzik@chromium.org> > Cr-Commit-Position: refs/heads/master@{#517030} TBR=yutak@chromium.org,haraken@chromium.org,tzik@chromium.org Change-Id: I716bcb1e7efd0f7a46395120e35eef95ed33d0f8 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 771087 Reviewed-on: https://chromium-review.googlesource.com/775542Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#517247}
-
Tommy Nyquist authored
TBR=fgorski@chromium.org BUG=786237 NOTRY=true Change-Id: I3407d82f6d1046deb5a3b4075200d4427f6978da Reviewed-on: https://chromium-review.googlesource.com/776233Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Cr-Commit-Position: refs/heads/master@{#517246}
-
xzhan96 authored
This function became useless after ServiceWorkerRegistrationObjectHost mojofication is completed. BUG=758151 Change-Id: I9052d03b7b112ca4e286ed825ad01e02671896be Reviewed-on: https://chromium-review.googlesource.com/774238 Commit-Queue: Xiaofeng Zhang <xiaofeng.zhang@intel.com> Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#517245}
-
Tommy Nyquist authored
TBR=fgorski@chromium.org BUG=786233 NOTRY=true Change-Id: Ie212892a4382a9b8c28346492cdbf53aa4f9bb79 Reviewed-on: https://chromium-review.googlesource.com/775890Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Cr-Commit-Position: refs/heads/master@{#517244}
-
Rouslan Solomakhin authored
Before this patch, PaymentRequest.show() could reject with "Payment method not supported" message, which did not clarify which payment methods were not supported. This could be debugging confusing in a large production environment, where multiple PaymentRequest instances with different payment method names are created. This patch stores the set of payment method names for each instance of PaymentRequest and prints them out in the error message, if none of them are supported. After this patch, PaymentRequest.show() can reject with error message "Payment method 'xyz' is not supported". (Plurals are handled correctly.) Bug: 785992 Change-Id: I976b11b84f788ea98b4e413ca983edd8f792052d Reviewed-on: https://chromium-review.googlesource.com/775045Reviewed-by:
Marijn Kruisselbrink <mek@chromium.org> Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org> Cr-Commit-Position: refs/heads/master@{#517243}
-
webrtc-autoroll@chromium.org authored
https://webrtc.googlesource.com/src.git/+log/8d9c5406c7ba..aea84f55199c $ git log 8d9c5406c..aea84f551 --date=short --no-merges --format='%ad %ae %s' Created with: roll-dep src/third_party/webrtc 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 TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I8031adcdd3dfcb12a9187c0736c37a4c3d49ff11 Reviewed-on: https://chromium-review.googlesource.com/776093Reviewed-by:
WebRTC Roll Bot <webrtc-autoroll@chromium.org> Commit-Queue: WebRTC Roll Bot <webrtc-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#517242}
-
yusukes authored
BUG=None TEST=try Change-Id: I46d30cf99b9e2bf8efc602226ee718eac2e8e21f Reviewed-on: https://chromium-review.googlesource.com/769289Reviewed-by:
Elijah Taylor <elijahtaylor@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Commit-Queue: Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#517241}
-
Zhongyi Shi authored
connectivity probing packet back to the source address of received connectivity probing packet without latching on the new peer address from received connectivity probing packet. relnote: n/a current unused code, flag protected by quic_server_reply_to_connectivity_probing which is on by default. Manual merge internal change: 175728966 Bug: 774622 Change-Id: If0f958cdd2f0540be435cd222ba6f848acb9e185 Reviewed-on: https://chromium-review.googlesource.com/775993Reviewed-by:
Ryan Hamilton <rch@chromium.org> Commit-Queue: Zhongyi Shi <zhongyi@chromium.org> Cr-Commit-Position: refs/heads/master@{#517240}
-
David Dorwin authored
This is a reland of 307a1624 with a fix build for Android targets with enable_vr=false. Original change's description: > Clean up VR-related runtime flags > > * Consolidate VR-related features and use consistent naming. > * Clarify flag names and descriptions. > * Avoid the "enable" pattern. > > Some flag and feature names are changed, but users shouldn't be using these. > > 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: I56de992d246a13ff911cb8c88938a0690731c18e > Reviewed-on: https://chromium-review.googlesource.com/762392 > Reviewed-by: Nick Carter <nick@chromium.org> > Reviewed-by: Yash Malik <ymalik@chromium.org> > Reviewed-by: Brian Sheedy <bsheedy@chromium.org> > Reviewed-by: Klaus Weidner <klausw@chromium.org> > Reviewed-by: Ian Vollick <vollick@chromium.org> > Reviewed-by: Bill Orr <billorr@chromium.org> > Reviewed-by: Brandon Jones <bajones@chromium.org> > Commit-Queue: David Dorwin <ddorwin@chromium.org> > Cr-Commit-Position: refs/heads/master@{#516518} 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: I529be0c78ece4b4ae77558f991d6631c2973328c Reviewed-on: https://chromium-review.googlesource.com/772211 Commit-Queue: David Dorwin <ddorwin@chromium.org> Reviewed-by:
Brian Sheedy <bsheedy@chromium.org> Reviewed-by:
Yash Malik <ymalik@chromium.org> Reviewed-by:
David Dorwin <ddorwin@chromium.org> Reviewed-by:
Nick Carter <nick@chromium.org> Cr-Commit-Position: refs/heads/master@{#517239}
-
Xianzhu Wang authored
The wrapped text format can be used for rebaseline: just copy the wrapped text output and paste it into a command line like starting with run-webkit-tests --reset-results Discussed offline with Xiaocheng who developed the feature and we agreed to remove the feature to avoid maintaining another rebaseline tool. Change-Id: I4595a36b455c921aecaa565eceff8d0c929ff051 Reviewed-on: https://chromium-review.googlesource.com/776061 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
Xiaocheng Hu <xiaochengh@chromium.org> Cr-Commit-Position: refs/heads/master@{#517238}
-
Brett Wilson authored
This avoids needing to manually encode the type in the function call as the correct variant will automatically be called for the input type. Inline forwarding versions are left in the header for backwards compatibility. These will be replaced in future patches. Adds a Double->String16 conversion variant. Even though this is currently never used, it feels like we should have this variant available. Change-Id: I96ed8bb9100e8dbae3e4eff86edd3d1cfa040f8f Reviewed-on: https://chromium-review.googlesource.com/772974 Commit-Queue: Brett Wilson <brettw@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#517237}
-
Scott Violet authored
This way reconnection can be attempted. BUG=755328 TEST=covered by test Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel Change-Id: I1c07ef7bb04ca048146392a2f33de5b8ea83ee35 Reviewed-on: https://chromium-review.googlesource.com/775044Reviewed-by:
danakj <danakj@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#517236}
-
Yash Malik authored
This CL adds the header and .aidl file that Chrome needs to dynamically load the Keyboard API implementation from the Daydream Keyboard apk. Bug: 641470 Change-Id: Id47074cc0fdff786d0ab23dd0e43faabc0c2b023 Reviewed-on: https://chromium-review.googlesource.com/771537 Commit-Queue: Yash Malik <ymalik@chromium.org> Reviewed-by:
David Dorwin <ddorwin@chromium.org> Reviewed-by:
Biao She <bshe@chromium.org> Reviewed-by:
Max Moroz <mmoroz@chromium.org> Reviewed-by:
Brett Wilson <brettw@chromium.org> Cr-Commit-Position: refs/heads/master@{#517235}
-
Robert Liao authored
Some cleanup in response to https://chromium-review.googlesource.com/c/chromium/src/+/741455#message-2cd2ececba25f8c996dd3815baaa9b1312d7d899 BUG= Change-Id: Ib0db0f62ca7eb9e355eef139cb4958520205768e Reviewed-on: https://chromium-review.googlesource.com/775574Reviewed-by:
Gabriel Charette <gab@chromium.org> Commit-Queue: Robert Liao <robliao@chromium.org> Cr-Commit-Position: refs/heads/master@{#517234}
-
Sergei Datsenko authored
Add tests to verify we render correctly pages that use JavaScript to change page title and write console logs. Change-Id: I7b33a888ad721c1673aaa7520e0ea22c4bdcdd75 Reviewed-on: https://chromium-review.googlesource.com/765632Reviewed-by:
Alex Clarke <alexclarke@chromium.org> Commit-Queue: Sergei Datsenko <dats@chromium.org> Cr-Commit-Position: refs/heads/master@{#517233}
-
rajendrant authored
New datause recorder should created only in OnBeforeUrlRequest. OnUrlRequestDestroyed should not create a new recorder and immediately delete it. Bug: 781189 Change-Id: Iba78e7e7db913f71c76884ae8c66616fdfad9f8b Reviewed-on: https://chromium-review.googlesource.com/775475Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Commit-Queue: rajendrant <rajendrant@chromium.org> Cr-Commit-Position: refs/heads/master@{#517232}
-
Alex Clarke authored
We now flush the queues outside of the lock because TSAN complains about a lock order inversion for tasks that are posted from within a lock, with adestructor that acquires the same lock. Bug: Change-Id: Ide17f8d1f4a92f5e5febe67666e4901915197a16 Reviewed-on: https://chromium-review.googlesource.com/774262 Commit-Queue: Alex Clarke <alexclarke@chromium.org> Reviewed-by:
Eric Seckler <eseckler@chromium.org> Cr-Commit-Position: refs/heads/master@{#517231}
-
Victor Vasiliev authored
Merge internal change: 173052616 R=rch@chromium.org Bug: Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: Ib1999a7e5bf96d00a2926d80ce75c1deeaef28b4 Reviewed-on: https://chromium-review.googlesource.com/773178 Commit-Queue: Victor Vasiliev <vasilvv@chromium.org> Reviewed-by:
Ryan Hamilton <rch@chromium.org> Cr-Commit-Position: refs/heads/master@{#517230}
-
Tommy Nyquist authored
TBR=jming@chromium.org,dtrainor@chromium.org BUG=773346 NOTRY=true Change-Id: Iab66ba9fe9c1ecc11439ca06eb1fc434696297fd Reviewed-on: https://chromium-review.googlesource.com/776012Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Cr-Commit-Position: refs/heads/master@{#517229}
-
Tommy Nyquist authored
Failing test: ThumbnailDiskStorageTest#testRetrieveThumbnailShouldMakeEntryMostRecent TBR=qinmin@chromium.org BUG=786212 NOTRY=true Change-Id: I3a52e5017406efe413f7cbc0f3e37a9762914653 Reviewed-on: https://chromium-review.googlesource.com/776129Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Cr-Commit-Position: refs/heads/master@{#517228}
-
Tommy Nyquist authored
TBR=qinmin@chromium.org BUG=778829 NOTRY=true Change-Id: I7f95b097012f6bb5b46458c43e71edf4a5861c8c Reviewed-on: https://chromium-review.googlesource.com/776127Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Cr-Commit-Position: refs/heads/master@{#517227}
-
Tommy Nyquist authored
Failed build: https://build.chromium.org/p/chromium.android/builders/Nougat%20Phone%20Tester/builds/1309 TBR=xingliu@chromium.org,bsheedy@chromium.org BUG=786200 NOTRY=true Change-Id: I447df2a740bd0579b231844f4b2be3e7e04b7ee1 Reviewed-on: https://chromium-review.googlesource.com/776118 Commit-Queue: Tommy Nyquist <nyquist@chromium.org> Reviewed-by:
Xing Liu <xingliu@chromium.org> Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Cr-Commit-Position: refs/heads/master@{#517226}
-
- 16 Nov, 2017 8 commits
-
-
Yuke Liao authored
This reverts commit cef83520. Reason for revert: DownloadTaskImplTest.* tests fail on iOS 11 devices, both iPhone and iPad. Original change's description: > DownloadTaskImpl implementation for //ios/web Download API. > > This CL implements DownloadTask public interface. > > DownloadControllerImpl CL: crrev.com/c/758525 > Design doc: http://go/ios-web-download-api > > Bug: 780646 > Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs > Change-Id: I2c508e77f3e529223499d6f2791b28011589fe90 > Reviewed-on: https://chromium-review.googlesource.com/758506 > Reviewed-by: Sylvain Defresne <sdefresne@chromium.org> > Reviewed-by: Gregory Chatzinoff <gchatz@chromium.org> > Commit-Queue: Eugene But <eugenebut@chromium.org> > Cr-Commit-Position: refs/heads/master@{#517176} TBR=sdefresne@chromium.org,eugenebut@chromium.org,gchatz@chromium.org Change-Id: I14f0c37aa92330b0a665bf59bb665f010ee1209d No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 780646 Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs Reviewed-on: https://chromium-review.googlesource.com/776067Reviewed-by:
Yuke Liao <liaoyuke@chromium.org> Commit-Queue: Yuke Liao <liaoyuke@chromium.org> Cr-Commit-Position: refs/heads/master@{#517225}
-
Vlad Tsyrklevich authored
This reverts commit d2cc1555. Reason for revert: speculative revert, this might cause hangs on Linux component builds due to linker symbol resolution issues. Original change's description: > [cfi-icall] Use ProtectedMemory for GetProcAddress > > Control Flow Integrity [1] indirect call (cfi-icall) checking can not > verify that dynamically resolved function pointers call their intended > function. Instead we place the pointer for GLGetProcAddress in > ProtectedMemory, a wrapper for keeping variables in read-only memory > except for when they are initialized. After setting the pointer in > protected memory we can use the UnsanitizedCfiCall wrapper to disable > cfi-icall checking when calling it since we know it can not be tampered > with. > > [1] https://www.chromium.org/developers/testing/control-flow-integrity > > Bug: 771365 > 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: Ia79c1cfab8e00f88bcc437c34cbb3012537c015a > Reviewed-on: https://chromium-review.googlesource.com/769654 > Commit-Queue: Peter Collingbourne <pcc@chromium.org> > Reviewed-by: Kenneth Russell <kbr@chromium.org> > Reviewed-by: Peter Collingbourne <pcc@chromium.org> > Cr-Commit-Position: refs/heads/master@{#517208} TBR=kbr@chromium.org,pcc@chromium.org,vtsyrklevich@chromium.org Change-Id: Ia474d99619795f9b2c40422858caf2a02461e462 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 771365 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 Reviewed-on: https://chromium-review.googlesource.com/775596Reviewed-by:
Peter Collingbourne <pcc@chromium.org> Commit-Queue: Peter Collingbourne <pcc@chromium.org> Cr-Commit-Position: refs/heads/master@{#517224}
-
Vlad Tsyrklevich authored
This reverts commit d0de1771. Reason for revert: speculative revert, this might cause hangs on Linux component builds due to linker symbol resolution issues. Original change's description: > [CFI] Use ProtectedMemory in CertVerifyProcNSS > > Because CertVerifyProcNSS dynamically resolves a pointer to the function > CERT_CacheOCSPResponseFromSideChannel(), Control Flow Integrity [1] > indirect call (cfi-icall) checking can not verify that it is the > intended target for that function pointer call site. > > Since we can not use cfi-icall to check the function pointer, instead we > place the pointer in ProtectedMemory, a wrapper for keeping variables in > read-only memory except for when they are initialized. After setting the > pointer in protected memory we can use the UnsanitizedCfiCall wrapper to > disable cfi-icall checking when calling it since we know it can not be > tampered with. > > [1] https://www.chromium.org/developers/testing/control-flow-integrity > > Bug: 771365 > Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet > Change-Id: I5d65b3591681f3daa917b6516eec1e5e47513d12 > Reviewed-on: https://chromium-review.googlesource.com/765098 > Reviewed-by: Peter Collingbourne <pcc@chromium.org> > Reviewed-by: Eric Roman <eroman@chromium.org> > Commit-Queue: Peter Collingbourne <pcc@chromium.org> > Cr-Commit-Position: refs/heads/master@{#517169} TBR=eroman@chromium.org,pcc@chromium.org,vtsyrklevich@chromium.org Change-Id: I2d9a65fd6284c2cf954b46588d70fd1fa6292014 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 771365 Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet Reviewed-on: https://chromium-review.googlesource.com/775595Reviewed-by:
Peter Collingbourne <pcc@chromium.org> Commit-Queue: Peter Collingbourne <pcc@chromium.org> Cr-Commit-Position: refs/heads/master@{#517223}
-
Tom Anderson authored
Linking on arm64 can fail when dependent libraries are missing. That is, when linking against liba which depends on libb, linking will fail when only libb is missing. This CL adds a check to prevent these types of missing libraries. BUG=webrtc:8535 R=thestig@chromium.org Change-Id: I14e15ce534bd8ac5602f84dedcaab2db041656fb Reviewed-on: https://chromium-review.googlesource.com/773200Reviewed-by:
Lei Zhang <thestig@chromium.org> Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/master@{#517222}
-
Joel Einbinder authored
Brings the inspected page to front and focuses it Change-Id: I0e6b18b079091fe2b0dfccbc69829470dcfaeeec Reviewed-on: https://chromium-review.googlesource.com/761057Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Reviewed-by:
Alice Boxhall <aboxhall@chromium.org> Reviewed-by:
Andrey Lushnikov <lushnikov@chromium.org> Commit-Queue: Joel Einbinder <einbinder@chromium.org> Cr-Commit-Position: refs/heads/master@{#517221}
-
Ian Kilpatrick authored
We previously didn't correctly handle block-end borders. This fixes a couple of subtle bugs: - We don't grow the block-size of a fragment if it doesn't have any content. - We expand to encapsulate floats first, then grow to encapsulate the border. Bug: 635619 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: I7770a1d23a9c25fcab51e2e681e00e4b4d3e9d08 Reviewed-on: https://chromium-review.googlesource.com/770645 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#517220}
-
dpapad authored
The lower part of the sidebar was incorrectly sized, causing the scrollbar to appear after part of the content was already hidden. Bug: 773928 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I50458546e67af9dfcd5416bdc81f6dfa7ca6e5b6 Reviewed-on: https://chromium-review.googlesource.com/775554Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#517219}
-
Vlad Tsyrklevich authored
This reverts commit e77256b1. Reason for revert: Reverting while I investigate failures causing recursive calls to hang. Original change's description: > [cfi-icall] Use ProtectedMemory for localtime ptrs > > Control Flow Integrity [1] indirect call (cfi-icall) checking can not > verify that dynamically resolved function pointers call their intended > function. Instead we place the LibcFunctions pointers in > ProtectedMemory, a wrapper for keeping variables in read-only memory > except for when they are initialized. After setting the pointers in > protected memory we can use the UnsanitizedCfiCall wrapper to disable > cfi-icall checking when calling them since we know they can not be > tampered with. > > [1] https://www.chromium.org/developers/testing/control-flow-integrity > > Bug: 771365 > Change-Id: Ib74faff066e1107293b67d11f2a1a054bbff08b5 > Reviewed-on: https://chromium-review.googlesource.com/769853 > Reviewed-by: Chris Palmer <palmer@chromium.org> > Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org> > Reviewed-by: Peter Collingbourne <pcc@chromium.org> > Commit-Queue: Peter Collingbourne <pcc@chromium.org> > Cr-Commit-Position: refs/heads/master@{#517152} TBR=jorgelo@chromium.org,palmer@chromium.org,pcc@chromium.org,vtsyrklevich@chromium.org Change-Id: I77e142638d73bd53de4b6fc1b9db2ffc819f6459 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 771365 Reviewed-on: https://chromium-review.googlesource.com/775594Reviewed-by:
Peter Collingbourne <pcc@chromium.org> Commit-Queue: Peter Collingbourne <pcc@chromium.org> Cr-Commit-Position: refs/heads/master@{#517218}
-