- 19 Jun, 2018 40 commits
-
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/63b3bfb711d7..5045e501d2ae git log 63b3bfb711d7..5045e501d2ae --date=short --no-merges --format='%ad %ae %s' 2018-06-19 mtklein@google.com Revert "Change how vertex/instance attributes are handled in geometry processors." Created with: gclient setdep -r src/third_party/skia@5045e501d2ae 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=kjlubick@chromium.org Change-Id: I2dd1d66f0f2fd063b96db11b229effd067f5a949 Reviewed-on: https://chromium-review.googlesource.com/1105419Reviewed-by:
skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#568342}
-
Andrey Lushnikov authored
This patch starts creating execution contexts for iframes that didn't commit initial successful loading. This is a common situation for iframes which navigation was blocked due to mixed content. R=dgozman BUG=854051 Change-Id: Ia1c39af39c1c99f20e69abfae48579ac1bc09021 Reviewed-on: https://chromium-review.googlesource.com/1102154 Commit-Queue: Andrey Lushnikov <lushnikov@chromium.org> Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#568341}
-
Ryan Hansberry authored
This method is unnecessary; if clients wish to disconnect a ClientChannel, they simply need to delete the object. Bug: 824568, 752273 Change-Id: I5ba7268743f8aabb208bc4add9ed849a982c7465 Reviewed-on: https://chromium-review.googlesource.com/1105609Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Commit-Queue: Ryan Hansberry <hansberry@chromium.org> Cr-Commit-Position: refs/heads/master@{#568340}
-
Sam McNally authored
Bug: 848126 Change-Id: Ifd3cf1996fdb33f5d0d93f5c5cf721abd5440d29 Reviewed-on: https://chromium-review.googlesource.com/1102279Reviewed-by:
Noel Gordon <noel@chromium.org> Commit-Queue: Sam McNally <sammc@chromium.org> Cr-Commit-Position: refs/heads/master@{#568339}
-
Giovanni Ortuño Urquidi authored
TBR=alancutter@chromium.org NOTRY=true Bug: 854053 Change-Id: Ie4264d2c95790c028a3054a385975a8c49192ed0 Reviewed-on: https://chromium-review.googlesource.com/1105525Reviewed-by:
Giovanni Ortuño Urquidi <ortuno@chromium.org> Commit-Queue: Giovanni Ortuño Urquidi <ortuno@chromium.org> Cr-Commit-Position: refs/heads/master@{#568338}
-
Fady Samuel authored
We eventually want to get rid of the notion of content source ID in favor of surface synchronization. In order to do this, we need to introduce an explicit API to clear caches in cc. This CL introduces LayerTreeHost::ClearCachesOnNextCommit API. Bug: 672962 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel Change-Id: Ib78a5e7dde17f335c1e591032f7e01c1fa9213f9 Reviewed-on: https://chromium-review.googlesource.com/1105343Reviewed-by:
Antoine Labour <piman@chromium.org> Reviewed-by:
Khushal <khushalsagar@chromium.org> Commit-Queue: Fady Samuel <fsamuel@chromium.org> Cr-Commit-Position: refs/heads/master@{#568337}
-
Sasha Morrissey authored
Without this patch, shouldShowTeamDrives_ calls |callback| synchronously when the --team-drives flag is disabled, and asynchronously if it is enabled. The asynchronous call causes the navigation tree to updated after the appropriate update methods are called, which causes undefined behaviour. This patch moves the check for Team Drives into an asynchronous function called *after* the tree has been synchronously initialized, and simply shows the element if the user has Team Drives (originally, it hid the element, but this means the item may be visible for a split-second. To fix this, it is added as a hidden element by default and then unhidden after the check). This also fixes the existing integration tests to work with the --team-drives flag enabled. Bug: 849497 Cq-Include-Trybots: luci.chromium.try:closure_compilation Change-Id: Ie8e174995ca8b16371f32e8ab780f45748fcc55e Reviewed-on: https://chromium-review.googlesource.com/1103983 Commit-Queue: Sasha Morrissey <sashab@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#568336}
-
Sam McNally authored
Update the getDriveConnectionStatus() and getSizeStats() implementations, the file manager EventRouter, and the test fake to function correctly when only DriveFS is enabled. Also update the test fakes to handle mount-relative absolute paths sent over mojo. Bug: 844292, 848126 Change-Id: I6f98d6bb3d00a9fcc4b26cd1090c2fa06ecf33e3 Reviewed-on: https://chromium-review.googlesource.com/1102234Reviewed-by:
Sasha Morrissey <sashab@chromium.org> Commit-Queue: Sam McNally <sammc@chromium.org> Cr-Commit-Position: refs/heads/master@{#568335}
-
Jun Choi authored
After connecting to Cable authenticator using advertisement/scanning, Cable protocol requires one more round trip of BLE control messages to be sent to establish shared secret key for encryption. Add this handshake protocol to FidoCableDiscovery. Bug: 849307 Change-Id: I388fa43dae60e97e027dafa1f9f430a2569ca981 Reviewed-on: https://chromium-review.googlesource.com/1089794 Commit-Queue: Jun Choi <hongjunchoi@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Jan Wilken Dörrie <jdoerrie@chromium.org> Cr-Commit-Position: refs/heads/master@{#568334}
-
Carlos Knippschild authored
Now also logging the offline_id. TBR=johnchen@chromium.org Bug: 852616 Change-Id: Ic28d9a59da5ff81b0da7b640044799fad4538b71 Reviewed-on: https://chromium-review.googlesource.com/1105566Reviewed-by:
Carlos Knippschild <carlosk@chromium.org> Commit-Queue: Carlos Knippschild <carlosk@chromium.org> Cr-Commit-Position: refs/heads/master@{#568333}
-
Karan Bhatia authored
With Declarative Net Request, there is no easy way for extensions to collapse the DOM elements corresponding to the resources they blocked. This CL implements the ability for the blocked <img> elements to be automatically collapsed in the DOM. In subsequent CLs, similar function will be implemented for other DOM elements. To do this, following changes are made: - A new field called kCollapsedByClient is added to blink::ResourceRequestBlockedReason. Whenever an extension ruleset wants to collapse the DOM element corresponding to a network request, the extended_error_code is set to kCollapsedByClient, which is then used as a signal by the renderer to perform the collapsing. - Changes to blink::ResourceRequestBlockedReason also necessiate changes to the Devtools protocol. As a good side-effect, resources collapsed by extensions would be marked as "collapsed-by-client" by Devtools. - Changes are made to allow content embedders to set a blink::ResourceRequestBlockedReason for a request. BUG=848842 Cq-Include-Trybots: luci.chromium.try:linux_mojo Change-Id: I0bfd1a60bee79ef651741b7655fade6be4a7d419 Reviewed-on: https://chromium-review.googlesource.com/1088189 Commit-Queue: Matt Menke <mmenke@chromium.org> Reviewed-by:
Istiaque Ahmed <lazyboy@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Reviewed-by:
Nate Chapin <japhet@chromium.org> Reviewed-by:
Andrey Kosyakov <caseq@chromium.org> Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#568332}
-
Alex Newcomer authored
Only the most recent notification will be shown. Adding a few new components: - NotificationMenuController - Handles adding/removing the container MenuItemView to an app context menu, and passing notification data to NotificationMenuView. - NotificationMenuView - Handles showing NotificationItemViews, showing the proper notifications, and in the future showing the overflow area. - NotificationItemView - Shows basic notification data. - NotificationMenuHeaderView - Shows "Notifications" text and a counter showing the number of notifications. Please see the design doc and spec, linked in the code review request. Bug: 801015 Change-Id: I907794db5bcf90e5238773ca7cf9978d539b0855 Reviewed-on: https://chromium-review.googlesource.com/1095431 Commit-Queue: Alex Newcomer <newcomer@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#568331}
-
Kyle Horimoto authored
This class declared its constructor and destructor but did not actually implement them. This CL implements them. Additionally, this CL adds a "destructor callback" as an optional constructor parameter and invokes the callback in the destructor. Bug: 824568, 752273 Change-Id: I0c60a0bc64ade3b55b926bc864c20c6ea4814d7b Reviewed-on: https://chromium-review.googlesource.com/1105306 Commit-Queue: Kyle Horimoto <khorimoto@chromium.org> Reviewed-by:
Ryan Hansberry <hansberry@chromium.org> Cr-Commit-Position: refs/heads/master@{#568330}
-
Istiaque Ahmed authored
Using OnceCallback+std::move would remove the necessity of using base::ResetAndReturn. Bug: None Change-Id: I38a3d945f03ad5abc3d12f13b55c92b1b66d3860 Reviewed-on: https://chromium-review.googlesource.com/1105509Reviewed-by:
Sam McNally <sammc@chromium.org> Commit-Queue: Istiaque Ahmed <lazyboy@chromium.org> Cr-Commit-Position: refs/heads/master@{#568329}
-
Sasha Morrissey authored
Change ShortcutItem to set the 'label' attribute of an element, so that the FolderShortcuts test can select these elements, with a TODO to remove later. This is the fastest way to fix the integration tests to work when team drives is enabled (and the IDs move around). This also makes the tests robust against more directories being added to the top- level tree. Other approaches considered: (1) Add a getIdForTreeElementWithName method to background/js/test_util.js. This doesn't work with waitForElement() since calling it beforehand fails immediately when the element doesn't exist. Adding a waitForElementInTreeWithName() could work, but you would need both methods, and adding waitFor*() methods is a bit tricky to write. (2) Use :nth-child selectors. This doesn't work because shortcuts are added in alphabetical order, meaning new shortcuts added might invalidate previous selectors. So the selectors aren't static. (3) Pass the expected index of the shortcut into each method call. This works for all methods except ones involving Drive, which use a slightly different selector. Also, for methods like removeShortcut(), it's impossible to tell whether the item has been removed (since all the elements shift up by 1, the shortcut at this index is now just the next shortcut in the list). (4) Keep track of the shortcut state in the test, and predict the indexes based on that. This is harder to do, and requires a nontrivial test rewrite. Bug: 849497 Cq-Include-Trybots: luci.chromium.try:closure_compilation Change-Id: Id26c559ea893491cf942b19a874fee29bde79534 Reviewed-on: https://chromium-review.googlesource.com/1103434Reviewed-by:
Noel Gordon <noel@chromium.org> Commit-Queue: Sasha Morrissey <sashab@chromium.org> Cr-Commit-Position: refs/heads/master@{#568328}
-
Steven Bennetts authored
This CL eliminates: * disable-network-settings-config * networkSettingsConfig * NetworkConfigView and related unused classes This also cleans up some stale comments and related interfaces. Bug: 848090 Cq-Include-Trybots: luci.chromium.try:closure_compilation Change-Id: Id79b835f72b79694d7013cf19a17d553622f844b Reviewed-on: https://chromium-review.googlesource.com/1102912 Commit-Queue: Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
Toni Barzic <tbarzic@chromium.org> Cr-Commit-Position: refs/heads/master@{#568327}
-
Peter Kasting authored
* More consistent names * Move initializers to .h * Remove using directives BUG=none TEST=none Change-Id: I52939db0418f50d3cef9c1ab92a04a79c326a9b9 Reviewed-on: https://chromium-review.googlesource.com/1094256Reviewed-by:
Robert Flack <flackr@chromium.org> Reviewed-by:
Michael Wasserman <msw@chromium.org> Commit-Queue: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#568326}
-
Clark DuVall authored
This matches the behavior in ChromeNetworkDelegate. Third party cookie handling has been moved from NetworkContext to CookieManager. Note: A lot of these files changed are removing the unnecessary CookieOptions arg from a bunch of methods. Bug: 789636, 789632 Cq-Include-Trybots: luci.chromium.try:linux_mojo Change-Id: I241cb396e588c433cf723c1effa8ea2c64f72266 Reviewed-on: https://chromium-review.googlesource.com/1100105 Commit-Queue: Clark DuVall <cduvall@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Christian Dullweber <dullweber@chromium.org> Cr-Commit-Position: refs/heads/master@{#568325}
-
Tetsui Ohkubo authored
We should explicitly close UnifiedSystemTray when the settings button is clicked. TEST=manual BUG=853610 Change-Id: I029396b33a3bdde0d64e5b89a01c53ba38e72f96 Reviewed-on: https://chromium-review.googlesource.com/1103436Reviewed-by:
Yoshiki Iguchi <yoshiki@chromium.org> Commit-Queue: Tetsui Ohkubo <tetsui@chromium.org> Cr-Commit-Position: refs/heads/master@{#568324}
-
Stuart Langley authored
We need to know the team_drive_id so that the FileChange observers can add or remove team drive change list loaders. Bug: 715355 Change-Id: Ie6185554c9a8b444913d1edb067530651b436a21 Reviewed-on: https://chromium-review.googlesource.com/1104625 Commit-Queue: Stuart Langley <slangley@chromium.org> Reviewed-by:
Sasha Morrissey <sashab@chromium.org> Cr-Commit-Position: refs/heads/master@{#568323}
-
Ke He authored
This is one step of "moving //device/geolocation into //services". BUG=800659 Change-Id: I041329923b2cbedab1afd51cc865b278a6a1523a Reviewed-on: https://chromium-review.googlesource.com/1100694Reviewed-by:
Ben Chan <benchan@chromium.org> Reviewed-by:
Ken Rockot <rockot@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Commit-Queue: Ke He <ke.he@intel.com> Cr-Commit-Position: refs/heads/master@{#568322}
-
junweifu authored
Split the provider in order to support Vision Framework [1] which recognizes barcode symbologies more than Core Image Framework. Split original large CL[2] up in smaller subpatches including this CL. [1] https://developer.apple.com/documentation/vision [2] https://chromium-review.googlesource.com/c/chromium/src/+/1088466 BUG=848182 Change-Id: I1bc9f1d898e34a04d819db9f90bd88d725b3601e Reviewed-on: https://chromium-review.googlesource.com/1088321Reviewed-by:
Reilly Grant <reillyg@chromium.org> Reviewed-by:
Miguel Casas <mcasas@chromium.org> Commit-Queue: Junwei Fu <junwei.fu@intel.com> Cr-Commit-Position: refs/heads/master@{#568321}
-
Giovanni Ortuño Urquidi authored
This reverts commit 9a7643de. Reason for revert: MediaRouterElementsBrowserTest.MediaRouterContainerFilterPart1 became flaky in Mac10.11, 10.12, and 10.13 after this landed. https://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=MediaRouterElementsBrowserTest.MediaRouterContainerFilterPart1 https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac10.12%20Tests/13846 [ RUN ] MediaRouterElementsBrowserTest.MediaRouterContainerFilterPart1 [35158:6151:0618/184304.560701:WARNING:notification_platform_bridge_mac.mm(510)] AlertNotificationService: XPC connection invalidated. [35158:775:0618/184305.696851:WARNING:CONSOLE(0)] "Styling master document from stylesheets defined in HTML Imports is deprecated. Please refer to https://goo.gl/EGXzpw for possible migration paths.", source: (0) [35158:775:0618/184306.249427:INFO:CONSOLE(1236)] "Running TestCase MediaRouterElementsBrowserTest.MAYBE_MediaRouterContainerFilterPart1", source: file:///b/s/w/ir/chrome/test/data/webui/test_api.js (1236) [35158:775:0618/184306.545042:WARNING:CONSOLE(16)] "Invalid keyframe value for property marginBottom: 44", source: chrome://resources/polymer/v1_0/web-animations-js/web-animations-next-lite.min.js (16) [35158:775:0618/184306.545170:WARNING:CONSOLE(16)] "Invalid keyframe value for property marginBottom: 44", source: chrome://resources/polymer/v1_0/web-animations-js/web-animations-next-lite.min.js (16) [35158:775:0618/184306.602655:ERROR:CONSOLE(48)] "Mocha test failed: MediaRouterContainerFilterPart1 focus sink search input Error: Script error. (:0) ", source: file:///b/s/w/ir/chrome/test/data/webui/mocha_adapter.js (48) [35158:775:0618/184306.602796:ERROR:CONSOLE(206)] "Uncaught AssertionError: expected 'sink-list' to equal 'filter'", source: file:///b/s/w/ir/third_party/chaijs/chai.js (206) [35158:775:0618/184306.688827:WARNING:CONSOLE(16)] "Invalid keyframe value for property marginBottom: 44", source: chrome://resources/polymer/v1_0/web-animations-js/web-animations-next-lite.min.js (16) [35158:775:0618/184306.688978:WARNING:CONSOLE(16)] "Invalid keyframe value for property marginBottom: 44", source: chrome://resources/polymer/v1_0/web-animations-js/web-animations-next-lite.min.js (16) [35158:775:0618/184306.878527:WARNING:CONSOLE(16)] "Invalid keyframe value for property marginBottom: 44", source: chrome://resources/polymer/v1_0/web-animations-js/web-animations-next-lite.min.js (16) [35158:775:0618/184306.878646:WARNING:CONSOLE(16)] "Invalid keyframe value for property marginBottom: 44", source: chrome://resources/polymer/v1_0/web-animations-js/web-animations-next-lite.min.js (16) [35158:775:0618/184307.420478:WARNING:CONSOLE(16)] "Invalid keyframe value for property marginBottom: 44", source: chrome://resources/polymer/v1_0/web-animations-js/web-animations-next-lite.min.js (16) [35158:775:0618/184307.420605:WARNING:CONSOLE(16)] "Invalid keyframe value for property marginBottom: 44", source: chrome://resources/polymer/v1_0/web-animations-js/web-animations-next-lite.min.js (16) [35158:775:0618/184308.705393:WARNING:CONSOLE(16)] "Invalid keyframe value for property marginBottom: 44", source: chrome://resources/polymer/v1_0/web-animations-js/web-animations-next-lite.min.js (16) [35158:775:0618/184308.705526:WARNING:CONSOLE(16)] "Invalid keyframe value for property marginBottom: 44", source: chrome://resources/polymer/v1_0/web-animations-js/web-animations-next-lite.min.js (16) [35158:775:0618/184308.710999:WARNING:CONSOLE(16)] "Invalid keyframe value for property marginBottom: 44", source: chrome://resources/polymer/v1_0/web-animations-js/web-animations-next-lite.min.js (16) [35158:775:0618/184308.711145:WARNING:CONSOLE(16)] "Invalid keyframe value for property marginBottom: 44", source: chrome://resources/polymer/v1_0/web-animations-js/web-animations-next-lite.min.js (16) [35158:775:0618/184308.845267:WARNING:CONSOLE(16)] "Invalid keyframe value for property marginBottom: 44", source: chrome://resources/polymer/v1_0/web-animations-js/web-animations-next-lite.min.js (16) [35158:775:0618/184308.845353:WARNING:CONSOLE(16)] "Invalid keyframe value for property marginBottom: 44", source: chrome://resources/polymer/v1_0/web-animations-js/web-animations-next-lite.min.js (16) [35158:775:0618/184308.850290:ERROR:web_ui_test_handler.cc(100)] Test Errors: 1/12 tests had failed assertions. Original change's description: > WebUI[MD-refresh]: replace most paper-input with cr-inputs > > This CL replaces most paper-inputs with cr-inputs within the code-base. > After this CL, the 3 places that still has paper-input remaining are: > - chrome/browser/resources/chromeos/login/ > - chrome/browser/resources/pdf/ > - ui/file_manager/ > > There are planned follow-up CLs to replace paper-input in the above 3 > areas as well. > > Bug: 832177 > Cq-Include-Trybots: luci.chromium.try:closure_compilation > Change-Id: I7acc7e0a26a6bd3d40ec6828608717fd97bd0c73 > Reviewed-on: https://chromium-review.googlesource.com/1086357 > Commit-Queue: Scott Chen <scottchen@chromium.org> > Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org> > Cr-Commit-Position: refs/heads/master@{#568241} TBR=dpapad@chromium.org,scottchen@chromium.org Change-Id: I1dd101893378c8354c48e72d9f56231ec1ee9850 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 832177 Cq-Include-Trybots: luci.chromium.try:closure_compilation Reviewed-on: https://chromium-review.googlesource.com/1105207Reviewed-by:
Giovanni Ortuño Urquidi <ortuno@chromium.org> Commit-Queue: Giovanni Ortuño Urquidi <ortuno@chromium.org> Cr-Commit-Position: refs/heads/master@{#568320}
-
Findit authored
This reverts commit 502b5a8a. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 568293 as the culprit for failures in the build cycles as shown on: https://findit-for-me.appspot.com/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtLzUwMmI1YThhM2I5YmNlOWYyYTVkY2E4M2NhMzRiMGM4YjExMTFlMDkM Sample Failed Build: https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-dbg/6372 Sample Failed Step: compile Original change's description: > [Fuchsia, ozone] Implement ScenicWindow > > ScenicWindow now creates View and listens to input events (mouse and keyboard). > > Bug: 829980 > Change-Id: If5d05bf1107fec553aecf2537fd197d177d2fbb1 > Reviewed-on: https://chromium-review.googlesource.com/1081609 > Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> > Reviewed-by: Robert Kroeger <rjkroege@chromium.org> > Reviewed-by: Scott Violet <sky@chromium.org> > Reviewed-by: Wez <wez@chromium.org> > Cr-Commit-Position: refs/heads/master@{#568293} Change-Id: I79c4bcd4615d058aa4080d01c9a3107ab8835bc3 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 829980 Reviewed-on: https://chromium-review.googlesource.com/1105440 Cr-Commit-Position: refs/heads/master@{#568319}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=mmoss@chromium.org Change-Id: I52a27cbd660bb0ee4dada66ffe1a7334911b5091 Reviewed-on: https://chromium-review.googlesource.com/1105521Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#568318}
-
Andrew Luo authored
Bug: 838650 Change-Id: I9850ab16c61592bf46068c2948535ab9b95d843c Reviewed-on: https://chromium-review.googlesource.com/1099566Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: Andrew Luo <aluo@chromium.org> Cr-Commit-Position: refs/heads/master@{#568317}
-
Xiaohan Wang authored
For now this is used as the flag to enable hardware secure decryption support on Windows while it's still under development. Added a TODO to apply this flag to Android and ChromeOS where hardware secure decryption is already supported. Bug: 848532 Test: No functionality change. Change-Id: Ie263008ace5f8da5da1ab94acf22485046a79b7d Reviewed-on: https://chromium-review.googlesource.com/1103283 Commit-Queue: Xiaohan Wang <xhwang@chromium.org> Reviewed-by:
John Rummell <jrummell@chromium.org> Cr-Commit-Position: refs/heads/master@{#568316}
-
Kyle Horimoto authored
This class generates BleInitiatorOperations. Bug: 824568, 752273 Change-Id: Ia99da736b4ace4de27a1bbeb61a39e99e66805bc Reviewed-on: https://chromium-review.googlesource.com/1103544 Commit-Queue: Kyle Horimoto <khorimoto@chromium.org> Reviewed-by:
Ryan Hansberry <hansberry@chromium.org> Cr-Commit-Position: refs/heads/master@{#568315}
-
Antoine Labour authored
It only returns true after a noop in production. We do not have current plans to have it do something else, as previous attempts at GPU-side memory management have failed. Bug: None 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: I6a4c2eb28754e1e58e082e057e9f260c441f4b23 Reviewed-on: https://chromium-review.googlesource.com/1105483Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Commit-Queue: Antoine Labour <piman@chromium.org> Cr-Commit-Position: refs/heads/master@{#568314}
-
Nick Harper authored
TBR=estark@chromium.org Change-Id: I0cc7108fa3379693ba90d28b96cbc806fa64c7a7 Reviewed-on: https://chromium-review.googlesource.com/1105478Reviewed-by:
Nick Harper <nharper@chromium.org> Commit-Queue: Nick Harper <nharper@chromium.org> Cr-Commit-Position: refs/heads/master@{#568313}
-
Tetsui Ohkubo authored
This CL replaces UI strings of Network feature pod button in UnifiedSystemTray. TEST=manual BUG=813499 Change-Id: I1c6b4bbf2fc5e5441eed5c88123f32b58fa0df9e Reviewed-on: https://chromium-review.googlesource.com/1103996Reviewed-by:
Yoshiki Iguchi <yoshiki@chromium.org> Commit-Queue: Tetsui Ohkubo <tetsui@chromium.org> Cr-Commit-Position: refs/heads/master@{#568312}
-
Kent Tamura authored
node.h is used in 4,700+ compilation units, and this CL reduces its estimated expanded size from 3.47MB to 2.58MB. Node depended on enum blink::MutationObserver::MutationType. This CL makes it to blink::MutationType, and moves it out from mutation_observer.h. Also, NodeMutationObserverData in node_rare_data.h depended on mutation_observer_registration.h. This CL moves member functions of NodeMutationObserverData from node_rare_data.h to node_rare_data.cc to remove #include mutation_observer_registration.h. Bug: 242216 Change-Id: I7a603bda1442dedc45674daab1b5d8f5b369f123 Reviewed-on: https://chromium-review.googlesource.com/1102291Reviewed-by:
Hayato Ito <hayato@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#568311}
-
Xiangjun Zhang authored
Add the audio mirroring client side code for Mirroring Service. Bug: 734672 Change-Id: I2a503fb5a059861a9cc4aa190a80134876eade4b Reviewed-on: https://chromium-review.googlesource.com/1083626 Commit-Queue: Xiangjun Zhang <xjz@chromium.org> Reviewed-by:
Yuri Wiitala <miu@chromium.org> Cr-Commit-Position: refs/heads/master@{#568310}
-
Peter Boström authored
We haven't been able to figure out why profiles outside the user data directory make any sense whatsoever. It seems more reasonable to reject or sanitize this directory path than taking it into account when trying to spawn the profile switcher. Bug: chromium:849912 Change-Id: I8386bee829c95ff6450b676d39091adf7bfad9d6 Reviewed-on: https://chromium-review.googlesource.com/1105495Reviewed-by:
Bret Sepulveda <bsep@chromium.org> Commit-Queue: Peter Boström <pbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#568309}
-
Adolfo Victoria authored
Allows administrators to set time intervals in which the managed devices should not check for updates. Unless the updates are forced. BUG=chromium:852860 TEST=Tested locally and used unit tests CQ-DEPEND=CL:1097698 Change-Id: Ibd9ff26fb537a966f86d9a824845fa4cf7f92d8e Reviewed-on: https://chromium-review.googlesource.com/1097990 Commit-Queue: Adolfo Higueros <adokar@google.com> Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Cr-Commit-Position: refs/heads/master@{#568308}
-
Kent Tamura authored
execution_context.h is used in 4,800+ compilation units, and this CL reduces its estimated expanded size from 3.17MB to 1.95MB. This CL removes #includes for single_thread_task_runner.h, security_context.h, and kurl.h from execution_context.h. Bug: 242216 Change-Id: I2e37b1c58902a58ba3370c26a5a38513ca1e3cbc Reviewed-on: https://chromium-review.googlesource.com/1102293Reviewed-by:
Hayato Ito <hayato@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#568307}
-
Mathieu Perreault authored
According to designers and internal spec (https://goo.gl/oRp6PA), some colors are a shade lighter. Bug: 850571 Test: Visual Change-Id: I2c593ed0019c9497873f0f8efa42b592e187d89b Reviewed-on: https://chromium-review.googlesource.com/1099687 Commit-Queue: Peter Kasting <pkasting@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#568306}
-
Tetsui Ohkubo authored
This CL adds all remaining UI strings for UnifiedSystemTray. String freeze will happen soon, so we have to make sure they land before that. TEST=manual BUG=813499 Change-Id: I8fed8fd079643fc37957a82628a24d09343fb70a Reviewed-on: https://chromium-review.googlesource.com/1103435Reviewed-by:
Yoshiki Iguchi <yoshiki@chromium.org> Commit-Queue: Tetsui Ohkubo <tetsui@chromium.org> Cr-Commit-Position: refs/heads/master@{#568305}
-
James Cook authored
Move the code to //ash/keyboard. Add yhanada to OWNERS. This should make it easier for the people working on keyboard support to get approvals from nearby time zones. Bug: none Change-Id: Idbb3023913c7e34daad9b42718dd90ad7ed8e319 Reviewed-on: https://chromium-review.googlesource.com/1105396Reviewed-by:
Yuichiro Hanada <yhanada@chromium.org> Commit-Queue: James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#568304}
-
Chromite Chromium Autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/86e1b8b5a23b..efd58885b78d git log 86e1b8b5a23b..efd58885b78d --date=short --no-merges --format='%ad %ae %s' 2018-06-19 yunlian@google.com eve-arcnext: remove USE="cfi" Created with: gclient setdep -r src/third_party/chromite@efd58885b78d The AutoRoll server is located here: https://chromite-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. BUG=chromium:853946 TBR=chrome-os-gardeners@chromium.org Change-Id: Ie4cc0a653204b46ba77c162abce07734cff42d76 Reviewed-on: https://chromium-review.googlesource.com/1105219Reviewed-by:
Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#568303}
-