- 13 Aug, 2020 40 commits
-
-
Caitlin Fischer authored
The test was re-enabled in crrev/c/crrev/c/2350231; however, fixing the original error uncovered an additional one: [FATAL:network_context.mojom.cc(9680)] Check failed: !connected. \ NetworkContext::ClearHttpCacheCallback was destroyed without first \ either being run or its corresponding binding being closed. It is an \ error to drop response callbacks which still correspond to an open \ interface pipe. Bug: 1096047 Change-Id: Ia4702463ab41fba49827baa93b9f15b74af21125 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354290 Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Commit-Queue: Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#797711}
-
Danila Kuzmin authored
Bug: 1108862 Change-Id: If36f057d4724f10f41558affe3900aee0d65a89d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2322827 Commit-Queue: Danila Kuzmin <dkuzmin@google.com> Reviewed-by:
Roman Aleksandrov <raleksandrov@google.com> Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#797710}
-
Yuke Liao authored
A few test suites are stable, remove the experimental label so that they're watched by sheriffs to prevent regressions. Bug: 1111979 Change-Id: I5076314717607fef7768d466ad24c79c487ae280 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2351385Reviewed-by:
Sven Zheng <svenzheng@chromium.org> Reviewed-by:
Erik Chen <erikchen@chromium.org> Commit-Queue: Yuke Liao <liaoyuke@chromium.org> Cr-Commit-Position: refs/heads/master@{#797709}
-
Chris Harrelson authored
Remove PaintHolding to make room, since the file was too big for Windows command-lines otherwise. Bug: 1115577 Change-Id: Ib2dda288cce960a1c0c43eda99487327004f4fe3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353707Reviewed-by:
-
Caitlin Fischer authored
The test case is AddSyncedUserBirthYearAndGenderToProtoData, and it's being re-enabled on Android. Bug: 1102746 Change-Id: Ie02597dc1704ba0d5efb13eb297f7e87ef0865d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2329920 Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Reviewed-by:
-
Karel Král authored
Implement initializer list support for creating arrays and dictionaries in TracedValue::Build. Thus speed up adding debugging tracing of multiple parameters, including container types. Follow-up of: crrev.com/c/2263160 Bug: 1043616 Change-Id: I2d3205d550e6ce6328ea253e6b94f9cc2cbe3098 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346286Reviewed-by:
Eric Seckler <eseckler@chromium.org> Reviewed-by:
Alexander Timin <altimin@chromium.org> Commit-Queue: Karel Král <karelkral@google.com> Cr-Commit-Position: refs/heads/master@{#797706}
-
Lambros Lambrou authored
This CL fixes the host process so that the client can successfully select a different codec after SDP offer/answer exchange is restarted during an active connection. This comes in 2 parts: 1. The current encoder in WebrtcVideoStream is reset, so that captured frames are routed to the new encoder. 2. The WebrtcVideoEncoderSelector logic is slightly tweaked so that a call to SetPreferredCodec() resets the cycle of encoders returned by repeated calls to CreateEncoder(). This is done so that the correct encoder is returned after WebrtcVideoStream changes the preferred codec. This tweak does not break any existing unittests. This CL fixes crashes which occur when the host tries to use a different encoder than what WebRTC created via the WebrtcDummyVideoEncoderFactory class. These crashes can only be triggered when SDP (or ICE) is restarted via the recently-implemented control messages, which are not supported in older versions of the host. Bug: 1113499 Change-Id: Idd1e388252c4359e1edc62ac4a51d71be0ae77cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353672 Auto-Submit: Lambros Lambrou <lambroslambrou@chromium.org> Commit-Queue: Jamie Walch <jamiewalch@chromium.org> Reviewed-by:
Jamie Walch <jamiewalch@chromium.org> Cr-Commit-Position: refs/heads/master@{#797705}
-
Victor Hugo Vianna Silva authored
Assertions made by MultiStorePasswordUiEntry/MultiStoreExceptionEntry when merging two entries [1] are failing in some cases. This causes an exception to be thrown when the list of saved passwords is being updated, which in turn results in some passwords not being shown. In this CL, we treat merge failures more gracefully, namely: - Instead of assertions, we now have merge() return whether it succeeded. - The constructor of the multi-store entries can now only have 1 argument since we can't "return a failure" when calling the constructor. - When a merge fails, we just create separate items in the UI for the entries we were trying to merge. - We rename merge() to mergeInPlace() to make its side-effect clearer. [1] https://source.chromium.org/chromium/chromium/src/+/master:chrome/browser/resources/settings/autofill_page/multi_store_password_ui_entry.js;l=51 Bug: 1114697 Change-Id: I588af43cba874510b4d685a42434aa988c90b189 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2351911Reviewed-by:
Jan Wilken Dörrie <jdoerrie@chromium.org> Commit-Queue: Victor Vianna <victorvianna@google.com> Cr-Commit-Position: refs/heads/master@{#797704}
-
Caitlin Fischer authored
The histogram is already obsolete, so it shouldn't be logged. Filed http://crbug/1114728 to stop and prevent this from happening for other histograms. Bug: 1114723 Change-Id: I2f4426b697541f94b9f96f149878149c016681b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346726Reviewed-by:
Mark Pearson <mpearson@chromium.org> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Cr-Commit-Position: refs/heads/master@{#797703}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/522a635391bd..f20a184a017f 2020-08-13 jacktfranklin@chromium.org Log errors when regenerating all component bridges 2020-08-13 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS. 2020-08-13 jacktfranklin@chromium.org Fix bridges generation of non-nullable types 2020-08-13 jacktfranklin@chromium.org Remove string literal support from bridges 2020-08-13 szuend@chromium.org [ts] Type-check ui/XLink.js with TypeScript 2020-08-13 szuend@chromium.org [ts] Type-check ui/ui.js with TypeScript 2020-08-13 szuend@chromium.org [ts] Type-check ui/SyntaxHighlighter.js with TypeScript 2020-08-13 szuend@chromium.org [ts] Type-check ui/Panel.js with TypeScript 2020-08-13 szuend@chromium.org [ts] Type-check ui/SettingsUI.js with TypeScript 2020-08-13 petermarshall@chromium.org 'themselves' in design guidelines If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.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/+doc/master/autoroll/README.md Bug: chromium:1011811 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I0d249bd7050ae11148ca41e4affa68cddd02a573 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354220Reviewed-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@{#797702}
-
Victor Costan authored
Bug: 1068710 Change-Id: Icfbf850783134ba4c019c8abecc41c6854b711ca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354233 Auto-Submit: Victor Costan <pwnall@chromium.org> Commit-Queue: Ted Choc <tedchoc@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Cr-Commit-Position: refs/heads/master@{#797701}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/dbee93ac203d..e1360ddcec9e If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-mac-chromium Please CC perfetto-bugs@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/+doc/master/autoroll/README.md Tbr: perfetto-bugs@google.com Change-Id: Ifdb9884a7f78ce923f906e24dfc3a04a9db54b0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354240Reviewed-by:
-
Viktor Semeniuk authored
This change renames old version to LegacyPasswordDetailsTableVC and new version to PasswordDetailsTableVC. Bug: 1075494 Change-Id: I998582cf9a8d0baec85e49ed36f55e7c32e65e2f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339615Reviewed-by:
Eugene But <eugenebut@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Commit-Queue: Viktor Semeniuk <vsemeniuk@google.com> Cr-Commit-Position: refs/heads/master@{#797699}
-
Annie Sullivan authored
Bug: 1112857 Change-Id: I2c76e95ecb139d3359877e71c6f3713f4d9f3c37 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2348694Reviewed-by:
Philip Rogers <pdr@chromium.org> Commit-Queue: Annie Sullivan <sullivan@chromium.org> Cr-Commit-Position: refs/heads/master@{#797698}
-
Omar Morsi authored
This CL replaces all usages of platform_keys::KeyPermissions::KeyLocations by platform_keys::TokenId. Bug: 1115575 Change-Id: I4659ab8d5c1bd8f0a6ab5d13b39e6ae39ed37998 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352932 Commit-Queue: Omar Morsi <omorsi@google.com> Reviewed-by:
Omar Morsi <omorsi@google.com> Reviewed-by:
Edman Anjos <edman@chromium.org> Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Cr-Commit-Position: refs/heads/master@{#797697}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/9e3426eb..2bc574fa 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,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I69a72838e9c9dfda17078a9e3665a7afe400a029 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353290Reviewed-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@{#797696}
-
Joe Mason authored
I have my @google.com and @chromium.org accounts linked in gerrit, so I always forget which one is treated as canonical. R=chrisha Change-Id: I860a52ced8561dcfe19e05856c13e1d413b183ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354274 Auto-Submit: Joe Mason <joenotcharles@chromium.org> Reviewed-by:
Chris Hamilton <chrisha@chromium.org> Commit-Queue: Chris Hamilton <chrisha@chromium.org> Cr-Commit-Position: refs/heads/master@{#797695}
-
Mike Jackson authored
WebAppBrowserController looks directly at the manifest to decide if minimal ui buttons should be shown or not. This change introduces a new method on the AppRegistrar to return the effective display mode only accounting for the manifest. There are other places that do a similar thing - those places will be updated in a subsequent change. I also added comments to the existing functions to help clarify how they calculate their respective DisplayMode return values. To test the change use: chrome --enable-features=WebAppManifestDisplayOverride Example websites: https://mwjacksonmsft.github.io/pwa/display-override-custom/index.html (display == browser, display_override == [standard]) Explainer: https://github.com/WICG/display-override/blob/master/explainer.m Design document: https://docs.google.com/document/d/1hEmbGVHMN38q1YTaaGccQ-Y5CHr7xIURYPRWXTuvZLo/edit?usp=sharing I2P: https://groups.google.com/a/chromium.org/d/topic/blink-dev/WvIeZT8uSzw/discussion Bug: 1109520 Change-Id: I9fb7ba1da0060e0d7b101cc4268cf9297ca7bcdc Depends-On: Ib3f7465ed36474b1166f136c3cd6655cc34add0e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2344525Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Commit-Queue: Mike Jackson <mjackson@microsoft.com> Cr-Commit-Position: refs/heads/master@{#797694}
-
Mirko Bonadei authored
Change Log: https://chromium.googlesource.com/external/github.com/abseil/abseil-cpp/+log/f66bc74928..1beb3191c2 Full diff: https://chromium.googlesource.com/external/github.com/abseil/abseil-cpp/+/f66bc74928..1beb3191c2 Bug: None Change-Id: I11f7c0d12dd3f41240445afb97972c8a4a5db748 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353450 Auto-Submit: Mirko Bonadei <mbonadei@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#797693}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/cda86eff6461..abe07b943855 2020-08-13 swiftshader.regress@gmail.com Regres: Update test lists @ cda86eff If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Please CC swiftshader-team+autoroll@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;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:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: I8c1df567d5fb7adcd227407d2ffb9002825f4381 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354211Reviewed-by:
-
nancylingwang authored
For Arc icon, the current implementation is: 1. Call the function "CreateSuperimposedImage" to generate the 'mix' image with the background and foregorund. 2. Generate the mask image based on the above 'mix' image. 3. Apply the mask image on the 'mix' image to generate the standard icon. However, the 'mix' image generated by the operation function "CreateSuperimposedImage" doesn't have the same ImageSkiaRep, and scale as the raw image: foreground image, background image. So the generated mask image has 1 ImageSkiaRep for the scale 1.0f only. Therefore in ChomeOS, the icon shown uses the ImageSkiaRep with scale 1.0, which is not a good quality. This CL refactors the LoadMaskImage to get the scale and size from the Arc foreground image, not the 'mix' generated image, to create the matched mask image for Arc icons, so that in the ChromeOS the icon shown can use the ImageSkiaRep with scale 2.0f which is better quality. BUG=1114771 Change-Id: I7564d34b0be6950516e3c25480226ecf4aac403a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353972 Commit-Queue: Nancy Wang <nancylingwang@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#797691}
-
Chris Sharp authored
Bug: 1112444 Change-Id: I28f02be439b8e5ff24c8f2b15f5fc7dced79993c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354249Reviewed-by:
Yann Dago <ydago@chromium.org> Commit-Queue: Chris Sharp <csharp@chromium.org> Cr-Commit-Position: refs/heads/master@{#797690}
-
Caroline Rising authored
There was a bug that hover cards would flash in when a tab was closed, this could be due to missing a mouse event that would have updated the hover card while the delay timer was running. This change adds a check to make sure the hover card won't be shown if the tab was destroyed while the timer was running. Bug: 982964 Change-Id: I02b95f83f28b45138e61c75fe42cd62208248093 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2349922Reviewed-by:
Dana Fried <dfried@chromium.org> Commit-Queue: Caroline Rising <corising@chromium.org> Cr-Commit-Position: refs/heads/master@{#797689}
-
Yann Dago authored
In order to support channel switching on the main installation of the browser, A switch flag "--channel" that specifies which channel of the browser is about to be installed is added to the setup's command line. This flag will be used to store the right channel value in the registry so the browser knows which channel is running. The supported values are {stable|dev|beta}. This new switch will be ignored for if any of "--chrome-beta", "--chrome-dev" and "--chrome-sxs" is found in the command line. Bug: 1102927 Change-Id: Ib7bd622e906f8f4af067307c90d0caffc73afc24 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2172210 Commit-Queue: Yann Dago <ydago@chromium.org> Reviewed-by:Greg Thompson <grt@chromium.org> Cr-Commit-Position: refs/heads/master@{#797688}
-
Naomi Musgrave authored
chrome/services/sharing/nearby/decoder/nearby_decoder_unittest.cc chrome/browser/nearby_sharing/nearby_sharing_service_impl.cc - Update usage of advertisement field to new name chrome/services/sharing/public/* - Rename advertisement field to be more accurate - Update comments to be more detailed This is a follow-on to feedback raised on Ia384e12083a590f52beb1f98d50b192ab20f31cd Bug: 1084582 Change-Id: If5a3c40ee0ad33de01bd5c4322078c4fa9b206c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352893Reviewed-by:
Alex Chau <alexchau@chromium.org> Reviewed-by:
Richard Knoll <knollr@chromium.org> Reviewed-by:
Alex Gough <ajgo@chromium.org> Reviewed-by:
Josh Nohle <nohle@chromium.org> Commit-Queue: Naomi Musgrave <nmusgrave@chromium.org> Cr-Commit-Position: refs/heads/master@{#797687}
-
Joe DeBlasio authored
This CL adds a learn more link to the Safety Tip infobar on Android that matches the one used on Desktop. It broadly mirrors what was done previously with the PermissionInfoBar. Fixed: 1096550 Change-Id: I0581be14695fec9793183489b4aae4e9e08c2bc7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353424Reviewed-by:
Mustafa Emre Acer <meacer@chromium.org> Reviewed-by:
Matthew Jones <mdjones@chromium.org> Commit-Queue: Joe DeBlasio <jdeblasio@chromium.org> Cr-Commit-Position: refs/heads/master@{#797686}
-
Dan Harrington authored
Bug: 1115137 Change-Id: I4c17c8c50ef19b84cf7af8b7e19879a890670e00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2348700Reviewed-by:
Robert Sesek <rsesek@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Reviewed-by:
Justin DeWitt <dewittj@chromium.org> Commit-Queue: Dan H <harringtond@chromium.org> Cr-Commit-Position: refs/heads/master@{#797685}
-
Amr Aboelkher authored
EXPECT_DEATH isnt supported in Chromium. Thus the tests associated with it, needs to be removed. Especially, in the mentioned tests, its no need to rewrite them. Bug: chromium:1100129 Change-Id: I0aae13e83c6b4bbc0b7112e523148712e2ff432a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2270549Reviewed-by:
Amr Aboelkher <amraboelkher@google.com> Reviewed-by:
Amr Aboelkher <amraboelkher@chromium.org> Commit-Queue: Amr Aboelkher <amraboelkher@google.com> Cr-Commit-Position: refs/heads/master@{#797684}
-
Miyoung Shin authored
This CL adds |useMojo| parameter to JavascriptInjector that would default to false and using RemoteObjectInjector method in JavascriptInjectorImpl#addPossiblyUnsafeInterface() if useMojo is true. We will add useMojo for the rest of the code when RemoteObjectInjector#removeInterface is implemented and it is available for JavascriptInjectorImpl. This change adds usage of mojom interfaces and methods, and the binary size increase is caused by generated Java bindings. Java bindings improvements (including size optimizations) are captured in https://bugs.chromium.org/u/2764092486/hotlists/java-bindings. Bug: 1105927 Binary-Size: Size increase is unavoidable (see above). Change-Id: I5d9c6d83084b3a72812382e5cbe8011a37e938e9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2331988Reviewed-by:
Bo <boliu@chromium.org> Reviewed-by:
Oksana Zhuravlova <oksamyt@chromium.org> Commit-Queue: Miyoung Shin <myid.shin@igalia.com> Cr-Commit-Position: refs/heads/master@{#797683}
-
Alex Turner authored
This will improve performance when the identifiability study is not enabled. Bug: 1102934 Change-Id: Icbbd72ff0b470ebcf762bcf04754919f568ec1d3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2337254Reviewed-by:
Florin Malita <fmalita@chromium.org> Reviewed-by:
Asanka Herath <asanka@chromium.org> Commit-Queue: Alex Turner <alexmt@chromium.org> Cr-Commit-Position: refs/heads/master@{#797682}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/dbee93ac203d..e1360ddcec9e If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-linux-chromium Please CC perfetto-bugs@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/+doc/master/autoroll/README.md Tbr: perfetto-bugs@google.com Change-Id: Icea628be2aaf0dde7aa59e8b1c02857332db5b9b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354236Reviewed-by:
-
Nohemi Fernandez authored
This method is no longer used, clean up sign-in utilities. Bug: 1103274 Change-Id: I2b5a68c869d723e2216ab41fdf984948ce5b1eb5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352804 Auto-Submit: Nohemi Fernandez <fernandex@chromium.org> Commit-Queue: Eugene But <eugenebut@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/fec8e60ea3e4..df9ed89229db 2020-08-13 johnstiles@google.com Fix logic error in GrProcessorSet::dumpProcessors. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC fmalita@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Cq-Do-Not-Cancel-Tryjobs: true Bug: None Tbr: fmalita@google.com Change-Id: Ia8f7136457cc9d0efdb2d4416187876a929db6f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354215Reviewed-by:
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/e1360ddcec9e..b19e07ebf92c 2020-08-13 taylori@google.com Merge "Add WebUSB error" 2020-08-13 fmayer@google.com Move PackageFromLocation to freestanding function. 2020-08-13 fmayer@google.com Add messaging to APK list. 2020-08-13 fmayer@google.com Merge "Introduce GlobalStackProfileTracker." If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Please CC perfetto-bugs@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:linux-perfetto-rel Bug: chromium:159987908 Tbr: perfetto-bugs@google.com Change-Id: Id505925a99ede35650e0f91b8b05876ecaf04beb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354214Reviewed-by:
-
Yann Dago authored
Bug: 1115696 Change-Id: I75b402d78827a415243c3c11946f1ca17baf7605 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353362Reviewed-by:
Owen Min <zmin@chromium.org> Commit-Queue: Yann Dago <ydago@chromium.org> Cr-Commit-Position: refs/heads/master@{#797677}
-
Stephen Sigwart authored
Some web pages will have a login page that adds an MFA input after the initial username and password submission. When doing so, they set the submitted POST values as the username and password values. If autofill had a different password, but same username, it would overwrite the password field. This causes the password to be invalid when submitted with the MFA unless the user manually enters the original password again. Bug: 1101599 Change-Id: I316283ed09b7f7a9cb754a5246aff8a322ebbe65 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2280603 Commit-Queue: Stephen Sigwart <ssigwart@gmail.com> Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Cr-Commit-Position: refs/heads/master@{#797676}
-
Monica Basta authored
This CL adds support for device policies and adjusts UI accordingly. Bug: 1063856 Change-Id: Ibccfc34f6fdf588f704e8a7fe8c5818dfb2c0f25 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352190 Commit-Queue: Monica Basta <msalama@chromium.org> Reviewed-by:
David Roger <droger@chromium.org> Cr-Commit-Position: refs/heads/master@{#797675}
-
Varun Khaneja authored
When a user who can turn on Enhanced Protection runs Safety Check, they'll be informed that Enhanced Protection is available to them. Before: http://screen/NL1GrepiSiq After : http://screen/YkD3EQy7OS8 Fixed: 1103016 Change-Id: I364b9c47e79c1a4f7f501078f9dd670166fdc371 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2343569 Commit-Queue: Andrey Zaytsev <andzaytsev@google.com> Reviewed-by:
Andrey Zaytsev <andzaytsev@google.com> Reviewed-by:
Tommy Li <tommycli@chromium.org> Auto-Submit: Varun Khaneja <vakh@chromium.org> Cr-Commit-Position: refs/heads/master@{#797674}
-
Richard Knoll authored
This makes the conversions from Mojo Metadata Types available to be used by the NearbySharingService to avoid code duplication. Bug: 1085067 Change-Id: I42457e358fff3b02f7045d2788544c8bb636e066 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2349628Reviewed-by:
Himanshu Jaju <himanshujaju@chromium.org> Commit-Queue: Richard Knoll <knollr@chromium.org> Cr-Commit-Position: refs/heads/master@{#797673}
-
Chris Lu authored
Bug: 1071914 Change-Id: I27d71af8635d3c232a4f1562a7da5c61431efee2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2324884Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Reviewed-by:
-
