- 30 Jul, 2018 40 commits
-
-
Jun Choi authored
Currently, FIDO devices that sends any other protocols other than 'FIDO_2_0' or 'U2F_V2'in response to GetInfo command is rejected. This constraint needs to be fixed so that while devices that send duplicate or empty protocol list should be rejected, any protocols that the client does not know should be ignored. Change-Id: I0a574ada22d621e891c99d313eb19c3648144638 Reviewed-on: https://chromium-review.googlesource.com/1153620 Commit-Queue: Jun Choi <hongjunchoi@chromium.org> Reviewed-by:
Jan Wilken Dörrie <jdoerrie@chromium.org> Cr-Commit-Position: refs/heads/master@{#579205}
-
Patrick Noland authored
Also adds token invalidation when we get a 401 and a test for header values being set correctly. Bug: 869132 Change-Id: I61f963bf17a89f58d10583c51eb5234daa263639 Reviewed-on: https://chromium-review.googlesource.com/1155717Reviewed-by:
Filip Gorski <fgorski@chromium.org> Commit-Queue: Patrick Noland <pnoland@chromium.org> Cr-Commit-Position: refs/heads/master@{#579204}
-
Lu Chen authored
In this CL, metrics from the renderer process are processed in the browser. We extract document level metrics (e.g., number of links), as well as derived features (e.g., area rank). The calculated navigation scores (and other info) from onLoad are stored and can be looked up when an anchor element is clicked. Bug: 850624 Change-Id: I3a7516d3a991dc278441fb925822efa780a84b8d Reviewed-on: https://chromium-review.googlesource.com/1132680Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Commit-Queue: Lu Chen <chelu@chromium.org> Cr-Commit-Position: refs/heads/master@{#579203}
-
Emircan Uysaler authored
This CL adds functionality to convert webrtc::ColorSpace info into chromium's media::VideoColorSpace and sets it in remote video receiver. Bug: 867029 Change-Id: I175fcb6eb0f7918c510b7ff4f355aa300a89473c Reviewed-on: https://chromium-review.googlesource.com/1154030 Commit-Queue: Emircan Uysaler <emircan@chromium.org> Reviewed-by:
Christian Fremerey <chfremer@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#579202}
-
Esmael El-Moslimany authored
Bug: 867193 Change-Id: I140d9b979ba7f58a3ab8e62142797caddd148f44 Reviewed-on: https://chromium-review.googlesource.com/1154195Reviewed-by:
Scott Chen <scottchen@chromium.org> Commit-Queue: Esmael El-Moslimany <aee@chromium.org> Cr-Commit-Position: refs/heads/master@{#579201}
-
Andrii Shyshkalov authored
It has been deprecated and is no longer required. R=jbudorick, mknyszek Bug: 866476 Change-Id: I78b348e6d9a9dcf078608f27853abdd9b6531df1 No-Try: True Reviewed-on: https://chromium-review.googlesource.com/1155798Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org> Cr-Commit-Position: refs/heads/master@{#579200}
-
Rouslan Solomakhin authored
Bug: 869038 Change-Id: Ib22c53fb131acdf7ba887ca21171776663a0079d Reviewed-on: https://chromium-review.googlesource.com/1155100Reviewed-by:
Ganggui Tang <gogerald@chromium.org> Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org> Cr-Commit-Position: refs/heads/master@{#579199}
-
Peter Wen authored
Add `--compile-sdk-version` flag to `generate_gradle.py` in order to allow Android Studio to find the right SDK source files. This is useful when our targetSdkVersion is on a new android version while the publicly available source code for that version is not yet available. Passing this flag with an older version number allows Android Studio to use that older version's SDK source code during editing. Bug: 620034 Change-Id: I85d3c2bb9db6d7a1f39182cc6a66d65009072c00 Reviewed-on: https://chromium-review.googlesource.com/1155482 Commit-Queue: Peter Wen <wnwen@chromium.org> Reviewed-by:
Mohamed Heikal <mheikal@chromium.org> Cr-Commit-Position: refs/heads/master@{#579198}
-
Peter Kvitek authored
Change-Id: I56bb2d9930203b0a1668b6f00b9fdcd89fcf1e3e Reviewed-on: https://chromium-review.googlesource.com/1155745Reviewed-by:
Pavel Feldman <pfeldman@chromium.org> Commit-Queue: Peter Kvitek <kvitekp@chromium.org> Cr-Commit-Position: refs/heads/master@{#579197}
-
Takuto Ikuta authored
This is a part of effort to remove /wd4018 warning suppression. Master CL is https://chromium-review.googlesource.com/c/chromium/src/+/1152755 This CL was uploaded by git cl split. R=sky@chromium.org Bug: 868248, 588506 Change-Id: Ibeb235f73e433aa9bc34dbdb7513582cf11427c8 Reviewed-on: https://chromium-review.googlesource.com/1152844Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Takuto Ikuta <tikuta@chromium.org> Cr-Commit-Position: refs/heads/master@{#579196}
-
Ryan Hamilton authored
Add a new QUIC platform API class ScopedEnvironmentForThreads which needs to be instantiated in tests which use threads. Merge internal change: 206067592 Change-Id: Id873cbe6dbd6d515571f36454375129c85ff5eba Reviewed-on: https://chromium-review.googlesource.com/1150811 Commit-Queue: Zhongyi Shi <zhongyi@chromium.org> Reviewed-by:
Zhongyi Shi <zhongyi@chromium.org> Cr-Commit-Position: refs/heads/master@{#579195}
-
Dale Curtis authored
When EME is attached, if playback is ongoing, we will attempt to recreate the WatchTimeReporter without triggering play on it again -- losing that watch time. It's unclear if this is actually a real possibility though... is EME required to be attached to start playback of even a non-encrypted stream? Or just by the time the encrypted portion needs to play? Previously this also happened for property changes, but since those have all moved into secondary property updates that don't restart the reporter, there is no issue there anymore. BUG=none TEST=none. Change-Id: Ib2c021418eb63634c59b450bf9c80810ca2dc835 Reviewed-on: https://chromium-review.googlesource.com/1148951Reviewed-by:
Xiaohan Wang <xhwang@chromium.org> Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#579194}
-
Amy Qiu authored
It's been a week since simple_mobile_sites was refreshed, remove the old pages and corresponding expectation Bug: 852530 Change-Id: I8f18f80794ae711f36215ee50b50d8bb40e7dbf9 Reviewed-on: https://chromium-review.googlesource.com/1154997Reviewed-by:
Ned Nguyen <nednguyen@google.com> Commit-Queue: Amy Qiu <amyqiu@google.com> Cr-Commit-Position: refs/heads/master@{#579193}
-
Zhenyao Mo authored
BUG=867155 TEST=manual R=crouleau@chromium.org,sunnyps@chromium.org Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Change-Id: Id5bc22f7e8452e46397dd1a47fe7b1c8d50ff915 Reviewed-on: https://chromium-review.googlesource.com/1112771Reviewed-by:
Caleb Rouleau <crouleau@chromium.org> Reviewed-by:
Sunny Sachanandani <sunnyps@chromium.org> Reviewed-by:
Bruce Dawson <brucedawson@chromium.org> Commit-Queue: Zhenyao Mo <zmo@chromium.org> Cr-Commit-Position: refs/heads/master@{#579192}
-
Matt Menke authored
This way, they don't need chrome OWNERS approval to modify them. Bug: None Change-Id: Ie4e658999973224e31fb562a14f688dd6d682fea Reviewed-on: https://chromium-review.googlesource.com/1155094 Commit-Queue: Matt Menke <mmenke@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#579191}
-
Peter Wen authored
Bug: 620034 Change-Id: I4f128cfea59bb38615adc71cd8081a74c60cc39c Reviewed-on: https://chromium-review.googlesource.com/1155731 Commit-Queue: Mohamed Heikal <mheikal@chromium.org> Reviewed-by:
Mohamed Heikal <mheikal@chromium.org> Cr-Commit-Position: refs/heads/master@{#579190}
-
Antoine Labour authored
This path seems to be causing problems on some Android phones, so disable for now. Bug: 854298 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: Ifeba070c6c7805217c76b59e7f0328f188bc5615 Reviewed-on: https://chromium-review.googlesource.com/1155472Reviewed-by:
Peng Huang <penghuang@chromium.org> Commit-Queue: Antoine Labour <piman@chromium.org> Cr-Commit-Position: refs/heads/master@{#579189}
-
pdfium-chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/8584902d81ff..d718d634b7aa git log 8584902d81ff..d718d634b7aa --date=short --no-merges --format='%ad %ae %s' 2018-07-30 tsepez@chromium.org Type-safe iteration over CXFA_ContentLayoutItems. 2018-07-30 thestig@chromium.org Fix a misspelling of "locale". 2018-07-30 thestig@chromium.org Remove a NOTREACHED() in FormValueNode_SetChildContent(). 2018-07-30 hnakashima@chromium.org Remove CFGAS_PDFFontMgr::m_FDE2PDFFont font cache. 2018-07-30 art-snake@yandex-team.ru Check maximum bit count of shared group object numbers. Created with: gclient setdep -r src/third_party/pdfium@d718d634b7aa 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. BUG=chromium:868477 TBR=dsinclair@chromium.org Change-Id: I1c8753d90baf966d4c51eb20fec35a26ca8d2778 Reviewed-on: https://chromium-review.googlesource.com/1155429Reviewed-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@{#579188}
-
Robbie McElrath authored
This migrates AutoEnrollmentClientImpl and AppInstallEventLoCollector from using net::NetworkChangeNotifier to content::NetworkConnectionTracker, which works with the network service enabled. Bug: 821009 Change-Id: I33dbd4ab0102d5a55bf34affdb7366b444e842ac Reviewed-on: https://chromium-review.googlesource.com/1147602 Commit-Queue: Robbie McElrath <rmcelrath@chromium.org> Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Cr-Commit-Position: refs/heads/master@{#579187}
-
James Cook authored
The number of shards for browser_tests on "Linux Chromium OS ASan LSan Tests (1)" was increased to 30 a while back, but not viz_browser_tests. This means viz_browser_tests often timeout on the bot. I'm upping the number of shards to be the same for the two. (sky@ recently did something similar for mash_browser_tests) BUG=794372 TEST=none Change-Id: Ibbdb086bc37e8a4722a0e5ab0eeb6312a8db4741 Reviewed-on: https://chromium-review.googlesource.com/1155634Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Commit-Queue: James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#579186}
-
Sahel Sharify authored
Bug: 868584 Change-Id: Ifa831ebeb3c7b2b86dc9cb5d56d122085eabfec1 Reviewed-on: https://chromium-review.googlesource.com/1155148 Commit-Queue: Sahel Sharify <sahel@chromium.org> Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Cr-Commit-Position: refs/heads/master@{#579185}
-
Katie D authored
Has to make callbacks optional too in order to continue to pass closure compilation. Bug: 866161 Cq-Include-Trybots: luci.chromium.try:closure_compilation Change-Id: Ie911461b0e575771708897bca30483fa9cc9f038 Reviewed-on: https://chromium-review.googlesource.com/1155643Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Commit-Queue: Katie Dektar <katie@chromium.org> Cr-Commit-Position: refs/heads/master@{#579184}
-
Joanmarie Diggs authored
The missing states already exist in the platform-independent accessibility code and are already used in the platform-specific accessibility code. They just need to be exposed via ATK. R=dmazzoni@chromium.org Bug: 868735 Test: AXPlatformNodeAuraLinuxTest.TestAtkObjectState Change-Id: I098c5e53d4a1f5cf44331847ef5790c46e1d59d7 Reviewed-on: https://chromium-review.googlesource.com/1154358 Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#579183}
-
Mustafa Emre Acer authored
This CL adds a new presubmit check to verify that new or modified translation strings have associated screenshots. It does this by parsing the modified grd/grdp file, loading the messages and comparing them with old messages. It then checks whether the corresponding screenshot file exists. See go/chrome-translation-screenshots for design details. Change-Id: I981b3a95b66e2df8eee1d2b48223251fa0ff03a7 Bug: 814899 Reviewed-on: https://chromium-review.googlesource.com/872199Reviewed-by:
Aaron Gable <agable@chromium.org> Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Commit-Queue: Mustafa Emre Acer <meacer@chromium.org> Cr-Commit-Position: refs/heads/master@{#579182}
-
Peter Collingbourne authored
This reverts commit 748ac91e. Reason for revert: Broke orderfile generation. Original change's description: > Reland "build: Enable ThinLTO in official Android builds." > > This relands commit 1ba5d611. > > Fixes chromeos build issue by checking whether we have a secondary > toolchain before comparing it with the current toolchain. > > Original change's description: > > build: Enable ThinLTO in official Android builds. > > > > With this change we start building Chromium with ThinLTO when targeting > > Android. In 64-bit Monochrome builds, the 32-bit binary is also built > > with ThinLTO. This change is expected to reduce code size significantly > > (in local measurements it reduced the size of MonochromePublic.apk by 2.3MB) > > and is a prerequisite for enabling control flow integrity in official > > builds. > > > > Note that although this change enables ThinLTO, it does not enable > > the cross-TU optimizations normally associated with LTO. Enabling > > cross-TU optimizations is a separate project. > > > > On my local machine (a Lenovo P920) libmonochrome.so link times increase > > as follows: > > > > before after (first link) after (incremental links) > > 32-bit 18s 140s 50s > > 64-bit 13s 107s 41s > > > > All known blockers have now been fixed. This CL is likely to uncover > > unknown blockers. > > > > Bug: 469376 > > Change-Id: I8981e17abd50bc5ca00440e0d74dda878c911749 > > Reviewed-on: https://chromium-review.googlesource.com/1150870 > > Commit-Queue: Peter Collingbourne <pcc@chromium.org> > > Reviewed-by: Nico Weber <thakis@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#578195} > > Bug: 469376, 868426 > Change-Id: Ie46ba0db0ac68130bc600415777de5c813b28ebd > Reviewed-on: https://chromium-review.googlesource.com/1153612 > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > Commit-Queue: Peter Collingbourne <pcc@chromium.org> > Cr-Commit-Position: refs/heads/master@{#578854} TBR=thakis@chromium.org,dpranke@chromium.org,pcc@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 469376, 867878 Change-Id: Ie25a3cb8ca94cc4e9ba3edf53833f5e495654c92 Reviewed-on: https://chromium-review.googlesource.com/1155054Reviewed-by:
Peter Collingbourne <pcc@chromium.org> Commit-Queue: Peter Collingbourne <pcc@chromium.org> Cr-Commit-Position: refs/heads/master@{#579181}
-
Weilun Shi authored
When Building the ThemeInfo, we consider both default theme and system theme(GTK on Linux) as "default" theme. Because we can only apply custom background on the "default" theme, after applying the change we can now observe presence of gear icon on the GTK theme. Before: https://screenshot.googleplex.com/824PuvixCXA.png After: https://screenshot.googleplex.com/opmnGbv2xPx.png Bug: 851035 Change-Id: I14dd9019db665c084731bec374f0ce357afd9f45 Reviewed-on: https://chromium-review.googlesource.com/1150606Reviewed-by:
Mathieu Perreault <mathp@chromium.org> Commit-Queue: Weilun Shi <sweilun@chromium.org> Cr-Commit-Position: refs/heads/master@{#579180}
-
Kyle Milka authored
Adjust scrim from 20% opacity flat to, 0% (top) – 30% (bottom) Bug: 867753 Change-Id: I9b99f511c0656b352ca0c2840e6cd829b6d27576 Reviewed-on: https://chromium-review.googlesource.com/1155256 Commit-Queue: Kyle Milka <kmilka@chromium.org> Commit-Queue: Mathieu Perreault <mathp@chromium.org> Reviewed-by:
Mathieu Perreault <mathp@chromium.org> Cr-Commit-Position: refs/heads/master@{#579179}
-
Tommy C. Li authored
The suggestions indent was updated from 48dp to 47dp in a previous CL. This CL updates the jog length from 12dp to 11dp to match that. Bug: 868157 Change-Id: Ief7e64861e2a35fa2711209728c6078cb249c61d Reviewed-on: https://chromium-review.googlesource.com/1155386Reviewed-by:
Justin Donnelly <jdonnelly@chromium.org> Commit-Queue: Tommy Li <tommycli@chromium.org> Cr-Commit-Position: refs/heads/master@{#579178}
-
Dan Sanders authored
If the parent thread is the same as the gpu thread, these tests were incorrect, allowing work to be done after Destroy(). Now that Windows is running the media InterfaceFactory on the GPU main thread, this causes use-after-free of |media_log_|. Bug: 868760 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: I70dbeafe6744f721ef0eb407f43481095b7df3a5 Reviewed-on: https://chromium-review.googlesource.com/1155469Reviewed-by:
Frank Liberato <liberato@chromium.org> Commit-Queue: Dan Sanders <sandersd@chromium.org> Cr-Commit-Position: refs/heads/master@{#579177}
-
Peter Kasting authored
This was supposed to have been in https://chromium-review.googlesource.com/c/chromium/src/+/1152522 . Bug: 866672 Change-Id: I4b2076e13b1dc0ae2db0eec51775fb80790b90d7 TBR: estade Reviewed-on: https://chromium-review.googlesource.com/1155486Reviewed-by:
Peter Kasting <pkasting@chromium.org> Commit-Queue: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#579176}
-
Erik Luo authored
Simplify visible index calculation and tests by - Remove padding on viewport container - Remove negative margin (was on error/warning logs) Improve visible index / scrollItemIntoView() precision by - Rebuild cumulative heights even if each message is slightly off - No need to scroll last item into view if it is fully visible - Perform extra scroll on scroll into view in case items above were larger than expected - Message height measurements now include wrapper's border Bug: 865674 Change-Id: Id4abad0e40a971dff9accbc7b904427ea02f728c Reviewed-on: https://chromium-review.googlesource.com/1144254 Commit-Queue: Erik Luo <luoe@chromium.org> Reviewed-by:
Andrey Lushnikov <lushnikov@chromium.org> Cr-Commit-Position: refs/heads/master@{#579175}
-
Peter Boström authored
virtual/gpu-rasterization/images/color-profile-image-filter-all.html is flaky and times out occasionally. Bug: chromium:866166 Change-Id: Ib966574467cdb6e34ffef4f8f3323f11228b0a2c Reviewed-on: https://chromium-review.googlesource.com/1155638 Commit-Queue: Peter Boström <pbos@chromium.org> Reviewed-by:
Roger Tawa <rogerta@chromium.org> Cr-Commit-Position: refs/heads/master@{#579174}
-
angle-chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/e452382a61a1..67c388e6c04e git log e452382a61a1..67c388e6c04e --date=short --no-merges --format='%ad %ae %s' 2018-07-30 fjhenigman@chromium.org Vulkan: support GL_FIXED vertex data. Created with: gclient setdep -r src/third_party/angle@67c388e6c04e 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=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=fjhenigman@chromium.org Change-Id: I119b51f30ea0e12db5dd4264b2bfa1d5be121043 Reviewed-on: https://chromium-review.googlesource.com/1155074Reviewed-by:
angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#579173}
-
Weilun Shi authored
Setting all the attributions to empty string for all the images in the 'Solid Colors' collection. Therefore, attributions will no longer show for the them. Notice that, this change will not affect the 'Solid Color' image that already applied. To make it work, one should either open a new profile or change the background image and then change it back. Before: https://screenshot.googleplex.com/AQbWxLqi7UD.png After: https://screenshot.googleplex.com/0PFpVvCU4QC.png Bug: 868164 Change-Id: Ie5b8b416ba6ed0fedbc9ce5d19e18b67f410f0f4 Reviewed-on: https://chromium-review.googlesource.com/1152534 Commit-Queue: Mathieu Perreault <mathp@chromium.org> Reviewed-by:
Mathieu Perreault <mathp@chromium.org> Cr-Commit-Position: refs/heads/master@{#579172}
-
Penny MacNeil authored
Change-Id: Ia94594d1970b8bbe7ff669bd51fd3c9842392ced Reviewed-on: https://chromium-review.googlesource.com/1155161Reviewed-by:
Will Harris <wfh@chromium.org> Commit-Queue: Penny MacNeil <pennymac@chromium.org> Cr-Commit-Position: refs/heads/master@{#579171}
-
Nasko Oskov authored
This reverts commit 461c6510. Reason for revert: <INSERT REASONING HERE> Original change's description: > Eanble WebNavigationApiTest.Failures test. > > This test was likely flaky due to a race condition in navigation code, > which has now been fixed. Let's try to enable it and see if the fix has > helped deflake this test. > > Bug: 477840, 746407 > Change-Id: Ib1d449dd34c2d6044a60da38f03ac548179d475c > Reviewed-on: https://chromium-review.googlesource.com/1153221 > Reviewed-by: Alex Moshchuk <alexmos@chromium.org> > Commit-Queue: Nasko Oskov <nasko@chromium.org> > Cr-Commit-Position: refs/heads/master@{#578836} TBR=nasko@chromium.org,alexmos@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 477840, 746407 Change-Id: I553fa362ace34616cc34c496190e5b0c57bfd846 Reviewed-on: https://chromium-review.googlesource.com/1155490Reviewed-by:
Nasko Oskov <nasko@chromium.org> Commit-Queue: Nasko Oskov <nasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#579170}
-
Moe Ahmadi authored
Exisitng behavior is inconsistent with the Sync Settings switches and can caused confusion in the redesigned Autofill Settings where turning the master on/off enables/disables the addresses and credit cards toggles. Bug:865476 Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: I6d2afcb0a24de95b4eb1141ec42699f18733bfe3 Reviewed-on: https://chromium-review.googlesource.com/1143591 Commit-Queue: Moe Ahmadi <mahmadi@chromium.org> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Cr-Commit-Position: refs/heads/master@{#579169}
-
Jordy Greenblatt authored
The new unified setup project for multi device features involved consolidating the infrastructure for all the existing features (Instant Tethering, SmartLock) as well as the infrastructure for features that are not fully built (Android Messages). ------- This is a screenshot of the console showing the pref https://drive.google.com/open?id=0B1-cJJPK-cu6OGxTQnNLMEFHWDhibXJOSVJwclBoVGlFRF84 Change-Id: I7cedd5c9b7608ddea4f3914b1c0eb11f1ea1c7d3 Bug: 824568 Reviewed-on: https://chromium-review.googlesource.com/1154032Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Reviewed-by:
Bernhard Bauer <bauerb@chromium.org> Reviewed-by:
Michael Giuffrida <michaelpg@chromium.org> Reviewed-by:
Luis Hector Chavez <lhchavez@chromium.org> Commit-Queue: Jordy Greenblatt <jordynass@chromium.org> Cr-Commit-Position: refs/heads/master@{#579168}
-
Stephen Martinis authored
This allows for a smoother rename. The previous attempt at this (https://chromium-review.googlesource.com/c/chromium/src/+/1153616) caused the bot to show some errors. This is because the services which rely on the configs in //infra/config have a ~10 minute lag, so while those services were picking up the new configs, the existing builder configs (with old names), couldn't find themselves in any config files. This CL adds the new names, which will coexist alongside the old names. This means the 10 minute lag doesn't matter anymore, since both names are valid everywhere. Bug: 867725 Change-Id: Ic61f81c40c40d3c150bb53c39c88bcc2ee3f98c1 Reviewed-on: https://chromium-review.googlesource.com/1155263 Commit-Queue: Stephen Martinis <martiniss@chromium.org> Reviewed-by:
John Budorick <jbudorick@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#579167}
-
Sahel Sharify authored
This reverts commit 7cb247dd. Reason for revert: Check to see if the crash report in crbug.com/868849 goes away or not. Original change's description: > Clean up DidStopFlinging IPC > > This cl also removes TouchscreenFlingInProgress function that is no > longer needed. > > Bug: 249063 > Change-Id: Icc939d654cdfe0cf38c843933f2fd469f843b74c > Reviewed-on: https://chromium-review.googlesource.com/1145784 > Reviewed-by: Dave Tapuska <dtapuska@chromium.org> > Reviewed-by: Ken Buchanan <kenrb@chromium.org> > Reviewed-by: Philip Rogers <pdr@chromium.org> > Commit-Queue: Sahel Sharify <sahel@chromium.org> > Cr-Commit-Position: refs/heads/master@{#578410} TBR=kenrb@chromium.org,pdr@chromium.org,dtapuska@chromium.org,sahel@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 249063 Change-Id: Iee7200d3c4e388fccbc2dc6b86997a07a3a03f0a Reviewed-on: https://chromium-review.googlesource.com/1155169Reviewed-by:
Sahel Sharify <sahel@chromium.org> Commit-Queue: Sahel Sharify <sahel@chromium.org> Cr-Commit-Position: refs/heads/master@{#579166}
-