- 22 Oct, 2019 40 commits
-
-
Rafael Cintron authored
Now that all of the work on the Chromium and Dawn side to support Windows has been complete, we need to add WebGPU to about:flags on Windows. Bug: 966580 Change-Id: I41d9f892be0d849c5ece1d5569f98344a7a92a1e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873383Reviewed-by:
Sunny Sachanandani <sunnyps@chromium.org> Commit-Queue: Rafael Cintron <rafael.cintron@microsoft.com> Cr-Commit-Position: refs/heads/master@{#708405}
-
Yuwei Huang authored
Token upgrader does not work on hosts registered with non-robot account and new API server does not handle heartbeat without a robot account, so this CL removes code in remoting_me2me_host.cc that handles non-robot account. Bug: 987383 Change-Id: Ida49880e1f5458472c8b6c983df6c1fe4ef0ab3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872726Reviewed-by:
Jamie Walch <jamiewalch@chromium.org> Commit-Queue: Yuwei Huang <yuweih@chromium.org> Auto-Submit: Yuwei Huang <yuweih@chromium.org> Cr-Commit-Position: refs/heads/master@{#708404}
-
Klaus Weidner authored
The runtime_manager_->GetImmersiveRuntime() call only returned a VR runtime, ignoring AR runtimes such as ARCore for immersive-ar. However, various code locations were using it in ways that suggest they expect it to be the currently-active runtime. Rename GetImmersiveRuntime to GetImmersiveVrRuntime, add a separate GetImmersiveArRuntime function, and GetCurrentlyPresentingImmersiveRuntime that returns either the VR or AR runtime if active, or nullptr if none is presenting. (This is different from GetImmersiveVrRuntime which returns the VR runtime even when that's not presenting.) Also rename BrowserXRRuntime methods: GetPresentingVRService => GetServiceWithActiveImmersiveSession, ExitVrFromPresentingService => ExitActiveImmersiveSession Change-Id: I241870a69034dccc1a908fe89ced2a90a8751b1f Bug: 1014159 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865043 Commit-Queue: Klaus Weidner <klausw@chromium.org> Reviewed-by:
Alexander Cooper <alcooper@chromium.org> Reviewed-by:
Piotr Bialecki <bialpio@chromium.org> Cr-Commit-Position: refs/heads/master@{#708403}
-
Scott Violet authored
I only added this to the public API as that is the important part. BUG=none TEST=none Change-Id: I2369ea07fcac9e3bb87632f6235f11e37d5283a4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874587 Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#708402}
-
Jay Harris authored
This is necessary so observers know when to remove themselves, as they might otherwise attempt to remove themselves after the ShortcutManager has been destroyed, resulting in a use after free. Bug: 860581 Change-Id: I93f0d4020efdc5633462c8066b47a0a98922e373 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872083Reviewed-by:
Alexey Baskakov <loyso@chromium.org> Commit-Queue: Jay Harris <harrisjay@chromium.org> Cr-Commit-Position: refs/heads/master@{#708401}
-
Josh Simmons authored
This is unneeded. Bug: 1013380 Test: Built and fetched hints on device. Change-Id: I9f7d3fbfc15d199e14d6c760dfe3d0fb41363ba2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873344Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Commit-Queue: Josh Simmons <jds@google.com> Cr-Commit-Position: refs/heads/master@{#708400}
-
Tom Anderson authored
BUG=1016035 R=dalecurtis Change-Id: I3c12fe8c339ab326d910699739e289b5e9aaa343 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872724 Auto-Submit: Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/master@{#708399}
-
Quinten Yearsley authored
Buildbot is dead; this is meant to be the first of several CLs to clean up related code in blinkpy. Notes about changes here: - --build-name doesn't appear to be used anywhere - step name is usually not webkit_tests in practice - I don't know exactly how --master-name is used now but it's definitely not actually Buildbot master name now. Bug: 1002702 Change-Id: I318d6149b81609c100d5475ea35de0378fd094f1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872917 Commit-Queue: Quinten Yearsley <qyearsley@chromium.org> Reviewed-by:
Robert Ma <robertma@chromium.org> Cr-Commit-Position: refs/heads/master@{#708398}
-
Ted Meyer authored
A floating message box that looks like this: https://files.tedm.io/popup.png Bug: 794255 Change-Id: Icf73a6c1d92f96b61f27329bf02e4391a03209c0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873345 Commit-Queue: Ted Meyer <tmathmeyer@chromium.org> Reviewed-by:
-
Steven Bennetts authored
This is similar to: https://chromium-review.googlesource.com/c/chromium/src/+/1836178 Except for Service properties instead of Device properties. The problem was found in: https://chromium-review.googlesource.com/c/chromium/src/+/1864626 Ths probably only affects tests, but in theory there could be an edge case on devices as well. Bug: 1015493 Change-Id: I93987961596b3fba7cb8c7c4f7fde5c0b44ea738 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873381Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Commit-Queue: Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/heads/master@{#708396}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/dd075112b8d6..6e9cdb62e782 git log dd075112b8d6..6e9cdb62e782 --date=short --no-merges --format='%ad %ae %s' 2019-10-22 xiyuan@google.com chrome_util: Ensures to-be-copied dirs end with '/' 2019-10-22 dburger@chromium.org Don't run unit tests for grunt-kernelnext-paladin. Created with: gclient setdep -r src/third_party/chromite@6e9cdb62e782 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/chromite-chromium-autoroll Please CC chrome-os-gardeners@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel TBR=chrome-os-gardeners@google.com Bug: None Change-Id: I3adac69a081f1cb1a37b7c6f67cdd87aa4374d48 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874494Reviewed-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@{#708395}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/443f286e0cca..bef344f7017f git log 443f286e0cca..bef344f7017f --date=short --no-merges --format='%ad %ae %s' 2019-10-22 perezju@chromium.org [Telemetry] Fix TODO in story_runner_unittest.py Created with: gclient setdep -r src/third_party/catapult@bef344f7017f If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/catapult-autoroll Please CC rmhasan@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=rmhasan@google.com Bug: chromium:1008852 Change-Id: I7b50e6af116558a4dacfa187d75aace8e6d716a5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874496Reviewed-by:
-
Alex Newcomer authored
Noticed this laying around. Change-Id: Ie609d1fbb2c2a73e64f063ed3b094c287e64c446 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872793Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Alex Newcomer <newcomer@chromium.org> Cr-Commit-Position: refs/heads/master@{#708393}
-
Alex Newcomer authored
Just noticed this laying around, might aswell remove it. Change-Id: I24f7df5c675902484bc9143f231820f3b9304311 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872792Reviewed-by:
-
Luke Halliwell authored
Fixed: 1016414 Change-Id: Iaf0b71ed1bdae5f8e10391c2338f91bfac8f78b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872766 Auto-Submit: Luke Halliwell <halliwell@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Commit-Queue: Luke Halliwell <halliwell@chromium.org> Cr-Commit-Position: refs/heads/master@{#708391}
-
Toni Barzic authored
Fixes the test when hotseat is enabled - the issue was that the app list layout changes when the first test window is created (because the shelf height changes), and the expected apps grid bounds were calculated before a test window existed. BUG=1016822 Change-Id: I88881ac6b5ecf0a5b3bd02c222632d5faaf72517 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873988Reviewed-by:
Alex Newcomer <newcomer@chromium.org> Commit-Queue: Toni Baržić <tbarzic@chromium.org> Cr-Commit-Position: refs/heads/master@{#708390}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/78150fbefe75..8e8e4f75129b Created with: gclient setdep -r src-internal@8e8e4f75129b If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC jbudorick@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=jbudorick@google.com Bug: chromium:None Change-Id: Id140d6a5ec5a6195d1a48a733222f9ea8601373f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874495Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#708389}
-
Ryan Sturm authored
Currently, we are blocked on Load Event, but we should move to x seconds after commit instead. Bug: 1016553 Change-Id: Ic1ec95fd543e0b50a4541a7d860b1ce40baae2d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872423 Commit-Queue: Ryan Sturm <ryansturm@chromium.org> Reviewed-by:
Robert Ogden <robertogden@chromium.org> Cr-Commit-Position: refs/heads/master@{#708388}
-
Chris Mumford authored
This change switches from using testing::CreateFunctor when calling testing::Invoke() to a C++ lambda. This improves test readibility and makes easier an upcoming changes to gmock_mutant.h (switch away from base::Bind()). Bug: 1007833, 806952 Change-Id: I1473a6041e0aedbc0b6f8eb212ebb918742bc7c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872815Reviewed-by:
Dan Sanders <sandersd@chromium.org> Commit-Queue: Chris Mumford <cmumford@google.com> Cr-Commit-Position: refs/heads/master@{#708387}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/9122bec28506..be1fa7d8cddf git log 9122bec28506..be1fa7d8cddf --date=short --no-merges --format='%ad %ae %s' 2019-10-22 tobine@google.com Vulkan: Enable VK_EXT_line_rasterization Created with: gclient setdep -r src/third_party/angle@be1fa7d8cddf If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC jonahr@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=jonahr@google.com Bug: None Change-Id: I73828185c6dcb1b631689ed0a954e06f526189fd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874493Reviewed-by:
-
Nick Harper authored
Change-Id: Ia154142e6a5014965da9220d5cc90367b811740c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873990 Commit-Queue: Nick Harper <nharper@chromium.org> Auto-Submit: Nick Harper <nharper@chromium.org> Reviewed-by:
Renjie Tang <renjietang@chromium.org> Cr-Commit-Position: refs/heads/master@{#708385}
-
siyua authored
It was missed in the original CL Bug: 964127 Change-Id: I836cd53f502c354f38cf074866a54d13d7e13419 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869540Reviewed-by:
Peter Boström <pbos@chromium.org> Commit-Queue: Siyu An <siyua@chromium.org> Cr-Commit-Position: refs/heads/master@{#708384}
-
Tom Anderson authored
Shared memory segments created with shmget(..., 0600) only allows rooted processes to attach to the segment. In situations where X11 is running rootless, like with unetbootin, additional permissions are required for the segment. This CL changes the permissions to 0606 to fix this issue. This fixes WPT failures to unblock then from upgrading Chrome to M79. BUG=1014629 R=rjkroege CC=smcgruer Change-Id: Ib28ebd06e6bcc58d7d84cf5c195101ac255f2a8a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872948 Auto-Submit: Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Robert Kroeger <rjkroege@chromium.org> Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/master@{#708383}
-
Etienne Pierre-doray authored
This CL represents the entry count in tracing CFI table directly instead of index size in bytes. This makes the format simpler to parse. Bug: 989103 Change-Id: Ia025c053290855944755a0c6805501258008e726 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872799 Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org> Reviewed-by:
Mike Wittman <wittman@chromium.org> Reviewed-by:
ssid <ssid@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#708382}
-
David Black authored
Previously non-http/https schemes were allowed. Bug: b:143156047 Change-Id: I01074dc64dcb5f39e45f3198ad8897946d91090f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873111 Commit-Queue: David Black <dmblack@google.com> Reviewed-by:
Tao Wu <wutao@chromium.org> Cr-Commit-Position: refs/heads/master@{#708381}
-
Tomasz Wiszkowski authored
It appears that we have a non-trivial number of answer suggestions that are either of invalid, or unspecified type. We have been largely unaware of this situation since the original code used value of 0 to mark an unspecified suggestion type; this value has never beed handled by PropertyModel, since the implicit value for int property is 0 (ergo no update detected). In current model we explicitly determine decoration type at the time suggestion is processed and prepare suggestion drawable instead. Bug: 1016236 Change-Id: I83800041f563bf18e2a918b7e405af8ce84910f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873878Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Ender <ender@google.com> Cr-Commit-Position: refs/heads/master@{#708380}
-
Alex Newcomer authored
Seems un-used. Change-Id: Iab2b42bdc5af8d8a37d33123ce50081b66fc5eb1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874630Reviewed-by:
-
Ahmed Fakhry authored
This was a rgression caused by a previous CL of mine https://crrev.com/c/1865543. Using the developer keyboard shortcut to enable tablet mode should force the overview tray button visible even though the internal input events are not being blocked. BUG=1016594, 925087 TEST=Manually, added a new test. Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872468Reviewed-by:
-
Chris Mumford authored
Several tests were using testing::CreateFunctor unnecessarily. gmock's testing::Invoke() already supports a function pointer as an argument. This change simplifies the tests and upcoming refactoring to the functor implementation in gmock_mutant.h. Bug: 1007833, 806952 Change-Id: Ifca2fdc2364b770761f2da9f6d2b36a95b5c1547 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874050Reviewed-by:
Filip Gorski <fgorski@chromium.org> Commit-Queue: Chris Mumford <cmumford@google.com> Cr-Commit-Position: refs/heads/master@{#708377}
-
Min Qin authored
we are still investigating the high interruption issue BUG=1016399 Change-Id: I54eb9231fa1bce657a2d778570baca565806248f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872890Reviewed-by:
-
Etienne Bergeron authored
This CL has no behavior change. It is a simple optimisation that avoid doing two lookups in the map. The iterator returns by map::find is able to do both queries. R=robliao@chromium.org, asvitkine@chromium.org Change-Id: If6dc1c90914e0f5f7c6616d47f7a0325cfda93da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872308Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Robert Liao <robliao@chromium.org> Commit-Queue: Etienne Bergeron <etienneb@chromium.org> Cr-Commit-Position: refs/heads/master@{#708375}
-
Christopher Thompson authored
We want to be able to be able to compare user behavior when they see the legacy TLS deprecation warning UI against the counterfactual of "user behavior for users who would have seen a legacy TLS warning on this page if they weren't in the holdback control group". We split histograms on whether they occurred on a page that would have triggered a legacy TLS warning (i.e., legacy TLS and not in the control group of sites) or not (i.e., not legacy TLS or legacy TLS + control group). For Page Info, we want to measure interactions and time open for pages based on whether they would trigger a legacy TLS warning or not (if the user were in the proper field trial group). We split them on "Triggered"/"NotTriggered" suffixes so that we can track the underlying enum/numeric histogram for each case. Bug: 1016105 Change-Id: I0955cfba26edb4ec288f313d368dea4c3f9594e3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872301 Commit-Queue: Christopher Thompson <cthomp@chromium.org> Reviewed-by:
Mustafa Emre Acer <meacer@chromium.org> Cr-Commit-Position: refs/heads/master@{#708374}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/1486b05e..e9c6aa24 Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I5dc95a29487fb52c0fbae3eae7a200d542dd423d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874426Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#708373}
-
Brandon Jones authored
Provides a workaround for an issue with some versions of Windows Mixed Reality where the HolographicSpaceUserPresence will only ever report Absent or PresentPassive, and never PresentActive. We would ideally like to map PresentPassive to the WebXR state "visible-blurred", as their meaning is very close, but until this bug is fixed we'll need to force it to map to "visible" so that content runs correctly. Bug: 1016907 Change-Id: Icbec972fd6b62d1892609f8cf84ddf9f8190bc44 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873157Reviewed-by:
-
khmel@chromium.org authored
TEST=Locally, no crash reproduced. BUG=b:142926935 BUG=1016851 Change-Id: I518ec9ed5d03098284a55d2100425fe22987ed23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874188Reviewed-by:
Mitsuru Oshima (slow) <oshima@chromium.org> Commit-Queue: Yury Khmel <khmel@chromium.org> Cr-Commit-Position: refs/heads/master@{#708371}
-
minch authored
Bug: 1002733 Change-Id: I67ea5db271b1ad250b343a6f5c0d4183d7ccf233 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874057 Commit-Queue: Min Chen <minch@chromium.org> Reviewed-by:
-
Chris Mumford authored
Nothing in gmock_mutant.h was used in any of these source files. TBR=jam@chromium.org Bug: 1007833, 806952 Change-Id: Ifbfebfa78bfb6774dbcaed865e8127f24408419d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874060 Commit-Queue: Chris Mumford <cmumford@google.com> Reviewed-by:
Chris Mumford <cmumford@google.com> Cr-Commit-Position: refs/heads/master@{#708369}
-
Ian Struiksma authored
Disabled flaky password test of sign_in_pass/marriott with bug number. Added 6 new sites for autofill that had previously failed during record: abebooks bhphotovideo bloomingdales hayneedle sears vans Minor test recipe file updates to stabilize 4 flaky tests: catch north_face findmeagift aeropostale Updated cipd version for autofill to include new wpr/test files Bug: 984662,984664,1016437 Change-Id: I04957c4fa5d46bd1f7d57f00dfd746146ba213a0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874201 Auto-Submit: Ian Struiksma <ianstruiksma@google.com> Commit-Queue: Caleb Rouleau <crouleau@chromium.org> Reviewed-by:
Caleb Rouleau <crouleau@chromium.org> Cr-Commit-Position: refs/heads/master@{#708368}
-
rbpotter authored
This file is not used anywhere, so is only creating unnecessary additional resources.pak size on Chrome OS. Bug: 902076 Change-Id: I441e64df4cfbc0c247ee74a73d546989768bed96 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873373 Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#708367}
-
Ce Chen authored
fieldtrial_testing_config.json. Note these experiments are for desktop and Android. iOSs will be added in a different study "OmniboxOnDeviceHeadSuggestIOS" Bug: 925072 Change-Id: I557fc1f91fb9e12283bb62f957eee5dd3146f054 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872942Reviewed-by:
Mark Pearson <mpearson@chromium.org> Commit-Queue: Ce Chen <cch@chromium.org> Cr-Commit-Position: refs/heads/master@{#708366}
-
