- 28 Feb, 2019 40 commits
-
-
Eric Stevenson authored
Was already done for native functions but missed when calling native instance methods. Bug: 934847 Change-Id: Ie4bfbe81c748d8f3c78de77cd759ff4d2c804791 Reviewed-on: https://chromium-review.googlesource.com/c/1495443 Auto-Submit: Eric Stevenson <estevenson@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Commit-Queue: Tommy Nyquist <nyquist@chromium.org> Cr-Commit-Position: refs/heads/master@{#636561}
-
chromium-autoroll authored
The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll 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:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast TBR=cr-fuchsia+bot@chromium.org Change-Id: Iaaf076b7c6e7fa6e473cd835d579e1d8f57a3fbd Reviewed-on: https://chromium-review.googlesource.com/c/1494828Reviewed-by:
chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#636560}
-
Josh Nohle authored
Add a five-minute delay between immediate-retry attempts in the CryptAuth v2 Enrollment scheduler. It is probably a good idea to wait a short amount of time before retrying a failed enrollment attempt; otherwise, we might burn through all allotted "immediate" retry attempts specified by CryptAuth because of a transient failure. Also, CryptAuth throttles SyncKeys requests if more than one is sent within a five-minute window. Bug: 899080 Change-Id: Ie8d39b5e9d5af4464ac93200508b680e7039014c Reviewed-on: https://chromium-review.googlesource.com/c/1495739Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Commit-Queue: Josh Nohle <nohle@chromium.org> Cr-Commit-Position: refs/heads/master@{#636559}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/a0a1dcc95853..f6d776ff4a4a git log a0a1dcc95853..f6d776ff4a4a --date=short --no-merges --format='%ad %ae %s' 2019-02-28 dgarrett@google.com workspace_stages: Add test coverage for WorkspaceSyncChrome. Created with: gclient setdep -r src/third_party/chromite@f6d776ff4a4a The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-chromium-autoroll 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:chromeos-kevin-rel TBR=chrome-os-gardeners@chromium.org Change-Id: I9b6efa9c4116b2c6e40fb249c8ba2ccbe7bf628a Reviewed-on: https://chromium-review.googlesource.com/c/1494937Reviewed-by:
-
Brandon Jones authored
This requires all sessions that were previously setting an outputContext in the requestSession call to move that assignment to an updateRenderState call post-session-creation instead. Additionally, "inline" sessions can now be created without an outputContext but must still have one assigned to them before any requestAnimationFrame callbacks will be processed. Bug: 928417 Change-Id: I469fab8c3f641870387f2f92aee52182016efe37 Reviewed-on: https://chromium-review.googlesource.com/c/1476097 Commit-Queue: Brandon Jones <bajones@chromium.org> Reviewed-by:
Brian Sheedy <bsheedy@chromium.org> Reviewed-by:
Klaus Weidner <klausw@chromium.org> Cr-Commit-Position: refs/heads/master@{#636557}
-
Avery Musbach authored
CanSnapInSplitview() checks stricter requirements than WindowState::CanSnap(), meaning that a window snapped in clamshell mode might not be appropriate to carry over to split view on entering tablet mode. Now the tablet mode window manager shall seek approval from CanSnapInSplitview() before attempting to carry over a snapped window to split view on entering tablet mode. TabletModeWindowState::TabletModeWindowState() shall no longer call TabletModeWindowState::GetSnappedWindowStateType(), because the whole purpose of that function is to check CanSnapInSplitview() which shall have already been checked in the tablet mode window manager. Test: ash_unittests TabletModeControllerTest.StartTablet*DesktopOnly* Bug: 936478 Change-Id: If4f732d7276d7cae438fe08a919a13f170986f7d Reviewed-on: https://chromium-review.googlesource.com/c/1492351 Commit-Queue: Avery Musbach <amusbach@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#636556}
-
Daniel Libby authored
Currently, on both main and impl thread scrolling, if an in-progress scroll animation is updated in response to the GestureScrollUpdate, we do not get a TimeToScrollUpdateSwapBegin4 histogram value. This is due to the fact that we don't notify the LatencyInfoSwapPromiseMonitor while the input event is being handled, since only the scroll animation target is updated. This change adds calls that triggers the appropriate notifications so that the swap promises eventually trigger such that the LatencyInfo objects get shipped off with the CompositorFrame at a later point in time. Added to an existing layer_tree_host_impl unittest to verify we get the swap promise monitor notification when updating an animation. The main thread case was not as easily unit tested, so expanding and existing scroll wheel test in content_browsertests to perform multiple wheel-based scroll gestures and verify we see the appropriate histograms emitted. R=bokan@chromium.org, nzolghadr@chromium.org, tdresser@chromium.org Bug: 923498 Change-Id: Ia211800f96c304cdfebf2599e310e2bea8500d96 Reviewed-on: https://chromium-review.googlesource.com/c/1476208 Commit-Queue: Daniel Libby <dlibby@microsoft.com> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Timothy Dresser <tdresser@chromium.org> Reviewed-by:
David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#636555}
-
Tsuyoshi Horo authored
Bug: 910516 Change-Id: Iad6e51586678a3b391409d0f6526f62781d677a3 Reviewed-on: https://chromium-review.googlesource.com/c/1493688Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Tsuyoshi Horo <horo@chromium.org> Cr-Commit-Position: refs/heads/master@{#636554}
-
Rob Schonberger authored
This fixes a UI bug only visible when this flag is on. Bug: 911427 Change-Id: I31749509a5ba929fc484ae2812180bb2a5749fc1 Reviewed-on: https://chromium-review.googlesource.com/c/1491737 Commit-Queue: Rob Schonberger <robsc@chromium.org> Reviewed-by:
Alex Newcomer <newcomer@chromium.org> Reviewed-by:
Jenny Zhang <jennyz@chromium.org> Cr-Commit-Position: refs/heads/master@{#636553}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/fe34723a55ec..fe83cfa6b43a git log fe34723a55ec..fe83cfa6b43a --date=short --no-merges --format='%ad %ae %s' 2019-02-28 hferreiro@igalia.com Add --current to rebase the current branch Created with: gclient setdep -r src/third_party/depot_tools@fe83cfa6b43a The AutoRoll server is located here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll 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=agable@chromium.org Change-Id: I7cde445615f55d5c2229f41695326da9421054f5 Reviewed-on: https://chromium-review.googlesource.com/c/1494833Reviewed-by:
-
Mike Wittman authored
Updates the field and accessor name to reflect its actual state, and to be consistent across platforms. Bug: 931418 Change-Id: I758a7bb8c8183174c42142563203e8e5acd20c37 Reviewed-on: https://chromium-review.googlesource.com/c/1478250 Commit-Queue: Mike Wittman <wittman@chromium.org> Reviewed-by:
Andrey Kosyakov <caseq@chromium.org> Reviewed-by:
oysteine <oysteine@chromium.org> Reviewed-by:
Alexei Filippov <alph@chromium.org> Reviewed-by:
Charlie Andrews <charliea@chromium.org> Cr-Commit-Position: refs/heads/master@{#636551}
-
Antonio Gomes authored
... from t_p/blink/renderer/platform/. This is a first step to clean up how callbacks are handling in modules/filesystem. BUG=933878 R=jbroman@chromium.org CC=mek@chromium.org,blink-reviews-vendor@chromium.org Change-Id: I0d75062132af40e7e8038e1e90163d3b88d84caa Reviewed-on: https://chromium-review.googlesource.com/c/1494681Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Cr-Commit-Position: refs/heads/master@{#636550}
-
Nico Weber authored
It was only used by MSVC which we no longer use, and it required including sal.h (somewhat large) in compiler_specific.h (somewhat commonly included). clang-cl now no longer needs to process sal.h, which will help with build times a tiny bit. We still get the format string protection through the PRINTF_FORMAT macro. (WPRINTF_FORMAT on the other hand is a no-op and clang-cl seems to not check wprintf style format strings. So we do lose some coverage here for wide strings, but we lost that when we switched to clang-cl.) TBR=slangley Bug: none Change-Id: Iab02869cb06682500ab31e1810c070708347ad64 Reviewed-on: https://chromium-review.googlesource.com/c/1494679 Commit-Queue: Nico Weber <thakis@chromium.org> Auto-Submit: Nico Weber <thakis@chromium.org> Reviewed-by:
Bruce Dawson <brucedawson@chromium.org> Cr-Commit-Position: refs/heads/master@{#636549}
-
David Bokan authored
In https://crrev.com/45236fd563e9df53dc45579be1f3d0b4784885a2 I did a heavy refactoring of how fragment anchors work and when they get invoked. This refactoring removed the layout call from LocalFrameView::ProcessUrlFragment. This is desirable since it should be layout that drives the fragment anchor, not the other way around. In general avoiding surprise layouts is good. I assumed this would be ok since we'll invoke the fragment anchor again in the next layout. However, there's a case where this isn't true. When a document finishes loading (Document::ImplicitClose) it will invoke the fragment anchor. The fragment anchor will then be removed since the document is already in the "load completed" state. If the iframe finishes loading without any layouts this call will be the only invocation and it'll happen on a dirty layout tree. The solution in this CL is to remove that invocation in ImplicitClose while layout is dirty potentially dirty. If layout is dirty it'll be invoked when we perform the layout. This leaves the only two ways for the anchor to be invoked as: - Right after a layout - When the fragment is first set and layout is already clean Change-Id: I3f038a4e35038a0cd9e4a17593b9b6b3d810068f Bug: 934405 Reviewed-on: https://chromium-review.googlesource.com/c/1481054 Commit-Queue: David Bokan <bokan@chromium.org> Reviewed-by:
Stefan Zager <szager@chromium.org> Cr-Commit-Position: refs/heads/master@{#636548}
-
John Lee authored
This makes available an endpoint chrome://welcome/preview-background.jpg that takes in a parameter of a number, referring to the index in the whitelist of NTP backgrounds for Onboarding to fetch. Change-Id: I99ec3cc83852b88f56bc0bc58c2d1ef6dfbb2202 Reviewed-on: https://chromium-review.googlesource.com/c/1481890 Commit-Queue: John Lee <johntlee@chromium.org> Reviewed-by:
Martin Šrámek <msramek@chromium.org> Reviewed-by:
Hector Carmona <hcarmona@chromium.org> Reviewed-by:
Dan Beam <dbeam@chromium.org> Cr-Commit-Position: refs/heads/master@{#636547}
-
Ella Ge authored
Due to lake on android-marshmallow-arm64-rel TBR: perezju@chromium.org No-Try: True Bug: 937006 Change-Id: I6a825c27e9a8d9a4aacfca30478782375dfc68cc Reviewed-on: https://chromium-review.googlesource.com/c/1495859Reviewed-by:
Ella Ge <eirage@chromium.org> Commit-Queue: Ella Ge <eirage@chromium.org> Cr-Commit-Position: refs/heads/master@{#636546}
-
Ryan Sturm authored
This is a reland of 21fe97f0 Original change's description: > Stop over-recording data use related to Previews > > Lite Page Server Previews over records data use when it attempts to > record data savings. Instead, only the savings should be recorded. > > This also changes the data usage site breakdown code to use Virtual URL > (the one in the omnibox) instead of the actual host for the sake of > improving UI and tracking HTTPS Lite Page Previews more accurately. > > Bug: 936577 > Change-Id: Ib7dfe8afeea0b277ac065d58c02b2962a4ab6c94 > Reviewed-on: https://chromium-review.googlesource.com/c/1492428 > Commit-Queue: Ryan Sturm <ryansturm@chromium.org> > Reviewed-by: Robert Ogden <robertogden@chromium.org> > Cr-Commit-Position: refs/heads/master@{#636282} Bug: 936577 Change-Id: I342de5853cea0ffced06af1ac531846cdd1cc34b Reviewed-on: https://chromium-review.googlesource.com/c/1494797Reviewed-by:
Ryan Sturm <ryansturm@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Commit-Queue: Ryan Sturm <ryansturm@chromium.org> Cr-Commit-Position: refs/heads/master@{#636545}
-
Toni Barzic authored
Stops using ScreenExitCode enums reported by network screen (which is part of a larger effort to deprecate ScreenExitCode enum all together). Instead, defines result enums per screen when needed (i.e. if the screen can report multiple values). Updates how screens relay the exit code to WizardController - instead of using BaseScreenDelegate::OnExit (indirectly though BaseScreen::Finish), the screens now take a callback that is run when the screen exits. Affected screens: * NetworkScreen Deprecated exit codes: * NETWORK_BACK * NETWORK_CONNECTED * NETWORK_OFFLINE_DEMO_SETUP BUG=930267 Change-Id: If51230071833d239316d85ae1b047c83d7812bd2 Reviewed-on: https://chromium-review.googlesource.com/c/1484871 Commit-Queue: Toni Baržić <tbarzic@chromium.org> Reviewed-by:
Alexander Alekseev <alemate@chromium.org> Cr-Commit-Position: refs/heads/master@{#636544}
-
Lan Wei authored
In order to remove the timer to send the fake mouse move event, we decide the best place to send the fake mouse move event is at the next begin frame right after we have seen a gesture scroll end event. This CL is only about scrolls happening on compositor. I will work on scrolls on main thread in a following CL. Bug: 877132 Change-Id: Ia9c5e8b326a08797ad7f65e1242bb9f2bcb275ee Reviewed-on: https://chromium-review.googlesource.com/c/1481747 Commit-Queue: Lan Wei <lanwei@chromium.org> Reviewed-by:
-
Mike Wittman authored
Module sizes are required for lookup by the ModuleCache, so ensure they are provided and remove the constructor that allows construction without a size. Bug: 931418 Change-Id: Ibe3c1512196030de80c4785812a3ff31c55eeec8 Reviewed-on: https://chromium-review.googlesource.com/c/1478175 Commit-Queue: Mike Wittman <wittman@chromium.org> Reviewed-by:
-
Tim Song authored
If there are no focusable views in the LockContentsView a crash will occur when toggling focus. Although this doesn't currently cause a crash, it was a problem in the past and we need to prevent it from happening in case of UI changes in the future. TEST=unit test BUG=914103 Change-Id: Iee5f23d98aa202998ccd91c743e1f0279c162c81 Reviewed-on: https://chromium-review.googlesource.com/c/1493446Reviewed-by:
Jacob Dufault <jdufault@chromium.org> Commit-Queue: Tim Song <tengs@chromium.org> Cr-Commit-Position: refs/heads/master@{#636541}
-
Luke Halliwell authored
Merge-With: eureka-internal/247580 Bug: internal b/122743819 Test: None Change-Id: Ib31702df4e94550813c2e7c20f60657ec179af1d Reviewed-on: https://chromium-review.googlesource.com/c/1494802 Commit-Queue: Yuchen Liu <yucliu@chromium.org> Auto-Submit: Luke Halliwell <halliwell@chromium.org> Reviewed-by:
Yuchen Liu <yucliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#636540}
-
Oystein Eftevaag authored
These tests were failing under lsan as the ScopedTaskEnvironment used in the test environment requires the ProducerClient test runner to be reset between each test. R=ssid@chromium.org Bug: 936907 Change-Id: Iade8c117c43a9071d1e3ea85619930de21f6ea0d Reviewed-on: https://chromium-review.googlesource.com/c/1495043Reviewed-by:
ssid <ssid@chromium.org> Commit-Queue: oysteine <oysteine@chromium.org> Cr-Commit-Position: refs/heads/master@{#636539}
-
Min Qin authored
This CL adds helper method to rename a download if it is content URI. BUG=924751 Change-Id: Icbf0c6d493fba4caa3e8f929cebce9ea8c1c974f Reviewed-on: https://chromium-review.googlesource.com/c/1493375Reviewed-by:
Xing Liu <xingliu@chromium.org> Commit-Queue: Min Qin <qinmin@chromium.org> Cr-Commit-Position: refs/heads/master@{#636538}
-
Oystein Eftevaag authored
These DCHECKs check that the Coordinator functionality that Perfetto replaces should not be called when the Perfetto runtime flag is enabled. However, the unittests should still work so we check whether we're connected through Mojo or not (which is when Perfetto will override the Coordinator used). R=ssid@chromium.org Bug: 839084 Change-Id: Ia4370764f04dd444c01d7dd78789018e6ca7e76e Reviewed-on: https://chromium-review.googlesource.com/c/1495207Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/glslang/+log/ec484527b643..d90d548161bc git log ec484527b643..d90d548161bc --date=short --no-merges --format='%ad %ae %s' 2019-02-28 johnkslang@users.noreply.github.com Merge pull request #1713 from jeffbolznv/fix_nv_extension_disabled 2019-02-26 johnkslang@users.noreply.github.com Merge pull request #1701 from jeffbolznv/cooperative_matrix Created with: gclient setdep -r src/third_party/glslang/src@d90d548161bc The AutoRoll server is located here: https://autoroll.skia.org/r/glslang-chromium-autoroll 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: I1b54446f975077704f7f43e211d6babe2d06fb03 Reviewed-on: https://chromium-review.googlesource.com/c/1494831Reviewed-by:
-
Miyoung Shin authored
The size of ShowdowRoot class had doubled the bitfield size from 16 bits to 32 bits to match the alignment of all compilers after landing the CL[1]. This CL restores ShowdowRoot class size using only |unsigned| type with the bitfields. [1]https://crrev.com/c/1477558/ Bug: 936379 Change-Id: I5faaf4364738835f2fb68036777b148d25bbedc3 Reviewed-on: https://chromium-review.googlesource.com/c/1491743Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Darwin Huang <huangdarwin@chromium.org> Commit-Queue: Darwin Huang <huangdarwin@chromium.org> Cr-Commit-Position: refs/heads/master@{#636535}
-
Peter Wen authored
Rather than specifying each feature in multiple places, unify our base module java dependencies in the java group chrome_all_java. Also remove duplicate deps now that our base apk/module template adds chrome_all_java as a dep. Bug: 846440 Change-Id: I9e56cb425744896c5e9e893c3ef00547fdf4dbe0 Reviewed-on: https://chromium-review.googlesource.com/c/1495595 Auto-Submit: Peter Wen <wnwen@chromium.org> Reviewed-by:
-
mrefaat authored
I created all the files in the folder (some was moved around by others) But i own all the logic inside all of them Sample CLs: Reason: https: //chromium-review.googlesource.com/c/chromium/src/+/727519/ https: //chromium-review.googlesource.com/c/chromium/src/+/1101497/ Change-Id: Id926cff97afbbe8097bf77e54bcb418e10be9ac4 Reviewed-on: https://chromium-review.googlesource.com/c/1487184 Commit-Queue: Mohammad Refaat <mrefaat@chromium.org> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Cr-Commit-Position: refs/heads/master@{#636533}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/3c7b056c0c8b..9950df105a7c git log 3c7b056c0c8b..9950df105a7c --date=short --no-merges --format='%ad %ae %s' 2019-02-28 renjietang@chromium.org netlog_viewer: Update Quic dashboard to show new experiment race_stale_dns_on_connection. Created with: gclient setdep -r src/third_party/catapult@9950df105a7c The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll 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 BUG=chromium: TBR=sullivan@chromium.org Change-Id: I67cf76a6898bcd127abb643091f33ae7f16ae09a Reviewed-on: https://chromium-review.googlesource.com/c/1495297Reviewed-by:
-
Marijn Kruisselbrink authored
After a PublicURLManager is "stopped" (i.e. the ExecutionContext it belongs to has been destroyed) it is no longer possible to resolve any URLs through it. So in that case, just early return from Resolve(), just like Register and Revoke already do as well. Bug: 931139 Change-Id: Ibd76833f10a1ffa40b712e93a5b5ef41071ebe99 Reviewed-on: https://chromium-review.googlesource.com/c/1495373Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Cr-Commit-Position: refs/heads/master@{#636531}
-
Robert Liao authored
InProcessContextFactory isn't set up to properly support Direct Composition. BUG=936249 Change-Id: I34877fad76a40d8f141fb16c7a1d6d826d6c231a Reviewed-on: https://chromium-review.googlesource.com/c/1492482 Commit-Queue: Robert Liao <robliao@chromium.org> Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
kylechar <kylechar@chromium.org> Cr-Commit-Position: refs/heads/master@{#636530}
-
Sam Goto authored
We use ints for capturing and passing around deltas of time. This CL moves all of those uses to base::TimeDelta, which benefits us by being clearer about units (e.g. seconds, mins, etc) and semantics in tests. Bug: 878979 Change-Id: I5ad1cfc105882b63af7a974a72576212c773cb4a Reviewed-on: https://chromium-review.googlesource.com/c/1492991 Commit-Queue: Sam Goto <goto@chromium.org> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Reviewed-by:
-
Xida Chen authored
Bug: None Change-Id: I0cf1b3155c0fc2e9bfac6396dd45edd8a2d1ca3e Reviewed-on: https://chromium-review.googlesource.com/c/1494726Reviewed-by:
Navid Zolghadr <nzolghadr@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#636528}
-
Etienne Bergeron authored
This CL is removing the thread and using a task runner instead. I propose to continue this migration by renaming the thread service since it's no longer a thread. R=fdoray@chromium.org, gab@chromium.org BUG=936569 Change-Id: If65dfd41406d13c9f69036d71e75242ef29f9b1d Reviewed-on: https://chromium-review.googlesource.com/c/1492369Reviewed-by:
François Doray <fdoray@chromium.org> Reviewed-by:
Dominik Röttsches <drott@chromium.org> Commit-Queue: Etienne Bergeron <etienneb@chromium.org> Cr-Commit-Position: refs/heads/master@{#636527}
-
chrome://flags/#enable-gamepad-vibrationMatt Reynolds authored
Removes the GamepadVibration content feature and the corresponding entry in chrome://flags. BUG=933443 Change-Id: Ic20cb81faf172381ef5ffdb1f8022772408b3441 Reviewed-on: https://chromium-review.googlesource.com/c/1487525Reviewed-by:
-
Tom Anderson authored
See the comments added in this CL for details. BUG=429404 R=sky Change-Id: Icc5bad8e70853a62f76640b111a89f9e6b487d4b Reviewed-on: https://chromium-review.googlesource.com/c/1481125 Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Auto-Submit: Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
-
Jenny Zhang authored
Bug: 932058 Change-Id: I139538ff5bf93d61229e682bb04b2d38b758e4d3 Reviewed-on: https://chromium-review.googlesource.com/c/1492975Reviewed-by:
-
Akihiro Ota authored
Bug: 934101 Change-Id: I4dc128287e7d408d6608b1170683b5f581dcc8ef Reviewed-on: https://chromium-review.googlesource.com/c/1495434Reviewed-by:
David Tseng <dtseng@chromium.org> Commit-Queue: Akihiro Ota <akihiroota@chromium.org> Cr-Commit-Position: refs/heads/master@{#636523}
-
Jonathan Metzman authored
Speculative fix for Mac libFuzzer build breakage. Bug: 936849,831914 Change-Id: I7705682b79a9835ec014504f436af9cab83c01a3 Reviewed-on: https://chromium-review.googlesource.com/c/1494724 Auto-Submit: Jonathan Metzman <metzman@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Reviewed-by:
Max Moroz <mmoroz@chromium.org> Commit-Queue: Jonathan Metzman <metzman@chromium.org> Cr-Commit-Position: refs/heads/master@{#636522}
-
