- 27 Aug, 2018 40 commits
-
-
Eriko Kurimoto authored
The way to store logs and filter output is general in this patch. Other log type can be easily implemented. In future, console.log output will be removed. Bug: 874349 Change-Id: I4c54869cb23a700cccf6e9f8426c168d7bcf334f Reviewed-on: https://chromium-review.googlesource.com/1177205Reviewed-by:
David Tseng <dtseng@chromium.org> Reviewed-by:
Yuki Awano <yawano@chromium.org> Commit-Queue: Eriko Kurimoto <elkurin@google.com> Cr-Commit-Position: refs/heads/master@{#586212}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/51e736ca..13f46245 Please follow these instructions for assigning/CC'ing issues: https://github.com/v8/v8/wiki/Triaging%20issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I93d22d97bf1bab0f58c2a9b5483384eaa3b42ebb Reviewed-on: https://chromium-review.googlesource.com/1189553Reviewed-by:
V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#586211}
-
Trent Apted authored
r586060 added suppressions for Win7 but these flake on Mac as well. TBR=foolip@chromium.org Bug: 877104 Change-Id: Ic2f72440b1194ab493c165882d9bc50455eb53fc Reviewed-on: https://chromium-review.googlesource.com/1189509Reviewed-by:
Trent Apted <tapted@chromium.org> Commit-Queue: Trent Apted <tapted@chromium.org> Cr-Commit-Position: refs/heads/master@{#586210}
-
Noel Gordon authored
Most tests herein are promise-based. Having a few tests in StepsRunner is not great. Let promises win in this file. Bug: 877557 Change-Id: I0f778870684d3e55f038c1a5317f5c86983e747c Reviewed-on: https://chromium-review.googlesource.com/1189269 Commit-Queue: Noel Gordon <noel@chromium.org> Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Cr-Commit-Position: refs/heads/master@{#586209}
-
Sam McNally authored
The file manager integration tests currently have no coverage for offline Drive. Add tests to ensure the file chooser dialog allows the selection of Drive files that are available offline while offline. These tests only run with DriveFS enabled due to the lack of controls available to set up the test scenarios with the existing Drive sync client. Bug: 876973 Change-Id: I81e39fba868a073fd82a457004700bb0ebb566ec Reviewed-on: https://chromium-review.googlesource.com/1189515 Commit-Queue: Sam McNally <sammc@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#586208}
-
Gabriel Charette authored
R=grt@chromium.org https://chromium-review.googlesource.com/c/chromium/src/+/1178889 Bug: Shouldn't need an extra base OWNER for CLs like Change-Id: I3bfc9de274b7843a714b94b3b9e2dc74890fd88f Reviewed-on: https://chromium-review.googlesource.com/1188486Reviewed-by:Greg Thompson <grt@chromium.org> Commit-Queue: Greg Thompson <grt@chromium.org> Cr-Commit-Position: refs/heads/master@{#586207}
-
Trent Apted authored
Its comparator was rubbish and always has been. Array.prototype.sort() takes a function that should return {-1, 0, 1}, not bool. TBR=benwells@chromium.org Bug: 877890 Change-Id: I65162d2b261ad4ff91a028bf62c0cdcfb765df27 Reviewed-on: https://chromium-review.googlesource.com/1188736Reviewed-by: -
Noel Gordon authored
Load only the file needed for the test (for speed and simplicity), use appId, document each test step. Bug: 877557 Change-Id: I70a82b5334047587c5b426639347bf42c33d391d Reviewed-on: https://chromium-review.googlesource.com/1188734Reviewed-by:
-
Yuichiro Hanada authored
This is a reland of a0f6eb42. It was reverted by Findit in crrev.com/c/1188826, but the revert didn't fix the broken tests and another change fixed them. Bug: 845079 TBR=yusukes@chromium.org,michaelpg@chromium.org Original change's description: > Allow to use ARC IMEs only in tablet mode. > > This CL also changes InputMethodManagerImpl and language settings api to > allow ArcInputMethodManagerService to restrict ARC IMEs. > > Bug: 845079 > Test: Ran on DUT and unit tests. > Change-Id: I61516b3c6a65775f42aae7e51583e933d55ab1b6 > Reviewed-on: https://chromium-review.googlesource.com/1179733 > Reviewed-by: Michael Giuffrida <michaelpg@chromium.org> > Reviewed-by: Yusuke Sato <yusukes@chromium.org> > Commit-Queue: Yuichiro Hanada <yhanada@chromium.org> > Cr-Commit-Position: refs/heads/master@{#586121} Change-Id: I7f74b93c3a246f4c7379b1c3c1dd6eb349effc22 Reviewed-on: https://chromium-review.googlesource.com/1189268Reviewed-by:
Yuichiro Hanada <yhanada@chromium.org> Reviewed-by:
Michael Giuffrida <michaelpg@chromium.org> Commit-Queue: Yuichiro Hanada <yhanada@chromium.org> Cr-Commit-Position: refs/heads/master@{#586204}
-
Tatsuhisa Yamaguchi authored
Shows buttons when swipe control is opened by horizontal scroll of a notification box. The buttons triggers same action just like the existing control buttons inside MessageView for mouse. Test: ash_unittests --gtest_filter=MessageCenterViewTest.*:MessageListViewTest.* Test: manual Bug: 840497 Change-Id: I6ab456cda8dd1f2de5c885e9c28492bf00ac8cd3 Reviewed-on: https://chromium-review.googlesource.com/1188044 Commit-Queue: Tatsuhisa Yamaguchi <yamaguchi@chromium.org> Reviewed-by:
Yoshiki Iguchi <yoshiki@chromium.org> Cr-Commit-Position: refs/heads/master@{#586203}
-
Noel Gordon authored
Most tests herein are promise-based. Having a few tests in StepsRunner is not great. Let promises win in this file. Bug: 877557 Change-Id: Idc075946864b89a17f0e6b887323dbae361e5564 Reviewed-on: https://chromium-review.googlesource.com/1189266Reviewed-by:
-
Maksim Sisov authored
This is a preliminary work before introducing frame and presentation callbacks. Summary: It's too much for WaylandConnection to hold that much functionality. Instead, move the buffer management mechanism to its own WaylandBufferManager class. It's mostly moving code around with no functionality changes except that CreateBuffer, SwapBuffer and DestroyBuffer return the result of their job. On false, an error message is set and WaylandConnection uses it when calling TerminateGpuProcess. In followup CLs, I will make the buffer management easier. That will allow us to use frame callbacks in quite a nice way. Bug: 820047 Change-Id: Ib64d4d5d3e4c64bd7e95154e8d280509bbdac8b6 Reviewed-on: https://chromium-review.googlesource.com/1179835 Commit-Queue: Maksim Sisov <msisov@igalia.com> Reviewed-by:
Robert Kroeger <rjkroege@chromium.org> Reviewed-by:
Antonio Gomes <tonikitoo@igalia.com> Cr-Commit-Position: refs/heads/master@{#586201}
-
Noel Gordon authored
Use appId, document all test steps, use precise selectors when dealing with the #file-list [renaming] element and its <input> (exactly as per the testRenameFolder test below), check step return results. Bug: 877557 Change-Id: If57085de229f8213852d0fd1730871a5ad059004 Reviewed-on: https://chromium-review.googlesource.com/1189516Reviewed-by:
-
afdo-chromium-autoroll authored
This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 The AutoRoll server is located here: https://autoroll.skia.org/r/afdo-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=gbiv@chromium.org Change-Id: I7feaf9686e534953ea52b4a5e7c7a0bf74b98df9 Reviewed-on: https://chromium-review.googlesource.com/1189552Reviewed-by:
afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#586199}
-
Tatsuhisa Yamaguchi authored
This change adds a new container view between MessageListView and MessageView. The new view is intended to host buttons views for swipe control. This change also returns slided notifications when another notification swipe is started, so as to ensure only one swipe control can be opened. Bug: 840497 Change-Id: Ica92933a8d3f5d92caa43a5c926252681873ede1 Reviewed-on: https://chromium-review.googlesource.com/1184724Reviewed-by:
-
David Staessens authored
This seems to be caused by the decoder thread waiting for an EGL sync that will never come, when queuing an output buffer. Some changes are introduced to make sure that: * Waiting for an EGL sync is no longer blocking and can be interrupted. * Any tasks queued will check whether a destroy is pending upon starting, and early-exit if required. TEST=ran VDA tests on kevin Bug: 845645 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: I0c50ca1348a834d75899ce38f746929c67bd4a6f Reviewed-on: https://chromium-review.googlesource.com/1133614 Commit-Queue: David Staessens <dstaessens@chromium.org> Reviewed-by:
Pawel Osciak <posciak@chromium.org> Cr-Commit-Position: refs/heads/master@{#586197}
-
catapult-chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/bc2c0a930728..b6bda5336f20 git log bc2c0a930728..b6bda5336f20 --date=short --no-merges --format='%ad %ae %s' 2018-08-27 sadrul@chromium.org rendering: Fix for null browser thread. Created with: gclient setdep -r src/third_party/catapult@b6bda5336f20 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:877761 TBR=sullivan@chromium.org Change-Id: I693be47b4ca1ab080ad61d54051c782c77c2f69f Reviewed-on: https://chromium-review.googlesource.com/1188807Reviewed-by:
catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#586196}
-
v.paturi authored
In render_widget_host_view_android.cc FloatEquals() function is implemented. This implementaion already exists in cc/base/math_util as IsFloatNearlyTheSame(). So the FloatEquals() implementation is removed and is replaced with IsFloatNearlyTheSame() in the calling functions. Bug: None Change-Id: I84dd6fc29475e59cbbac6e953c8f0093f9f972c5 Reviewed-on: https://chromium-review.googlesource.com/1177218Reviewed-by:
Eric Karl <ericrk@chromium.org> Commit-Queue: Prashant Nevase <prashant.n@samsung.com> Cr-Commit-Position: refs/heads/master@{#586195}
-
Noel Gordon authored
waitAndAcceptDialog - document all steps herein, use appId. getTreeItems => getVisibleDirectoryTreeItemNames - name it by what is actually does, use appId. waitForDirectoryTreeItem, waitForDirectoryTreeItemLost - include directory in their names, use appId. keyboardCopy - remove unused |callback| argument, use appId. keyboardDeleteFolder - remove "directory" from the name to minimize the folder/directory naming dichotomy. testRenameFolder - use waitForElement in a consistent way. Bug: 877557 Change-Id: I8e9bd30bf98743764a0a4d7b9652a4854a52ee13 Reviewed-on: https://chromium-review.googlesource.com/1189512Reviewed-by: -
Trent Apted authored
TBR=twellington@chromium.org Bug: 877774 Change-Id: I868883a6a4b841dd6b3a94df813e8da23cc6887c Reviewed-on: https://chromium-review.googlesource.com/1189263 Commit-Queue: Trent Apted <tapted@chromium.org> Reviewed-by:
-
Stuart Langley authored
Part of ongoing work to cleanup various file system callbacks from repeating to once callback, to match the actual desired semantics of the operaton flow. Introduces no logic changes. Bug: 875700 Change-Id: I7f4c7a82e2d9a8b07bce67b683a5d1ab8d5eb39c Reviewed-on: https://chromium-review.googlesource.com/1188729Reviewed-by:
Anand Mistry <amistry@chromium.org> Commit-Queue: Stuart Langley <slangley@chromium.org> Cr-Commit-Position: refs/heads/master@{#586192}
-
Stuart Langley authored
AboutResource has an internal caching mechanism, that is only refreshed when UpdateAboutResource is called. With the introduction of team drives UpdateAboutResource is no longer called to get the largest change id, which means that the cached version can become stale. Here we introduce a timer that will periodically evict that cached version, so that calls to GetAboutResource will get fresh data from the server. Bug: 874551 Change-Id: Ib0ed943b2abec95c6d32be17228dd429ffedaea8 Reviewed-on: https://chromium-review.googlesource.com/1189684 Commit-Queue: Stuart Langley <slangley@chromium.org> Reviewed-by:
Sam McNally <sammc@chromium.org> Cr-Commit-Position: refs/heads/master@{#586191}
-
Matt Falkenhagen authored
Bug: 795989 Change-Id: I8b275dfeaab7f4f08f2a70130b74f98a344bed72 Reviewed-on: https://chromium-review.googlesource.com/1188728Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Commit-Queue: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#586190}
-
afdo-chromium-autoroll authored
This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 The AutoRoll server is located here: https://autoroll.skia.org/r/afdo-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=gbiv@chromium.org Change-Id: Ie27c16cc2de9ef38ffcbde555f047e3dddf0841c Reviewed-on: https://chromium-review.googlesource.com/1189708Reviewed-by:
-
Kunihiko Sakamoto authored
Bug: 865852 Change-Id: I3dea747eca69722f2abfbfdebd5d7e05eeabf743 Reviewed-on: https://chromium-review.googlesource.com/1189508Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#586188}
-
Becky Zhou authored
Use tab interactivity if tab model is not found in the tab model list. Bug: 875595 Change-Id: I5fd69ed11e2f30733a25eaa98e353a98fc026a5e Reviewed-on: https://chromium-review.googlesource.com/1188753Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Commit-Queue: Becky Zhou <huayinz@chromium.org> Cr-Commit-Position: refs/heads/master@{#586187}
-
Trent Apted authored
TBR=grt@chromium.org Bug: 877815 Change-Id: Ie8145b1bce2354365fc0284374bef442e67cf10c Reviewed-on: https://chromium-review.googlesource.com/1189510 Commit-Queue: Trent Apted <tapted@chromium.org> Reviewed-by:
-
Trent Apted authored
Equality for chrome.app.window.AppWindow objects is not well-defined. In fact, testGetAllMultipleWindows was passing even though it was comparing arrays in different orders. Fix the tests by comparing the `id` property of the objects. Bug: 877129 Change-Id: I1a262b5f17c97320f9602f5d4251a044ec49220e Reviewed-on: https://chromium-review.googlesource.com/1188727Reviewed-by:
Ben Wells <benwells@chromium.org> Commit-Queue: Trent Apted <tapted@chromium.org> Cr-Commit-Position: refs/heads/master@{#586185}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=govind@chromium.org Change-Id: I9d69ae47cad64ee01e4635f78d22d4059c07db0e Reviewed-on: https://chromium-review.googlesource.com/1189210Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#586184}
-
Jinsuk Kim authored
Moves |WebContents.isSelectPopupVisibleForTesting| from the public interface to test-only util class. Bug: 875742 Change-Id: I51e5368b862cf1bbe4fd94ee0bba8435ae1e35a5 Reviewed-on: https://chromium-review.googlesource.com/1180943 Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Reviewed-by:
-
Raymes Khoury authored
This removes content settings set for embedded sites for the geolocation, protected media and midi sysex permissions when permission delegation is enabled. If one of these permissions is set, the permission for the top level origin will also be reset. This is because some users may have allowed a top level origin while blocking a site embedded in it. In those cases the top level site could delegate permission to an embedded site they had previously blocked. Clearing access to the top level site gives those users another opportunity. Bug: 802945 Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: Ie858ff005078326d9b04b82a03ebc9febe81aebe Reviewed-on: https://chromium-review.googlesource.com/1166620 Commit-Queue: Raymes Khoury <raymes@chromium.org> Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Martin Šrámek <msramek@chromium.org> Reviewed-by:
Varun Khaneja <vakh@chromium.org> Cr-Commit-Position: refs/heads/master@{#586182}
-
Stuart Langley authored
Part of ongoing work to cleanup various file system callbacks from repeating to once callback, to match the actual desired semantics of the operaton flow. Introduces no logic changes. Bug: 875700 Change-Id: I397368e27816ec11262e2cb4501677f7ccc02623 Reviewed-on: https://chromium-review.googlesource.com/1188725Reviewed-by:
-
Noel Gordon authored
Sending Enter to the file-list container after sending an Enter key to the list renaming text input element causes flaky failures on the bots due to [renaming] complete racing with the processing of the file-list container Enter key handling. To verify that the Folder cannot be entered while it is being renamed, send Enter to the file-list container before sending Enter to the text input [renaming] element. Bug: 874954,877557,410163 Change-Id: Icf8ec215b4a4658e16940ab8ce9b1778f19f6235 Reviewed-on: https://chromium-review.googlesource.com/1188726Reviewed-by:
-
Trent Apted authored
Fails reliably on macOS 10.12 since https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac10.12%20Tests/15035 NOTRY=true TBR=dpapad@chromium.org, scottchen@chromium.org, rbpotter@chromium.org Bug: 877109, 876990 Change-Id: I360d6766bffd48178894d9023fcc1758c0e7eba3 Reviewed-on: https://chromium-review.googlesource.com/1189683 Commit-Queue: Trent Apted <tapted@chromium.org> Reviewed-by:
-
Alan Cutter authored
Currently it's not obvious how to remove a PWA on platforms other than Chrome OS. The user needs to navigate to chrome://apps, right click icon and pick "Remove from Chromium". This CL adds a hosted app menu option to uninstall the hosted app. Screenshots: Menu option: https://bugs.chromium.org/p/chromium/issues/attachment?aid=354298&signed_aid=_QBTIue6dZ9AK09Q11Ppzw==&inline=1 Confirmation: https://bugs.chromium.org/p/chromium/issues/attachment?aid=354299&signed_aid=XgFqjDNSIfIOnosVYz-B6w==&inline=1 Disabled option: https://bugs.chromium.org/p/chromium/issues/attachment?aid=354300&signed_aid=GLxQI_0xEXHLyc8ZG3IKwA==&inline=1 Bug: 876560 Change-Id: Idc95eb5f8f48db5033cd61a944c7d172fe96842b Reviewed-on: https://chromium-review.googlesource.com/1184128 Commit-Queue: Alan Cutter <alancutter@chromium.org> Reviewed-by:
Giovanni Ortuño Urquidi <ortuno@chromium.org> Reviewed-by:
Finnur Thorarinsson <finnur@chromium.org> Cr-Commit-Position: refs/heads/master@{#586178}
-
Yoshisato Yanagisawa authored
Bug: 874754 Change-Id: Id9ef555874ddf4977d11f47ae0ee6d168d536b1e Reviewed-on: https://chromium-review.googlesource.com/1188214 Commit-Queue: Yoshisato Yanagisawa <yyanagisawa@chromium.org> Reviewed-by:
Ryan Tseng <hinoka@chromium.org> Cr-Commit-Position: refs/heads/master@{#586177}
-
Noel Gordon authored
Comment only change, no change in behavior. Bug: 876267 Change-Id: Ia5d46aafb094ea8e01ba5ec40397742b4a2d0dc9 Reviewed-on: https://chromium-review.googlesource.com/1189243Reviewed-by:
-
Yue Li authored
Bug: 867919 Test: Local Compile Change-Id: Icf219704c8640b5112ed9c3b434643757fda4688 Reviewed-on: https://chromium-review.googlesource.com/1183947 Commit-Queue: Yue Li <updowndota@chromium.org> Reviewed-by:
Markus Heintz <markusheintz@chromium.org> Cr-Commit-Position: refs/heads/master@{#586175}
-
Jinsuk Kim authored
Java UserDataHost/UserData is modeled after native C++ SupportsUserData/Data class to allow users to attach random class/data to a 'host' class by key. Considering the limitation of Java disallowing multiple inheritance, UserData itself is designed as interface, and UserDataHost a final class that a host class defines as member variable. Host class Foo exposes UserDataHost so that the classes to be attached to Foo can be managed without Foo actually knowing about them. An object of FooBar can be retrieved from UserHostData of Foo by: public class Foo { // Defines the container. private final UserDataHost mUserDataHost = new UserDataHost(); public UserDataHost getUserDataHost() { return mUserDataHost; } } public class FooBar implements UserDataHost.UserData { public FooBar from(UserDataHost host) { FooBar foobar = host.getUserData(FooBar.class); // Instantiate FooBar upon the first access. return foobar != null ? foobar : host.setUserData(FooBar.class, new FooBar()); } } Foo foo = new Foo(); ... FooBar bar = FooBar.from(foo.getUserDataHost()); ... The design doc is here: https://goo.gl/2uWDja The method |destroy| is defined in Userdata interface to have the lifecycle entirely under control. Note that it is not *yet* possible to make it work for WebView. Change-Id: Iaae038a2b6577b07328917724c610c4efda9bb2e Reviewed-on: https://chromium-review.googlesource.com/1179507Reviewed-by:Tommy Nyquist <nyquist@chromium.org> Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Cr-Commit-Position: refs/heads/master@{#586174}
-
Stuart Langley authored
Start changing various file system callback types to be once callback rather than the default repeating callback. They are only repeating callback because that was the previous default and this can introduce subtle and hard to find bugs that would be more obvious if the types were once callback. An example of this is crbug.com/875140. Bug: 875700 Change-Id: I3f37be3ca9f7622116db83fae287056203ff723e Reviewed-on: https://chromium-review.googlesource.com/1187859Reviewed-by:
Joel Hockey <joelhockey@chromium.org> Reviewed-by:
-
