- 31 Jan, 2018 40 commits
-
-
Tatsuhisa Yamaguchi authored
Once loading of an archive has been started, it should not start loading the same file again. Existing logic returns "EXISTS" error via fileSystemProvider API when an archive is already mounted. However, it missed handling of a case where user requested opening the same archive while its loading is ongoing. It typically happens when an archive is on Drive and not yet cached. As a transitive fix, this change reuses the "scanning..." message to indiacte that user need to wait operation finish in such case. Bug: 807254 Test: manually tested on Files app as noted in the bug. Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I90d5b8b2c157ea40b40ad106bbcb85b1bd022ea7 Reviewed-on: https://chromium-review.googlesource.com/895424 Commit-Queue: Tatsuhisa Yamaguchi <yamaguchi@chromium.org> Reviewed-by:
Yuki Awano <yawano@chromium.org> Cr-Commit-Position: refs/heads/master@{#533292}
-
Jonathan Backer authored
This CL adds a few things: - autogenerated unittests - associated mocks - associated test drivers - enough implementation in raster_decoder.cc to make the tests pass No changes to GLES2 autogen. Bug: 789238 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: Iac2ee4922a21f3bd11ff58693e2e5fb1fe26bd45 Reviewed-on: https://chromium-review.googlesource.com/891988 Commit-Queue: Jonathan Backer <backer@chromium.org> Reviewed-by:
Victor Miura <vmiura@chromium.org> Cr-Commit-Position: refs/heads/master@{#533291}
-
Elly Fong-Jones authored
The code in [AppController shouldQuitWithInProgressDownloads] needs to account for the fact that incognito profiles have separate DownloadManagers from their parent profiles. This change does this by considering incognito profiles as though they were regular profiles. 1) Create a profile, create an incognito window from it, start a download, quit Chrome: a "cancel download?" prompt should now appear. 2) Create a profile, create an incognito window from it, quit Chrome: no "cancel download?" prompt should appear. 3) Create a profile, start a download, quit Chrome: a "cancel download?" prompt should appear as before. 4) Create a profile, quit Chrome: no "cancel download?" prompt should appear. Bug: 88419 Test: Manual Change-Id: Ib25995c45ae99f3b1fe00b15a37108399be06f77 Reviewed-on: https://chromium-review.googlesource.com/895802 Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#533290}
-
Friedrich Horschig authored
When the search view is collapsed, the search should be reset entirely. Bug: 807574, 807306 Change-Id: Id13eb9e119459d05751e06b515671eccacc776f2 Reviewed-on: https://chromium-review.googlesource.com/895485Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Friedrich Horschig <fhorschig@chromium.org> Cr-Commit-Position: refs/heads/master@{#533289}
-
Guido Urdaneta authored
This CL introduces two main updates to constraints processing for audio: 1. The SelectSettings() algorithm now considers audio-processing properties as belonging to each device instead of being considered independent of the device. The reason is that, while the audio-processing module can be applied to any source, once a source has processing applied, all tracks for that source must use the same audio-processing settings. 2. The getUserMedia() implementation leverages (1) and makes sure that candidate settings for audio sources already in use are limited to their current configuration. Bug: 802198 Change-Id: I3554206e852ff41116a1fe02be45a7a8dff4760d Reviewed-on: https://chromium-review.googlesource.com/881183Reviewed-by:
Henrik Boström <hbos@chromium.org> Commit-Queue: Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#533288}
-
Miriam Gershenson authored
The DnsConfigService can't get a correct DNS config for a VPN until Android M. On earlier versions, check for a VPN and treat it as a config read failure. Bug: 805020 Change-Id: I696c52a2e012460ddd70381e5278c3abca9ca665 Reviewed-on: https://chromium-review.googlesource.com/894149Reviewed-by:
Paul Jensen <pauljensen@chromium.org> Commit-Queue: Miriam Gershenson <mgersh@chromium.org> Cr-Commit-Position: refs/heads/master@{#533287}
-
Rouslan Solomakhin authored
This reverts commit 6e232c77. Reason for revert: Possibly broke http/tests/devtools/tracing/timeline-style/timeline-recalculate-styles.js in https://ci.chromium.org/buildbot/chromium.win/Win7%20Tests%20%28dbg%29%281%29/66101 Original change's description: > Roll src/third_party/catapult/ 7c98d04db..12ffa8933 (2 commits) > > https://chromium.googlesource.com/catapult.git/+log/7c98d04db58b..12ffa8933991 > > $ git log 7c98d04db..12ffa8933 --date=short --no-merges --format='%ad %ae %s' > 2018-01-31 perezju [Devil] Dismiss errors in GetRecursiveDiskUsage > 2018-01-25 perezju [Telemetry] Move profile setup on desktop to its possible browser > > 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: I349d5d5c652ff38030b5ad74c49ad136e791b421 > Reviewed-on: https://chromium-review.googlesource.com/895406 > Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> > Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> > Cr-Commit-Position: refs/heads/master@{#533256} TBR=sullivan@chromium.org,catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Change-Id: I881b5f5750cd5b49f073464647ae0c925db1a4b3 No-Presubmit: true No-Tree-Checks: true No-Try: true Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel Reviewed-on: https://chromium-review.googlesource.com/895663Reviewed-by:
Rouslan Solomakhin <rouslan@chromium.org> Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org> Cr-Commit-Position: refs/heads/master@{#533286}
-
Balazs Engedy authored
This reverts commit aad276cb. Reason for revert: Suspected to be the culprit for breaking Mac browser_tests and unit_tests that use an local python test server, e.g.: RUN ] CloudPolicyTest.FetchPolicy [4513:779:0131/005831.599342:3098052568384:ERROR:local_test_server_posix.cc(81)] poll() timed out; bytes_read=0 [4513:779:0131/005831.599552:3098052743513:ERROR:local_test_server_posix.cc(168)] Could not read server_data_len ../../chrome/browser/policy/cloud/cloud_policy_browsertest.cc:190: Failure Value of: test_server_->Start() Actual: false Expected: true Original change's description: > Use vpython rather than python for GPU tests on the bots. > > From talking with iannucci@, this is the easiest way to use vpython > with these tests on the bots. Once the LUCI conversion is done, this > will be a no-op, and can be removed. > > Incorporate the newly deployed pyobjc wheels into Chromium's root > .vpython; they are needed by helper scripts in the GPU directory. > > Bug: 776804, 804174 > 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: I1c720a9f7992e411aa85bcc7959de95ecc03c1f5 > Reviewed-on: https://chromium-review.googlesource.com/869512 > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Commit-Queue: Kenneth Russell <kbr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#533226} TBR=iannucci@chromium.org,kbr@chromium.org,dnj@chromium.org,nednguyen@google.com Change-Id: Idb03a7a1176d79443b3a29267a16c7631fbf1be8 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 776804, 804174 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/894208Reviewed-by:
Balazs Engedy <engedy@chromium.org> Commit-Queue: Balazs Engedy <engedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#533285}
-
Andreas Haas authored
R=inferno@chromium.org Change-Id: Ida49d839c1a0ccfd60d4ba556f6225000c81f3a6 Reviewed-on: https://chromium-review.googlesource.com/895533Reviewed-by:
Abhishek Arya <inferno@chromium.org> Commit-Queue: Abhishek Arya <inferno@chromium.org> Cr-Commit-Position: refs/heads/master@{#533284}
-
David Roger authored
Change-Id: I44027badf2aaa5d4aa556ab6bfb686b0e8913b98 Reviewed-on: https://chromium-review.googlesource.com/893562Reviewed-by:
Mihai Sardarescu <msarda@chromium.org> Commit-Queue: David Roger <droger@chromium.org> Cr-Commit-Position: refs/heads/master@{#533283}
-
Clemens Hammacher authored
The wasm call fuzzer is superseded by the wasm compile fuzzer, thus remove it. R=ahaas@chromium.org Change-Id: I732a3d2ca81a1642e862f2cf374e4adaf51e8f07 Reviewed-on: https://chromium-review.googlesource.com/895531 Commit-Queue: Abhishek Arya <inferno@chromium.org> Reviewed-by:
-
Andrii Shyshkalov authored
R=jbudorick@chromium.org Bug: 731553 Change-Id: I064be66068ef0a02e5bab21061112d6174395246 No-Try: True Reviewed-on: https://chromium-review.googlesource.com/893654Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: John Budorick <jbudorick@chromium.org> Cr-Commit-Position: refs/heads/master@{#533281}
-
Brian Salomon authored
Bug: 807055 Change-Id: Iccbce54b0ca478701575edee04558e081e3a70d7 Reviewed-on: https://chromium-review.googlesource.com/891485Reviewed-by:
Robert Phillips <robertphillips@google.com> Commit-Queue: Brian Salomon <bsalomon@chromium.org> Cr-Commit-Position: refs/heads/master@{#533280}
-
https://pdfium.googlesource.com/pdfium.git/+log/2334660053e0..4b0c5b935471 $ git log 233466005..4b0c5b935 --date=short --no-merges --format='%ad %ae %s' 2018-01-31 dsinclair Remove NumericLimit params which are always the same Created with: roll-dep src/third_party/pdfium The AutoRoll server is located here: https://pdfium-roll.skia.org Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=dsinclair@chromium.org Change-Id: I2312f9ea3374e68a718d0dbb0bceebddf51e25dd Reviewed-on: https://chromium-review.googlesource.com/894672Reviewed-by:
pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#533279}
-
Sahel Sharify authored
This cl moves touchscreen handling logic from the renderer to the browser. The fling_controller handles a GSF and generates a fling curve, as long as the fling is active, the controller advances the fling progress and sends GSU events with computed scroll deltas to the renderer. At the end of the fling the controller generates and sends a GSE event. Deleted event_unittests are either covered in fling_controller_unittests and fling_booster_unittests or are not relevant anymore. Bug: 249063 TEST: FlingControllerTest.* Change-Id: I072da0ae726eed3d0a567843c9ccc84725074eb0 Reviewed-on: https://chromium-review.googlesource.com/879359Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Timothy Dresser <tdresser@chromium.org> Commit-Queue: Sahel Sharifymoghaddam <sahel@chromium.org> Cr-Commit-Position: refs/heads/master@{#533278}
-
https://webrtc.googlesource.com/src.git/+log/3c706972bad7..bbf46c27538c $ git log 3c706972b..bbf46c275 --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;master.tryserver.chromium.win:win-msvc-dbg TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I00831f5efff8cc22e89cc7b8d87f07620f40ff76 Reviewed-on: https://chromium-review.googlesource.com/895285Reviewed-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@{#533277}
-
Rouslan Solomakhin authored
This reverts commit 2f79d543. Reason for revert: Failed compile on https://ci.chromium.org/buildbot/chromium.win/WinMSVC64/1698 [74/5635] ACTION //third_party/WebKit/Source/platform:color_data(//build/toolchain/win:x64) FAILED: gen/blink/platform/ColorData.cpp E:/b/depot_tools/win_tools-2_7_6_bin/python/bin/python.exe ../../third_party/WebKit/Source/build/scripts/gperf.py ../../third_party/gperf/bin/gperf.exe --key-positions=* -D -s 2 ../../third_party/WebKit/Source/platform/ColorData.gperf --output-file=gen/blink/platform/ColorData.cpp Traceback (most recent call last): File "../../third_party/WebKit/Source/build/scripts/gperf.py", line 88, in <module> main() File "../../third_party/WebKit/Source/build/scripts/gperf.py", line 85, in main generate_gperf(gperf_path, open(infile).read(), gperf_args)) File "../../third_party/WebKit/Source/build/scripts/gperf.py", line 30, in generate_gperf gperf_output = gperf.communicate(gperf_input)[0] File "E:\b\depot_tools\win_tools-2_7_6_bin\python\bin\lib\subprocess.py", line 798, in communicate return self._communicate(input) File "E:\b\depot_tools\win_tools-2_7_6_bin\python\bin\lib\subprocess.py", line 1035, in _communicate self.stdin.write(input) IOError: [Errno 22] Invalid argument Original change's description: > various small tweaks to blink's gperf use > > * make gperf.py call generate_gperf() both when it's invoked via > use_jinja_gperf_template() as well as when it's called directly > as a standalone script > > * make generate_gperf() do massaging of gperf's output to remove > uses of the `register` keyword (needed to build with -std=c++17) > and replace `/*FALLTHROUGH*/` with real FALLTHROUGH statements > (needed for -Wimplicit-fallthrough) > > * remove now-unneeded suppressions for -Wdeprecated-register > > * remove TODO about removing gperf.py; that's from a time when the > script was 1 non-comment line long > > * bump check_output() requirement in comment to 3.4 (since that added > the input= parameter) > > * add missing dependency on gperf.py to build steps calling it > through the jinja interface, so that these edges rerun when > gperf.py gets modified > > * add a comment mentioning gperf.py at the start of the generated > outputs > > * make :character_data not call gperf.py since it doesn't use gperf, > and make it use compiled_action() instead which is made for > exactly character_data's use case > > No intended behavior change. > > Bug: 752720,177475 > Change-Id: I56372729bb47787e2d41a5dff2f30804574770f0 > Reviewed-on: https://chromium-review.googlesource.com/891141 > Commit-Queue: Nico Weber <thakis@chromium.org> > Reviewed-by: Darren Shen <shend@chromium.org> > Reviewed-by: Daniel Cheng <dcheng@chromium.org> > Cr-Commit-Position: refs/heads/master@{#533269} TBR=dcheng@chromium.org,thakis@chromium.org,shend@chromium.org Change-Id: Iddbf12ba341fa4ea456552f449154bc5d6328073 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 752720, 177475 Reviewed-on: https://chromium-review.googlesource.com/895543Reviewed-by:
-
Ioana Pandele authored
This CL adds: - Request for password serialization - Writing passwords to a temporary file - Handling of errors that can occur during writing - Presenting a UIActivityViewController with options to save the file Bug:789122 Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs Change-Id: I2963b9b425b5e6de62f0461c2d66cc19b2d61f22 Reviewed-on: https://chromium-review.googlesource.com/842623Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Commit-Queue: Ioana Pandele <ioanap@chromium.org> Cr-Commit-Position: refs/heads/master@{#533275}
-
James Cook authored
All Chrome OS platforms use ozone. Make the filename match the header. Bug: none Test: compiles Change-Id: I0b62471c2eab082fe9863aa1db8976fbddc24d2d Reviewed-on: https://chromium-review.googlesource.com/894737Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Commit-Queue: James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#533274}
-
Ella Ge authored
When hit on a scrollbar, hit_layer can be false. It cause the hit test result in child frame not pass to outer frame. In this CL, force hit_layer to true when hit on frame scrollbar. Bug: 806300 Change-Id: Ie2debd3d2eae626022af508b0c0962e39095fb17 Reviewed-on: https://chromium-review.googlesource.com/889518Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Ella Ge <eirage@chromium.org> Cr-Commit-Position: refs/heads/master@{#533273}
-
James Cook authored
Disable it in viz_browser_tests via filter file so we can get the Mojo FYI bot green. it's been failing for > 1 week and > 200 builds. Bug: 807465 Change-Id: I4f067303cc74d607d519fd7f72b20d5b75d92c28 Reviewed-on: https://chromium-review.googlesource.com/894634Reviewed-by:
Michael Wasserman <msw@chromium.org> Cr-Commit-Position: refs/heads/master@{#533272}
-
Vadym Doroshenko authored
Atm in case when Password Manager tries to fill a password form and encounters inputs with the same names it stops processing such form. This CL implements that the first field will be filled. Bug: 803215 Change-Id: Ia1ec0f1de8390c59308e8c70cbaebe285ae7431d Reviewed-on: https://chromium-review.googlesource.com/886707 Commit-Queue: Vadym Doroshenko <dvadym@chromium.org> Reviewed-by:
Maxim Kolosovskiy <kolos@chromium.org> Cr-Commit-Position: refs/heads/master@{#533271}
-
Nicolas Dossou-gbete authored
Additionally to scaning the first level of third_party for README.chromium files, these directories can now contain an additional_readme_paths.json file that lists subdirectories that will contain the actual third_party dependencies to take into account for credits generation. Bug: 794210 Change-Id: If6eef9fcd615bd96b9a260f9ae4d0c0c4fd6405a Reviewed-on: https://chromium-review.googlesource.com/822612 Commit-Queue: Nicolas Dossou-Gbété <dgn@chromium.org> Reviewed-by:
Hiroshi Ichikawa <ichikawa@chromium.org> Reviewed-by:
Bernhard Bauer <bauerb@chromium.org> Cr-Commit-Position: refs/heads/master@{#533270}
-
Nico Weber authored
* make gperf.py call generate_gperf() both when it's invoked via use_jinja_gperf_template() as well as when it's called directly as a standalone script * make generate_gperf() do massaging of gperf's output to remove uses of the `register` keyword (needed to build with -std=c++17) and replace `/*FALLTHROUGH*/` with real FALLTHROUGH statements (needed for -Wimplicit-fallthrough) * remove now-unneeded suppressions for -Wdeprecated-register * remove TODO about removing gperf.py; that's from a time when the script was 1 non-comment line long * bump check_output() requirement in comment to 3.4 (since that added the input= parameter) * add missing dependency on gperf.py to build steps calling it through the jinja interface, so that these edges rerun when gperf.py gets modified * add a comment mentioning gperf.py at the start of the generated outputs * make :character_data not call gperf.py since it doesn't use gperf, and make it use compiled_action() instead which is made for exactly character_data's use case No intended behavior change. Bug: 752720,177475 Change-Id: I56372729bb47787e2d41a5dff2f30804574770f0 Reviewed-on: https://chromium-review.googlesource.com/891141 Commit-Queue: Nico Weber <thakis@chromium.org> Reviewed-by:
Darren Shen <shend@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#533269}
-
Mugdha Lakhani authored
Bug: 799483 Change-Id: Id180ebd58acefa8f047858101c586b940b435e70 Reviewed-on: https://chromium-review.googlesource.com/887083 Commit-Queue: Mugdha Lakhani <nator@chromium.org> Reviewed-by:
Peter Beverloo <peter@chromium.org> Cr-Commit-Position: refs/heads/master@{#533268}
-
Elly Fong-Jones authored
This change introduces a new command line flag, --polychrome, which causes a mac_views_browser build to use the existing Cocoa UI instead of the new Views browser UI. This involves: 1) Linking all of the Cocoa UI in when building the Views browser; 2) Resolving symbol and filename conflicts; 3) Introducing views_mode_controller::IsViewsBrowserCocoa(); 4) Having BrowserWindowFactory choose which type of BrowserWindow to create based on the value of views_mode_controller::IsViewsBrowserCocoa() This change also makes unit_tests build, but not any other targets - it is likely that browser_tests does not build. The resulting mac_views_browser *runs* but is unstable because of bug 804950, which is hard to address without this CL being landed. The current name is deliberately a bit silly, under the theory that we'll pick a better one once the approach solidifies :) Bug: 802257,804950 Change-Id: I30aaef7ed08dd11b66d59d5b816f57641bf2f209 Reviewed-on: https://chromium-review.googlesource.com/874730 Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Reviewed-by:
Trent Apted <tapted@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#533267}
-
Maxim Kolosovskiy authored
In https://chromium-review.googlesource.com/c/chromium/src/+/725342, enum.xm wasn't updated properly. It should corresponds to |ShowAllSavedPasswordsContext| Bug: 739343, 775825 Change-Id: I0129522e95414412aeb6f271d0aa07cc236801cf Reviewed-on: https://chromium-review.googlesource.com/893560Reviewed-by:
Tatiana Gornak <melandory@chromium.org> Commit-Queue: Maxim Kolosovskiy <kolos@chromium.org> Cr-Commit-Position: refs/heads/master@{#533266}
-
https://webrtc.googlesource.com/src.git/+log/70294c8eab2f..3c706972bad7 $ git log 70294c8ea..3c706972b --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;master.tryserver.chromium.win:win-msvc-dbg TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: Ib690a34c8ca7172f14fc7f1917f61c242c05c948 Reviewed-on: https://chromium-review.googlesource.com/894711 Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
-
Christos Froussios authored
I also changed the timing on the IN_PROGRESS update to occur as soon as the destination is known. If we happen to still be serialising, that is an implementation detail that should not be affect the UI. Bug: 785237 Change-Id: Ie9466840b1e4bf11ddfaa4c69045326ab3b11fe3 Reviewed-on: https://chromium-review.googlesource.com/789330 Commit-Queue: Christos Froussios <cfroussios@chromium.org> Reviewed-by:
Vaclav Brozek <vabr@chromium.org> Cr-Commit-Position: refs/heads/master@{#533264}
-
Bence Béky authored
Add unittest to document existing Websocket behavior with existing HTTP/2 connection: if there is an HTTP/2 connection open to a server, a Websocket request should not use it, but instead open a new connection with HTTP/2 disabled. Bug: 801564 Change-Id: Ibff7278cb298491f8183ca0946acfef39c7e8309 Reviewed-on: https://chromium-review.googlesource.com/891738 Commit-Queue: Bence Béky <bnc@chromium.org> Reviewed-by:
Adam Rice <ricea@chromium.org> Cr-Commit-Position: refs/heads/master@{#533263}
-
Naina Raisinghani authored
Revert "Replace CSSPropertyValueSet in @font-face related objects with a new AtRuleDescriptorValueSet." This reverts commit 4e4f284d. Revert "Fix segfault in AtRuleCSSStyleDeclaration::getPropertyValue" This reverts commit 32c5f6b3. Bug: 807229 Change-Id: I5c92de4734440709c60b383c485967795e9643b2 Reviewed-on: https://chromium-review.googlesource.com/895225 Commit-Queue: nainar <nainar@chromium.org> Reviewed-by:
Alan Cutter <alancutter@chromium.org> Cr-Commit-Position: refs/heads/master@{#533262}
-
Boris Sazonov authored
This CL removes context parameter from SigninManager instance getter. It also removes context parameter from FirstRunSignInProcessor.updateSigninManagerFirstRunCheckDone, as it becomes unused. Bug: None Change-Id: I49aebc25becfce676a3eba1e15d7c4451c0ba36c Reviewed-on: https://chromium-review.googlesource.com/883806Reviewed-by:
-
v8-autoroll authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/70bfb939..13ef7708 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: I05fe99a062e02526d70c4511ce26e7ec0fad3756 Reviewed-on: https://chromium-review.googlesource.com/895562Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#533260}
-
Henrik Grunell authored
That is, after input stream creation. It will be removed from the underlying WebRTC component shortly. Bug: webrtc:8346 Change-Id: Ib80b27b4580b737bcfec7f80acc9207ddafab419 Reviewed-on: https://chromium-review.googlesource.com/888703Reviewed-by:
Olga Sharonova <olka@chromium.org> Commit-Queue: Henrik Grunell <grunell@chromium.org> Cr-Commit-Position: refs/heads/master@{#533259}
-
Eric Willigers authored
Test that perspective-origin supports the <position> grammar https://drafts.csswg.org/css-transforms-2/#perspective-origin-property https://drafts.csswg.org/css-values-4/#typedef-position and not the additional forms allowed by the <bg-position> grammar https://drafts.csswg.org/css-backgrounds-3/#propdef-background-position Blink has deprecated <bg-position> support in perspective-origin (and other contexts other than background-position), so the expected failures are while we wait for removal in M68. BUG=804187 Change-Id: I9e93af5a5af0975fca82aadd4485c601c439969f Reviewed-on: https://chromium-review.googlesource.com/895222 Commit-Queue: Eric Willigers <ericwilligers@chromium.org> Reviewed-by:
nainar <nainar@chromium.org> Cr-Commit-Position: refs/heads/master@{#533258}
-
Roman Sorokin authored
https://chromium.googlesource.com/chromiumos/platform/system_api.git/+log/55af1ecf9588..03017732129d $ git log 55af1ecf9..030177321 --date=short --no-merges --format='%ad %ae %s' 2018-01-25 ljusten authpolicy: Add domain join errors 2018-01-23 allenvic smbprovider: Add WriteFile protobuf 2017-12-19 igorcov system_api: D-Bus constant for TpmAttestationGetEnrollmentId 2018-01-24 ljusten Remove deprecated AuthPolicy D-Bus method names 2018-01-21 ljusten authpolicy: Add ERROR_NO_WINDOWS_POLICY Created with: roll-dep src/third_party/cros_system_api BUG=chromium:805908 Change-Id: I87859bf3e03d9c3668d731041317b31379a7a1e0 Reviewed-on: https://chromium-review.googlesource.com/893271Reviewed-by:
Lutz Justen <ljusten@chromium.org> Commit-Queue: Roman Sorokin <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#533257}
-
https://chromium.googlesource.com/catapult.git/+log/7c98d04db58b..12ffa8933991 $ git log 7c98d04db..12ffa8933 --date=short --no-merges --format='%ad %ae %s' 2018-01-31 perezju [Devil] Dismiss errors in GetRecursiveDiskUsage 2018-01-25 perezju [Telemetry] Move profile setup on desktop to its possible browser 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: I349d5d5c652ff38030b5ad74c49ad136e791b421 Reviewed-on: https://chromium-review.googlesource.com/895406 Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#533256}
-
François Beaufort authored
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I042e565d27078e50ae6ac3ce01726452df3a9e2d Reviewed-on: https://chromium-review.googlesource.com/886943 Commit-Queue: Mounir Lamouri (slow) <mlamouri@chromium.org> Reviewed-by:
Mounir Lamouri (slow) <mlamouri@chromium.org> Cr-Commit-Position: refs/heads/master@{#533255}
-
tzik authored
This CL contains: - Convert MIDIOutput::pending_data_ to contain DOMUint8Array instead of Vector, so that we don't need an extra copy on the lazy open case. - Take care null or non-Document ExecutionContext. - Misc clean up. Change-Id: I33862de0aa39ddd68dc9ee5e4a594caf1e8f7437 Reviewed-on: https://chromium-review.googlesource.com/895129 Commit-Queue: Taiju Tsuiki <tzik@chromium.org> Reviewed-by:
Takashi Toyoshima <toyoshim@chromium.org> Cr-Commit-Position: refs/heads/master@{#533254}
-
https://webrtc.googlesource.com/src.git/+log/1a2f20748581..70294c8eab2f $ git log 1a2f20748..70294c8ea --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;master.tryserver.chromium.win:win-msvc-dbg TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I5c97ecb038fdb960da05336e576eb190e7418e8b Reviewed-on: https://chromium-review.googlesource.com/895284 Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
-
