- 18 Nov, 2017 40 commits
-
-
Conley Owens authored
Currently characteristics are not getting marked discovered. This change fixes that. At the moment, this does not bubble up a services discovered event, so a test for this will be made in a subsequent change. https://chromium-review.googlesource.com/c/chromium/src/+/730653/ BUG=507419 Change-Id: Ie6a510ee2ae6d97e34760822fe7b01f65e28337d Reviewed-on: https://chromium-review.googlesource.com/735983 Commit-Queue: Conley Owens <cco3@chromium.org> Reviewed-by:
Vincent Scheib <scheib@chromium.org> Reviewed-by:
Matt Reynolds <mattreynolds@chromium.org> Cr-Commit-Position: refs/heads/master@{#517677}
-
Kevin Cernekee authored
BUG=none TEST=unit tests Change-Id: Ia734c40400e722cf979231af398fa4a38611cfb7 Reviewed-on: https://chromium-review.googlesource.com/777971 Commit-Queue: Kevin Cernekee <cernekee@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/heads/master@{#517676}
-
Adrienne Walker authored
This moves test-only paint op comparisons from unittests into paint ops themselves. This is to support a fuzzing correctness test that serializing and then deserializing an op results in the same op. Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel Change-Id: I351b4fb5329ee9ff64d54bb9dd49d0a1a34f7b13 Reviewed-on: https://chromium-review.googlesource.com/777840Reviewed-by:
Khushal <khushalsagar@chromium.org> Commit-Queue: enne <enne@chromium.org> Cr-Commit-Position: refs/heads/master@{#517675}
-
Xianzhu Wang authored
- When click the toolbar to select a view during animation, show the view for 1 second. This is convenient to briefly view a specific view without stopping the animation. Previously the time showing the clicked view was random. - Let GUI.getExpectation(el) handle cases that the el is under result-frame, so that keyboard navigation still works when the focus is under result-frame (e.g. after the toolbar or the image result is clicked). - Let GUI.activeExpectation() return the open expectation if no expectation line can be found from the focused element, so that keyboard navigation can be based on the open expectation if the focus is neither under the expectation line nor result-frame. - Correct total count. Previously the total count didn't include expected failures, skipped and wontfix tests, etc. Change-Id: Ibc4b697c52a7b5d37f0ebbfb5c925cc478f15f06 Reviewed-on: https://chromium-review.googlesource.com/777469 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
Quinten Yearsley <qyearsley@chromium.org> Cr-Commit-Position: refs/heads/master@{#517674}
-
Evan Stade authored
of direct access to MessageCenter. Manual test: add `LowDiskSpace(10000);` to end of constructor. Bug: 783018 Change-Id: I3c1f7dd591e4c84b9d41742e6c042e63c7003138 Reviewed-on: https://chromium-review.googlesource.com/775059 Commit-Queue: Evan Stade <estade@chromium.org> Reviewed-by:
-
Kenneth Russell authored
Seems the earlier problems have been fixed. BUG=779991 NOTRY=true 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: I8e5563ce02c2817e84611e0758edc44a19edc602 Reviewed-on: https://chromium-review.googlesource.com/775999 Commit-Queue: Kenneth Russell <kbr@chromium.org> Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Cr-Commit-Position: refs/heads/master@{#517672}
-
Conley Owens authored
Previously, we notified discovery complete on a device before our async discovery calls actually finish. Additionally, we only partially recorded discovery. This change remedies both of these issues. BUG=507419 Change-Id: I730a52d74a0d11d8a62fb041d2103b78f566cc18 Reviewed-on: https://chromium-review.googlesource.com/730653 Commit-Queue: Conley Owens <cco3@chromium.org> Reviewed-by:
-
danakj authored
The test for this is in https://chromium-review.googlesource.com/c/chromium/src/+/775759 which converts all TextureMailbox-based tests over to ImportedResources. R=piman@chromium.org Bug: 769423 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel Change-Id: I9eefcd5a8783a6c2359fb46e1e2efb076302f13e Reviewed-on: https://chromium-review.googlesource.com/777695 Commit-Queue: danakj <danakj@chromium.org> Reviewed-by:
Antoine Labour <piman@chromium.org> Cr-Commit-Position: refs/heads/master@{#517670}
-
David Bokan authored
This reverts commit 55c943bf. The bots are convinced it's repsonsible for the linked perf regression, though it doesn't make much sense to me and couldn't reproduce locally. This patch has also caused lifecycle issues and isn't urgent so I'll back it out for now and consider better ways to do this. Bug: 742339 Change-Id: I271c5fa31512beefc74dcb1936f570edf1cc1175 Reviewed-on: https://chromium-review.googlesource.com/777040Reviewed-by:
Steve Kobes <skobes@chromium.org> Commit-Queue: David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#517669}
-
Conley Owens authored
Several device unittests test whether things behave properly after a device is deleted. This change enables those tests on Windows. These tests will become more relevant as service discovery is completed on Windows in a subsequent change. https://chromium-review.googlesource.com/c/chromium/src/+/730653/ BUG=507419 Change-Id: I1a6060692d9bb7f46b05acca78336015c72ce047 Reviewed-on: https://chromium-review.googlesource.com/776355Reviewed-by:
-
Sky Malice authored
Per guidance at about data coming from untrusted sources, such as disk or network, removed DCHECKs when handling data Loopback storage, see https://groups.google.com/a/chromium.org/d/msg/chromium-dev/LU6NWiaSSRc/oolO8fg5AAAJ Instead null entities are returned which are essentailly just dropped. Also includes some minor cleanup, including deletion of un-used fake_server_entity.cc file, consistent usage of un-templated WrapUnique, nullptr for empty unique_ptrs, and pushed test constant back to test file (single_client_wallet_sync_test.cc). Bug: 771811 Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs Change-Id: I73045ed11982e6c44d5b623855163e61c1961fa2 Reviewed-on: https://chromium-review.googlesource.com/713556Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Mike Baxley <baxley@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Commit-Queue: Sky Malice <skym@chromium.org> Cr-Commit-Position: refs/heads/master@{#517667}
-
depot-tools-roller@chromium.org authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/0844d0e4444c..276e0454b797 $ git log 0844d0e44..276e0454b --date=short --no-merges --format='%ad %ae %s' Created with: roll-dep src/third_party/depot_tools The AutoRoll server is located here: https://depot-tools-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. TBR=phajdan.jr@chromium.org Change-Id: I2b2eebd702461162110cdc0a5399a8e9d460a0bf Reviewed-on: https://chromium-review.googlesource.com/777847Reviewed-by:
depot-tools-roller . <depot-tools-roller@chromium.org> Commit-Queue: depot-tools-roller . <depot-tools-roller@chromium.org> Cr-Commit-Position: refs/heads/master@{#517666}
-
Xiaohui Chen authored
BUG=b:69178309 TEST=login as supervised user, see assistant settings gone Change-Id: Ib84d9dc34288b9edaffcddd3f42ecdacd0e7d0a8 Reviewed-on: https://chromium-review.googlesource.com/777961Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Xiaohui Chen <xiaohuic@chromium.org> Cr-Commit-Position: refs/heads/master@{#517665}
-
Tim Brown authored
Change-Id: I852031b2c7dcf210c05ed9f2b0f0cea7ee9faf3e Reviewed-on: https://chromium-review.googlesource.com/778048Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Commit-Queue: Tim Brown <timbrown@chromium.org> Cr-Commit-Position: refs/heads/master@{#517664}
-
James Cook authored
Enable all passing tests. Categorize all failing tests and file bugs for the most common ones. Bug: 678687 Test: browser_tests --mash Change-Id: I13bbf84322aaa3d6dcceb36a2fceff1fc16280f1 Reviewed-on: https://chromium-review.googlesource.com/777848Reviewed-by:
James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#517663}
-
Ryan Landay authored
changwan@ pointed out it would be a good idea to add a test for the autocorrect attribute (e.g. <input autocorrect="off">) since we don't appear to have one already. Change-Id: Ifb21a7e68950e60d66a1a5c8ee618b436c4620c6 Reviewed-on: https://chromium-review.googlesource.com/740373 Commit-Queue: Ryan Landay <rlanday@chromium.org> Reviewed-by:
Changwan Ryu <changwan@chromium.org> Cr-Commit-Position: refs/heads/master@{#517662}
-
Renjie Liu authored
Original owner: amoylan@chromium.org Original cl: https://chromium-review.googlesource.com/c/chromium/src/+/754254 This CL is part of the implementation of public-IP-only geolocation as described in the design doc: https://docs.google.com/document/d/1oSQM3GEMTL1raWLYv8S6_Yyt93FF2zQbANI4bKJ6LDs This part is the implementation of the centralized PublicIpAddressLocationNotifier that issues IP-geolocation requests to handle any/all clients. This reuses the NetworkLocationRequest class from the existing Geolocation service (which provides web-platform geolocation) in //device/geolocation. This CL creates //services/device/geolocation/ and includes a "+net" DEPS entry. (This "+net" dependency, among others, will eventually be needed when all of //device/geolocation eventually moves into //services/device/geolocation as part of Geolocation Servicification.) Tests: Unit tests for PublicIpAddressGeolocationNotifier covering the logic to do with responding to different sequences of "network change detected" and "client wants a new/next position". Add PartialNetworkTrafficAnnotation as well. Bug: 718694, 769158 Bug: Change-Id: I792a1793a54b283949b97f411b70a71ea27ec6c8 Reviewed-on: https://chromium-review.googlesource.com/757821Reviewed-by:
Miguel Casas <mcasas@chromium.org> Reviewed-by:
Zhongyi Shi <zhongyi@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Reviewed-by:
Ramin Halavati <rhalavati@chromium.org> Reviewed-by:
Renjie Liu <renjieliu@chromium.org> Commit-Queue: Renjie Liu <renjieliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#517661}
-
Menglu Huang authored
Bug: Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs Change-Id: Ib3c61bb6351d79be433fea84842580ab4f950cad Reviewed-on: https://chromium-review.googlesource.com/777781Reviewed-by:
-
Kenneth Russell authored
Core Animation doesn't have the ability to honor this flag. Fall back to the regular OpenGL-based composition path in this case. Finally add a pixel test for this. BUG=599285 Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2;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: I06ffe41b5080bab6d767472b0deb4b97142ead21 Reviewed-on: https://chromium-review.googlesource.com/776218 Commit-Queue: Kenneth Russell <kbr@chromium.org> Reviewed-by:
Kai Ninomiya <kainino@chromium.org> Reviewed-by:
ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#517659}
-
Weiyong Yao authored
Android VEA currently doesn't preserve the timestamps in the input frames, causing trouble for WebRTC. The reason is MediaCodec assumes the presentation timestamp to be monotonically-growing value. But in chromium the video capture maybe paused a while or drop some frames, so the timestamps in input frames won't be continious as expected. Then we have to generate a seperate monotonically-growing timestamp for encoding instead. Here we cache the timestamps in input frames, mapping to the generated timestamp, and read them out after encoding. Then encoder can work happily and we can preserve the input timestamps. Bug: 785407 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: I594190436f18437afb937c4f0667a5b1e3019280 Reviewed-on: https://chromium-review.googlesource.com/775144 Commit-Queue: Weiyong Yao <braveyao@chromium.org> Reviewed-by:
Emircan Uysaler <emircan@chromium.org> Reviewed-by:
Frank Liberato <liberato@chromium.org> Cr-Commit-Position: refs/heads/master@{#517658}
-
Jialiu Lin authored
PPAPIDownloadRequest.RequestDuration is always zero. This is because UMA_HISTOGRAM_TIMES macro cannot handle negative number. This Cl fixes this issue. Bug: 633341 Change-Id: I8dd1200ed7f28e746469b4d82ef0e927a5080a88 Reviewed-on: https://chromium-review.googlesource.com/777887 Commit-Queue: Jialiu Lin <jialiul@chromium.org> Commit-Queue: Nathan Parker <nparker@chromium.org> Reviewed-by:
Nathan Parker <nparker@chromium.org> Cr-Commit-Position: refs/heads/master@{#517657}
-
mark a. foltz authored
We want to consolidate how route descriptions passed to the UX by using MediaRoute.description instead of MediaStatus.description. This adds comments explaining what the route description should be used for, and notes that MediaStatus.description will be deprecated once MRPs are updated to use MediaRoute.description instead. It also removes the "Casting" prefix which was sometimes inserted before MediaRoute.description, as we want to customize the description to say "Casting," "Remoting," or "Mirroring." The template string remains so we can use it in a future change for proper localization of the description. This change does not make the UX any worse than it is right now (and will be followed soon by an MRP changes to add "Casting" back where it makes sense). The Media Router elements are refactored to use "description" consistently and to better share CSS, which makes rendering more consistent between MediaStatus.description and MediaRoute.description. TBR=estark@chromium.org for comment-only .mojom changes Bug: 786208 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I9356fa917f0d77eeac5b7b32d6175aa03a943e5c Reviewed-on: https://chromium-review.googlesource.com/776130 Commit-Queue: mark a. foltz <mfoltz@chromium.org> Reviewed-by:
Derek Cheng <imcheng@chromium.org> Reviewed-by:
Takumi Fujimoto <takumif@chromium.org> Cr-Commit-Position: refs/heads/master@{#517656}
-
Wenzhao Zang authored
The functions listed in the mojo interface are all from WallpaperManager. The next step is to move their implementation to //ash one by one. By the time they are all moved, WallpaperManager can basically be deleted. TBR=michaelpg@chromium.org Bug: 779221 Change-Id: I90efac15662d32d96670f56af3145a9c42270ef3 Reviewed-on: https://chromium-review.googlesource.com/762126Reviewed-by:
Wenzhao (Colin) Zang <wzang@chromium.org> Reviewed-by:
Oliver Chang <ochang@chromium.org> Reviewed-by:
-
Eric Roman authored
concatenation. The former is a direct reading of RFC 6960 Change-Id: Iaadd14838f41524330345c488eab81d49e406fe4 Reviewed-on: https://chromium-review.googlesource.com/777733Reviewed-by:
Matt Mueller <mattm@chromium.org> Commit-Queue: Eric Roman <eroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#517654}
-
Jonathan Metzman authored
Bug: 784014 Change-Id: Id7b5b16debfa4cbb3aebf3d84c30b34fe67b64d0 Reviewed-on: https://chromium-review.googlesource.com/766514 Commit-Queue: Jonathan Metzman <metzman@chromium.org> Commit-Queue: Max Moroz <mmoroz@chromium.org> Reviewed-by:
Marja Hölttä <marja@chromium.org> Reviewed-by:
Abhishek Arya <inferno@chromium.org> Reviewed-by:
Max Moroz <mmoroz@chromium.org> Cr-Commit-Position: refs/heads/master@{#517653}
-
Philip Rogers authored
These root layer scrolling expectations are now correct. paint/invalidation/window-resize/window-resize-frameset.html paint/invalidation/window-resize/window-resize-viewport-percent.html paint/invalidation/window-resize/window-resize-positioned-percent-top.html paint/invalidation/window-resize/window-resize-positioned-bottom.html paint/invalidation/window-resize/window-resize-percent-width-height.html paint/invalidation/window-resize/window-resize-percent-html.html paint/invalidation/window-resize/window-resize-no-layout-change2.html paint/invalidation/window-resize/window-resize-no-layout-change1.html paint/invalidation/window-resize/window-resize-media-query.html paint/invalidation/window-resize/window-resize-centered-inline-under-fixed-pos.html paint/invalidation/window-resize/window-resize-background-image-non-fixed.html paint/invalidation/window-resize/window-resize-background-image-generated.html paint/invalidation/window-resize/window-resize-background-image-fixed-centered-composited.html paint/invalidation/window-resize/window-resize-background-image-fixed-centered.html window-resize-vertical-writing-mode.html has not been rebaselined because it fails for underinvalidation and needs to be fixed. Bug: 781419 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_root_layer_scrolls Change-Id: If96694875991c95895deeca322c1e5b20612d5c2 Reviewed-on: https://chromium-review.googlesource.com/777482Reviewed-by:
-
Nate Fischer authored
No change to behavior. There were a few method calls in content layer where a comment is used to indicate the parameter name, but the comment's param name doesn't match the real parameter name. This CL changes the comment to match the parameter name. This is another errorprone compile warning. Test: ninja system_webview_apk (warnings go away) Change-Id: I6080a30f6656a1e6d2221521fbb9c11a250e8376 Reviewed-on: https://chromium-review.googlesource.com/777551Reviewed-by:
Bo <boliu@chromium.org> Commit-Queue: Nate Fischer <ntfschr@chromium.org> Cr-Commit-Position: refs/heads/master@{#517651}
-
Kenneth Russell authored
This runs essentially the same tests as the desktop bots. BUG=786572 NOTRY=true 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: I36718069f2a786e3f7e274645d3ff6f58404f492 Reviewed-on: https://chromium-review.googlesource.com/777728 Commit-Queue: Kenneth Russell <kbr@chromium.org> Reviewed-by:
Yuly Novikov <ynovikov@chromium.org> Cr-Commit-Position: refs/heads/master@{#517650}
-
Bill Orr authored
There were a number of issues with lifetime that would cause issues, such as multiple initializations of OpenVR, multiple conflicting OpenVRDevices, and leaking objects. This change fixes those so OpenVRDeviceProvider owns OpenVRDevice, which owns OpenVRRenderLoop, and OpenVRRenderLoop correctly cleans up its bindings. Change-Id: I32ee8abaa70a8a13155448e697d318c675f1d9ed Reviewed-on: https://chromium-review.googlesource.com/777787Reviewed-by:
Brandon Jones <bajones@chromium.org> Commit-Queue: Bill Orr <billorr@chromium.org> Cr-Commit-Position: refs/heads/master@{#517649}
-
Greg Kerr authored
FontObjectsServer access is needed on not just macOS version 10.11, and the new sandbox was blocking the accees and causing renderer crashes. Bug: 786615 Change-Id: If94af99e476325155d9262ac3e3dc75831aa8c5f Reviewed-on: https://chromium-review.googlesource.com/777976Reviewed-by:
Robert Sesek <rsesek@chromium.org> Commit-Queue: Greg Kerr <kerrnel@chromium.org> Cr-Commit-Position: refs/heads/master@{#517648}
-
David Jacobo authored
In chrome://settings we already have a definition for AndroidAppsInfo so reusing instead of duplicating. Bug: None Test: Build. Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: Ie7a24d9c9df7fe3d22e3e85d067c140944f85db4 Reviewed-on: https://chromium-review.googlesource.com/773479Reviewed-by:
-
Eric Karl authored
This change adds the OOP Raster transfer cache. Subsequent changes will hook these objects up to the OOP Raster serialize/deserialize mechanisms. The transfer cache includes four main classes/interfaces: --ClientTransferCacheEntry-- Represents an object that can be added to the transfer cache. Includes methods for serializing the object for transport to the GPU process. --ClientTransferCache-- Provides methods for inserting, locking, unlocking, and deleting ClientTransferCacheEntry objects. Handles sending these objects to the ServiceTransferCache. --ServiceTransferCacheEntry-- Represents an object that can be stored in the GPU process' ServiceTransferCache. Includes methods for deserializing the serialized data produced by the ClientTransferCacheEntry. --ServiceTransferCache-- Includes methods for receiving new objects from the ClientTransferCache, looking up existing objects, and enforcing memory limits. This system is built around the existing DiscardableHandle system used in GPU discardable textures. Bug: 777622 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;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: I5bf2ed467147d6dbcd5690a3997280806c4d7763 Reviewed-on: https://chromium-review.googlesource.com/747273 Commit-Queue: Eric Karl <ericrk@chromium.org> Reviewed-by:
enne <enne@chromium.org> Cr-Commit-Position: refs/heads/master@{#517646}
-
Jayson Adams authored
The ColorPanelCocoa sets itself as the target and delegate of the NSColorPanel, and on dealloc it clears the NSColorPanel's target and delegate settings if it sees that it is the delegate. On 10.13 it appears that the NSColorPanel's delegate can get set to nil while leaving the target intact, preventing -dealloc from clearing the ColorPanelCocoa target and leading to a Zombie crash. This cl uses a private method to check the NSColorPanel's target in -dealloc and clear it if it's still the ColorPanelCocoa. R=rsesek@chromium.org,avi@chromium.org Bug: 767598 Change-Id: I86557f3dadc65b8e0d455156457d960d8f45044e Reviewed-on: https://chromium-review.googlesource.com/685394 Commit-Queue: Jayson Adams <shrike@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
-
Steven Bennetts authored
C++ -> JS listeners are relatively expensive and having more than one for a particular event is unnecessary, more complex, and confusing. Instead, make <internet-page>, which contains the other elements, the primary listener and dispatch JS events to the other elements when a networkingPrivate event occurs. Bug: 784026 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I834797a2d814cde563144bac816c69d55ad78633 Reviewed-on: https://chromium-review.googlesource.com/775661 Commit-Queue: Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#517644}
-
rbpotter authored
Bug: 773928 Change-Id: I2980d8833df8abd31b231efd5bc531c4479d171d Reviewed-on: https://chromium-review.googlesource.com/777459Reviewed-by:
Lei Zhang <thestig@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#517643}
-
Lei Zhang authored
Change-Id: I84e036d5c71373ce3572d4b67b06fcadb25bb347 Reviewed-on: https://chromium-review.googlesource.com/777963 Commit-Queue: Lei Zhang <thestig@chromium.org> Reviewed-by:
Will Harris <wfh@chromium.org> Cr-Commit-Position: refs/heads/master@{#517642}
-
CrystalFaith authored
Image in notification was removed, but the name of the image in notification was not updated. Bug: None Change-Id: I121a86bf592601933d1f4ae0730e5c049b743dd4 Reviewed-on: https://chromium-review.googlesource.com/769655Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Commit-Queue: Crystal Lambert <crystallambert@chromium.org> Cr-Commit-Position: refs/heads/master@{#517641}
-
Bailey Berro authored
Bug: Change-Id: I79fa779041a90182dc839b00fc404f6f80acd6a7 Reviewed-on: https://chromium-review.googlesource.com/777395 Commit-Queue: Bailey Berro <baileyberro@chromium.org> Reviewed-by:
Zentaro Kavanagh <zentaro@chromium.org> Cr-Commit-Position: refs/heads/master@{#517640}
-
chrome://flagsEdward Jung authored
iOS doesn't show unavailable experiments which broke the tab layout. Additionally set the viewport max scale so the page doesn't jump around when the keyboard is activated, Bug: 783837 Change-Id: I691b3efca6ad24870d195357783e6016d30b0cee Reviewed-on: https://chromium-review.googlesource.com/769949Reviewed-by:
-
Yash Malik authored
This CL add the necessary glue to wire up the keyboard API to its implementation in the Daydream Keyboard APK. The keyboard can be temporarily be summoned via the app button by turning on the vr-browser-keyboard runtime flag. Follow-up CLs will introduce the keyboard element and remove the temporary code in VrShellGl. Bug: 641470 Change-Id: I3d1372aa335db69c1e38adbb00a67993f9eea1e0 Reviewed-on: https://chromium-review.googlesource.com/731568 Commit-Queue: Yash Malik <ymalik@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Reviewed-by:
Biao She <bshe@chromium.org> Reviewed-by:
Amirhossein Simjour <asimjour@chromium.org> Reviewed-by:
Ian Vollick <vollick@chromium.org> Cr-Commit-Position: refs/heads/master@{#517638}
-
