- 03 May, 2018 40 commits
-
-
Marc Treib authored
The version without the "virtual/video-surface-layer/" prefix already had it. Bug: 520736,838128 Change-Id: I815f420dd134143837d1602e795075176f4e4eb5 Reviewed-on: https://chromium-review.googlesource.com/1042565Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Commit-Queue: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#555746}
-
Oskar Sundbom authored
Now that AudioInputDevice doesn't automatically redirect calls to the correct thread, ProcessedLocalAudioSource needs to do that itself. Bug: 838929 Change-Id: I55f1cf9c6446b90b464b229e4c9a621613bf9dfb Reviewed-on: https://chromium-review.googlesource.com/1041954 Commit-Queue: Oskar Sundbom <ossu@chromium.org> Reviewed-by:
Max Morin <maxmorin@chromium.org> Cr-Commit-Position: refs/heads/master@{#555745}
-
Egor Pasko authored
I think digit@chromium.org is more preferable these days, so change the remaining cases of digit@google.com to the preferable way for extra consistency. TBR=estevenson@chromium.org NOTRY=true Bug: None Change-Id: Ie545282b334f056c7e72836caabec8539441ec3b Reviewed-on: https://chromium-review.googlesource.com/1030376 Commit-Queue: Egor Pasko <pasko@chromium.org> Reviewed-by:
John Budorick <jbudorick@chromium.org> Reviewed-by:
David Turner <digit@chromium.org> Cr-Commit-Position: refs/heads/master@{#555744}
-
Kevin McNee authored
If we pinch an element with a touch-action that prevents pinch in an OOPIF, we route the pinch events to the child so that the child's TouchActionFilter filters them. Due to crbug.com/771330, the TouchActionFilter could let the pinch events through. We'll filter such events in RenderWidgetHostViewChildFrame::FilterInputEvent to prevent them from being sent to the child renderer. Bug: 827182 Change-Id: I3782a2d135a008df271a73d79ecade25dcc9f1a5 Reviewed-on: https://chromium-review.googlesource.com/1040354Reviewed-by:
James MacLean <wjmaclean@chromium.org> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Commit-Queue: Kevin McNee <mcnee@chromium.org> Cr-Commit-Position: refs/heads/master@{#555743}
-
Marc Treib authored
TBR=pauljensen@chromium.org Bug: 838524 Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: I1ae71d8c07f91827e164b046d4c379aeee4125ac Reviewed-on: https://chromium-review.googlesource.com/1042397 Commit-Queue: Marc Treib <treib@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#555742}
-
Antonio Gomes authored
This method is creating a net::HttpRequestHeaders object, serializing it to a string, and then parsing that string to create a new net::HttpRequestHeaders object. CL just returns the net::HttpRequestHeaders object directly. No expected behavior change. TESTS=Covered by existing tests. Bug: None Change-Id: I356c5987e0dcf60e454efc08f93d25ec75954c11 Reviewed-on: https://chromium-review.googlesource.com/1040705 Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Reviewed-by:
-
spqchan authored
The horizontal padding around the browser actions container was incorrectly reduced. This causes issues where you can't resize the omnibox (because the extensions now overlap the gripper) or drag the extensions into the wrench menu Bug: 825378, 825782 Change-Id: I66061a67546fab679c280a8d816b78dbe19b876e Reviewed-on: https://chromium-review.googlesource.com/1040914Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Sarah Chan <spqchan@chromium.org> Cr-Commit-Position: refs/heads/master@{#555740}
-
jonross authored
The test WorkspaceLayoutManagerBackdropTest.OpenAppListInOverviewMode is flaking so I'm disabling. TBR= xiyuan@chromium.org TEST=WorkspaceLayoutManagerBackdropTest.OpenAppListInOverviewMode Bug: 838756 Change-Id: I68f90b668996a885ef37e047d453e6ecca12217c Reviewed-on: https://chromium-review.googlesource.com/1042350Reviewed-by:
Jonathan Ross <jonross@chromium.org> Commit-Queue: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/master@{#555739}
-
David 'Digit' Turner authored
Now that we can safely depend on C++11, add a few move constructors to the String and Vector utility classes. This will be used in future CLs used to fix various issues with the crazy linker. BUG=802068 R=pasko@chromium.org, lizeb@chromium.org, agrieve@chromium.org Change-Id: I7fe420fe16e03e2eb1dbabafdcc0fb72c40ce3ba Reviewed-on: https://chromium-review.googlesource.com/1041960 Commit-Queue: David Turner <digit@chromium.org> Reviewed-by:
Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#555738}
-
Wez authored
Bug: 706592 Change-Id: I5e399e76e3ca98ee80d76aa4fd92b2d3bba60d39 Reviewed-on: https://chromium-review.googlesource.com/976085Reviewed-by:
Kevin Marshall <kmarshall@chromium.org> Reviewed-by:
-
Oskar Sundbom authored
This is done specifically to filter out the aggregate devices created when using kAudioUnitSubType_VoiceProcessingIO. Those should not be directly user-selectable. This CL allows other aggregate devices, but ensures they do not claim to support native echo cancellation, since they don't. Those devices will have to use software AEC. Bug: 837227 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: Iebb5286cafebe40204899ee2b7f1e0ff263d1fd6 Reviewed-on: https://chromium-review.googlesource.com/1030170 Commit-Queue: Oskar Sundbom <ossu@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#555736}
-
Annie Sullivan authored
NOTRY=true TBR=nednguyen@google.com Bug: 839411 Change-Id: I659bb4ca9a7cac243e6ccc294d383ce71776f84d Reviewed-on: https://chromium-review.googlesource.com/1042527Reviewed-by:
Annie Sullivan <sullivan@chromium.org> Commit-Queue: Annie Sullivan <sullivan@chromium.org> Cr-Commit-Position: refs/heads/master@{#555735}
-
Mikel Astiz authored
With DCHECKs enabled, GetStorageKey() might potentially fail in some codepaths that are updated in this patch. In addition, we introduce a CHECK for a scenario that is subject to investigation. Bug: 837517 Change-Id: I903f83e8ed7ca96aa525c0640aa9ffc629fc5721 Reviewed-on: https://chromium-review.googlesource.com/1042393Reviewed-by:
-
Vadym Doroshenko authored
Bug: None Change-Id: Ib80295f0aaa4bb2001c2ffd28d78924030b06e4f Reviewed-on: https://chromium-review.googlesource.com/1042289Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Commit-Queue: Vadym Doroshenko <dvadym@chromium.org> Cr-Commit-Position: refs/heads/master@{#555733}
-
jonross authored
Currently MSE_ExternalClearKey/EncryptedMediaTest.Playback_Multiple_VideoAudio_WebM is flaking on Mac. So I'm disabling it until that can be resolved. TBR=xhwang@chromium.org TEST=MSE_ExternalClearKey/EncryptedMediaTest.Playback_Multiple_VideoAudio_WebM Bug: 835585 Change-Id: Ifb82978c391d99804667c87a3d43ea1539bf9110 Reviewed-on: https://chromium-review.googlesource.com/1042373Reviewed-by:
-
Alex Newcomer authored
Add a chrome flag so users can enable the feature without using a switch. BUG=832876 Change-Id: I18b754c892e37e995561bd22b6e95545683ff03e Reviewed-on: https://chromium-review.googlesource.com/1012930Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Alex Newcomer <newcomer@chromium.org> Cr-Commit-Position: refs/heads/master@{#555731}
-
v8-autoroll authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/fc1a04fd..e043a8b3 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,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org Change-Id: Ieb151d6570f0c1960f2a39ff80502cd86a23b331 Reviewed-on: https://chromium-review.googlesource.com/1042045Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#555730}
-
Rune Lillesveen authored
We need the special-cased width because of some icon taking up space for input type="search". However, we should not modify computed style to do so. Instead use SetOverrideLogicalWidth(). Gets rid of MutableStyleRef() access. TEST=fast/forms/placeholder-position.html Bug: 813068 Change-Id: I93886bc8c53ff84b3c37a0cc543ab7dc274a758f Reviewed-on: https://chromium-review.googlesource.com/1041932 Commit-Queue: Rune Lillesveen <futhark@chromium.org> Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#555729}
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/0caef298c2ff..4722a4135911 $ git log 0caef298c..4722a4135 --date=short --no-merges --format='%ad %ae %s' 2018-05-03 rmistry Skip post upload hooks for new service accounts 2018-05-03 skia-bookmaker Update markdown files 2018-05-03 angle-skia-autoroll Roll third_party/externals/angle2/ 78feddc28..e708f004b (5 commits) 2018-04-30 bungeman Update SkRandomScalerContext to handle mask filters. 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;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=brianosman@chromium.org Change-Id: I2533cfb22f6b1d2b736592cac79b60a3dfd53ffa Reviewed-on: https://chromium-review.googlesource.com/1042368 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@{#555728}
-
arthursonzogni authored
This updates the following tests: - NavigationControllerBrowserTest.ReloadWithUrlAnchor - NavigationControllerBrowserTest.ReloadWithUrlAnchorAndScroll This two tests are making a <div> to scroll because of a navigation to an anchor. Then the tests check the scroll position is restored after a reload. The issue is that it is not deterministic when the scrolled area is not the root area. It is working consistently only because the main resource's response is small (e.g <64ko) and FrameLoader::ProcessFragment() is called before FrameLoader::RestoreScrollPositionAndViewState(). This CL make the tests uses the root area instead of the <div>. --- Description of what happens in the current code: 1) When ProcessFragment() is called first: a) ProcessFragment(): Several scrollable layers are scrolled such that the anchor is displayed. It may includes the root one, but also some children. b) RestoreScrollPositionAndViewState(): The root layer is scrolled using what is stored in the HistoryItem. It overrides the scroll done in a) for the root layer. Children layers are not overridden. 2) When RestoreScrollPositionAndViewState() is called first: a) RestoreScrollPositionAndViewState(): The root layer is scrolled using what is stored in the HistoryItem. Children layers are not scrolled. b) ProcessFragment(): Nothing happens because InitialScrollState::did_restore_from_history has been set to true in a). The ProcessFragment() will skip the fragment scroll. At the end, the difference is that the children layers are scrolled in 1), but not in 2). --- Bug: 821877, 831155, 839292 Change-Id: I11c74224ba42ad58814c4d4e185d7db189551775 Reviewed-on: https://chromium-review.googlesource.com/1039827Reviewed-by:
Jianpeng Chao <chaopeng@chromium.org> Reviewed-by:
Camille Lamy <clamy@chromium.org> Reviewed-by:
Steve Kobes <skobes@chromium.org> Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#555727}
-
Christian Dullweber authored
Protocol handler are site settings and should be deleted when a user decides to remove site settings from Clear Browsing Data. In order to allow precise deletions, we need to add a timestamp. Old handlers don't have timestamps, so they are treated as created at base::Time(0) and will only be removed if all data is deleted. Preinstalled and policy defined handlers are not removed. Bug: 824131 Change-Id: I2599a53ff5712d5aac28ba4024bb0bc123aa32e6 Reviewed-on: https://chromium-review.googlesource.com/1000697 Commit-Queue: Christian Dullweber <dullweber@chromium.org> Reviewed-by:
Matt Giuca <mgiuca@chromium.org> Reviewed-by:
Martin Šrámek <msramek@chromium.org> Cr-Commit-Position: refs/heads/master@{#555726}
-
Mounir Lamouri authored
Bug: None Change-Id: I99ee800fcfc009f45f789c1343ab026e400bb2d0 Reviewed-on: https://chromium-review.googlesource.com/1042405Reviewed-by:
-
Antonio Gomes authored
Of the various unittests associated with the migration that were reworked to work with the TestURLLoaderFactory machinery, two particularly became unneeded: - OneGoogleBarFetcherImplTest::SecondRequestOverridesFirst. The test exercised a premise of SimpleURLLoader that says once an instance is deleted its completion call will not be called. - OneGoogleBarFetcherImplTest, HttpErrorIsFatal The latest CL does not distinguish between server and common HTTP errors any more. CL also updates OneGoogleBarFetcherImplTests::thread_bundle_ to initialize with IO_MAINLOOP, so that it accommodates network requests being made on UI threa BUG=773295 Change-Id: I1a186f4067eb64f0e36d1b88ccbe9c8914a67480 Reviewed-on: https://chromium-review.googlesource.com/1031450 Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Reviewed-by:
Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#555724}
-
jonross authored
PushMessagingBrowserTest.UnsubscribeSuccess is flaking on Windows, so I'm disabling it. TBR=peter@chromium.org TEST=PushMessagingBrowserTest.UnsubscribeSuccess Bug: 838759 Change-Id: I7cf36aa034f8666639830a510aa1d18da6189911 Reviewed-on: https://chromium-review.googlesource.com/1042366Reviewed-by:
-
Alex Newcomer authored
When an event occurs that closes the Context Menu, do not repost the event. This cl also updates a few tests that broke once the change was made. Bug: 826517 Change-Id: I9fa29ab37f55ebbd62ef0764750174db1057043c Reviewed-on: https://chromium-review.googlesource.com/1038757Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Alex Newcomer <newcomer@chromium.org> Cr-Commit-Position: refs/heads/master@{#555722}
-
John Budorick authored
TBR=rdevlin.cronin@chromium.org Bug: 839371 Change-Id: I828d3038e4651275905ae82c984bc58d7262917e Reviewed-on: https://chromium-review.googlesource.com/1042367Reviewed-by:
-
Leonard Grey authored
In https://chromium-review.googlesource.com/c/chromium/src/+/852978, TabWindowController was changed to no longer subclass NSWindowController. But, since many callers assumed that a browser window's window controller was also its delegate, the new window controller proxies NSWindowDelegate methods to the TabWindowController. Unfortunately, it turns out that callers also make assumptions about the delegate, and if we only forward NSWindowDelegate methods, some fall through the cracks. This change removes the NSWindowDelegate check from the forwarding code, to ensure that TabWindowController receives all method calls meant for it. Bug: 835296 Change-Id: Ia16b8018c7c110e44a34b0f4cb1a636a143c3415 Reviewed-on: https://chromium-review.googlesource.com/1040945Reviewed-by:
Sidney San Martín <sdy@chromium.org> Commit-Queue: Leonard Grey <lgrey@chromium.org> Cr-Commit-Position: refs/heads/master@{#555720}
-
chaopeng authored
This issue is caused by: 1. When user tap on screen, we receive TapDown, ShowPress, Tap. TapDown and ShowPress will active the tapped element. Then Tap checks the LastShowPressTimeStamp() to stay active or cancel. 2. Each frame has GestureManager and we store LastShowPressTimeStamp() in GestureManager. 3. We check the root frame GestureManager LastShowPressTimeStamp() before hit test so we read the wrong LastShowPressTimeStamp(). In this patch, we move last_show_press_timestamp_ to root frame EventHandler so we don't need to hit test and figure which GestureManager should use. Bug: 714573 Change-Id: I80c75bf2f0493a6cbfd3b24873e1127da4fd7a27 Test: EventHandlerSimTest_TapActiveInFrame Test: Manual test for OOPIF Reviewed-on: https://chromium-review.googlesource.com/1041065Reviewed-by:
David Bokan <bokan@chromium.org> Commit-Queue: Jianpeng Chao <chaopeng@chromium.org> Cr-Commit-Position: refs/heads/master@{#555719}
-
Christian Fremerey authored
The API of the video capture service currently depends on a native enum VideoPixelFormat and a struct media.mojom.MailboxVideoFrameData declared in media_types.mojom. This CL breaks this dependency by defining a (non-native) Mojo enum VideoCapturePixelFormat and a struct media.mojom.MailboxBufferHandleSet specifically for the video capture service. This has two benefits: 1.) It makes it clear from the API that the video capture service actually only supports a much more limited set of pixel formats. 2.) It allows the reuse of the API definition in the mojom files in contexts where media/ and type mappings to native enums are not available. In particular, this is the case when trying to use the video capture service API from ChromiumOS. This is purely an interface refactoring. There is no intent for functional change. TBR=xjz@chromium.org Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel Change-Id: I418e5bb95bd92da0600afd874b6fde71e982761a Reviewed-on: https://chromium-review.googlesource.com/1026795Reviewed-by:
Christian Fremerey <chfremer@chromium.org> Reviewed-by:
Ken Rockot <rockot@chromium.org> Reviewed-by:
Tom Sepez <tsepez@chromium.org> Reviewed-by:
Emircan Uysaler <emircan@chromium.org> Commit-Queue: Christian Fremerey <chfremer@chromium.org> Cr-Commit-Position: refs/heads/master@{#555718}
-
Roman Sorokin authored
Problem is gssapi library (which Chrome uses for Kerberos SSO) uses krb5.conf settings. So even if DisableAuthNegotiateCnameLookup is enabled, GSSAPI still does canonicalization internally. This can be toggled in krb5.conf by setting dns_canonicalize_hostname, so this CL modifies the krb5.conf we get from authpolicy accordingly. It also sets reverse dns (rdns) to false, because Chrome does not do reverse search BUG=chromium:815158 TEST=ExistingUserControllerActiveDirectoryTest.PolicyChangeTriggersFileUpdate Change-Id: I418ed028d1bc4ba58883b01fb9f3c314fbed7c1c Reviewed-on: https://chromium-review.googlesource.com/1016802 Commit-Queue: Roman Sorokin <rsorokin@chromium.org> Reviewed-by:
Lutz Justen <ljusten@chromium.org> Reviewed-by:
Alexander Alekseev <alemate@chromium.org> Cr-Commit-Position: refs/heads/master@{#555717}
-
Max Moroz authored
This reverts commit d6e2784f. Reason for revert: llvm-cov is also using 'coverage' directory, so this change doesn't work well: https://github.com/llvm-mirror/llvm/blob/master/tools/llvm-cov/SourceCoverageView.h#L97 Original change's description: > [Code Coverage] Use platform name for the root directory instead of 'coverage'. > > That single-line change would be very helpful for hosting reports at GCS, as it > provides a multi-platform dir structure for free. > > Bug: 836663 > Change-Id: Ic9a984360cb352a23ace780d4aa600084be98a36 > Reviewed-on: https://chromium-review.googlesource.com/1041282 > Reviewed-by: Abhishek Arya <inferno@chromium.org> > Commit-Queue: Abhishek Arya <inferno@chromium.org> > Cr-Commit-Position: refs/heads/master@{#555664} TBR=inferno@chromium.org,mmoroz@chromium.org,liaoyuke@chromium.org Change-Id: I9812e8dde9ed121a4b379fef336336b7f62508c6 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 836663 Reviewed-on: https://chromium-review.googlesource.com/1042465Reviewed-by:
Max Moroz <mmoroz@chromium.org> Commit-Queue: Max Moroz <mmoroz@chromium.org> Cr-Commit-Position: refs/heads/master@{#555716}
-
Charlie Harrison authored
This refactors main.cc into a class RulesetConverter to make things a bit more testable. This CL only contains one behavior change: instead of using a colon separated list of directories as input, we instead use a comma separated list. Paths in windows frequently have colons in them :) Bug: 833419 Change-Id: I51c3b9c2b8ac6ce93a193d07f8bafaff897f3fdf Reviewed-on: https://chromium-review.googlesource.com/1036243 Commit-Queue: Charlie Harrison <csharrison@chromium.org> Reviewed-by:
Josh Karlin <jkarlin@chromium.org> Cr-Commit-Position: refs/heads/master@{#555715}
-
Jérôme Lebel authored
The tests were broken because UIScrollView doesn't scroll when animated, while WaitUntilConditionOrTimeout() is running. Those tests check if the displayed strings for the user consent are correct. Those tests work only if the user consent scroll view is scrolled to bottom. It was broken for iPhone 5s and SE. To avoid the issue above, this CL finds the first UIScollView in the sign-in screen, and then scrolls it to the bottom without animation (instead of simulating a tap on the More button). Tests broken: crrev.com/c/1010346 Tests disabled: crrev.com/c/1040346 Bug: 839001 Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs Change-Id: Ibb82222275d9d24d7bdfbb6b63111e69651cbe7a Reviewed-on: https://chromium-review.googlesource.com/1041085Reviewed-by:
Mihai Sardarescu <msarda@chromium.org> Commit-Queue: Jérôme Lebel <jlebel@chromium.org> Cr-Commit-Position: refs/heads/master@{#555714}
-
https://webrtc.googlesource.com/src.git/+log/2e28edaa8a25..01042067beb1 $ git log 2e28edaa8..01042067b --date=short --no-merges --format='%ad %ae %s' Created with: roll-dep src/third_party/webrtc BUG=chromium:838854,chromium: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 TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: Ie4430832d12b820c23370ae2ecc2045f0b9e0a28 Reviewed-on: https://chromium-review.googlesource.com/1042026 Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#555713}
-
Elly Fong-Jones authored
TBR=jbudorick@chromium.org Bug: 828031 Change-Id: I30eec44d2abf35a594874a2e20a0d6906a1a92f7 Reviewed-on: https://chromium-review.googlesource.com/1042206Reviewed-by:
-
Helen Li authored
This CSP test fails when network service flag is on. wpt/content-security-policy/inside-worker/dedicated-inheritance.html TBR=jam@chromium.org Bug: 729849 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo Change-Id: I5488b1eb50040792f84d0cbf9efd3c1d68fcaf2d Reviewed-on: https://chromium-review.googlesource.com/1041405 Commit-Queue: Helen Li <xunjieli@chromium.org> Reviewed-by:
Helen Li <xunjieli@chromium.org> Cr-Commit-Position: refs/heads/master@{#555711}
-
Marc Treib authored
TBR=riajiang@chromium.org Bug: 838835 Change-Id: Ie69310cde0d51472d3446c57b8bbd66bc703a602 Reviewed-on: https://chromium-review.googlesource.com/1041957Reviewed-by:
-
Samuel Huang authored
- Move bucket to gs://chromium-binary-patching/zucchini-testdata, which is more specific, and has a manifest file: gsutil cat gs://chromium-binary-patching/zucchini_testdata/manifest.json - Old file copies are kept in root as legacy. - Move destination path to Zucchini root, and make it recursively look for .sha1 files. The reaosn is that we'll add fuzzing data in a different directory, and want to use the same hook name. Details: Change-Id: Ie96cb99de9e0727d3cb6dfb0afa25c08cf4f31c3 Reviewed-on: https://chromium-review.googlesource.com/1038047Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Reviewed-by:
Samuel Huang <huangs@chromium.org> Commit-Queue: Samuel Huang <huangs@chromium.org> Cr-Commit-Position: refs/heads/master@{#555709}
-
Devlin Cronin authored
The ExtensionFunction::GetAssociatedWebContentsDeprecated() method is unpredictable and can return surprising values in certain circumstances. It is deprecated and should be removed to ensure that callers are using the WebContents they expect. Update the passwordsPrivate API to use GetSenderWebContents() instead. Bug: 461394 Change-Id: I24b75989786d06aa14a64f403d134e293eb9902a Reviewed-on: https://chromium-review.googlesource.com/1040530Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Commit-Queue: Devlin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/master@{#555708}
-
jonross authored
BrowserSideFlingBrowserTest.AutoscrollFling is flaking on ChromeOS, so I'm disabling it. TBR=dtapuska@chromium.org TEST=BrowserSideFlingBrowserTest.AutoscrollFling Bug: 838769 Change-Id: I1d8bc6ed78c9e15258ff90ccef9535e42d8189cf Reviewed-on: https://chromium-review.googlesource.com/1042029Reviewed-by:
-
