- 19 Nov, 2020 40 commits
-
-
Denis Kuznetsov authored
Bug: None Change-Id: Ie4329a1a00ad35316f22340a2ce42832427243c3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2549962 Commit-Queue: Denis Kuznetsov [CET] <antrim@chromium.org> Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#829207}
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC chrome-fuchsia-gardener@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 Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-deterministic-dbg;luci.chromium.try:fuchsia-x64-cast Tbr: chrome-fuchsia-gardener@grotations.appspotmail.com Change-Id: Ieda249b47c753697db3de49d482af1f8ec1d1591 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2549145Reviewed-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@{#829206}
-
Maksim Sisov authored
In the first take, I thought buffer formats could be determined from the browser process side as early as possible, but several problems were identified in the end - 1) glx's bindings' initialization is required. And it's done on the gpu process side 2) gl implementation can be determined after gl is set (it's temporarily required before angle + gmb support is added, though). I also thought to make fetching gmb formats asynchronous, but it would require rewriting some important clients, which is non-trivial, unfortunately. Thus, that approach didn't work well and I had to reuse the existing approach to pass support buffer formats for gmb via gpu extra info. Now, OzonePlatform has fetch_buffer_formats_for_gmb_on_gpu variable that clients can use to determine the way that they are able to fetch supported buffer formats. All the previous logic that non-Ozone/X11 had stayed the same except that it's also used by OzonePlatform that has fetch_buffer_formats_for_gmb_on_gpu set to true. In this case, CollectGpuExtraInfo collects supported buffer formats. Bug: 1099183 Change-Id: I56c1323af54ae5bec4a5f9152aca47a21035d6b8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2540286Reviewed-by:
Jonathan Backer <backer@chromium.org> Reviewed-by:
Robert Kroeger <rjkroege@chromium.org> Commit-Queue: Maksim Sisov (GMT+2) <msisov@igalia.com> Cr-Commit-Position: refs/heads/master@{#829205}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/d40c6d7f3bef..745ab6e3c09a 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 mkwst@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.chrome.try:linux-chromeos-chrome Bug: None Tbr: mkwst@google.com Change-Id: If781c93efa24c71f3be9c1d61845e74e46dc80e0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2549162Reviewed-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@{#829204}
-
Viktor Semeniuk authored
Bug: 1096986 Change-Id: Ic3f4b69c0762afd09386d42a3639a207da24aa9c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2546007Reviewed-by:
Caitlin Fischer <caitlinfischer@google.com> Commit-Queue: Viktor Semeniuk <vsemeniuk@google.com> Cr-Commit-Position: refs/heads/master@{#829203}
-
Danila Kuzmin authored
Screens with loaded webview parts need focus adjustment after returning focus from the system tray. But it breaks logic when tab is returned in reverse order and we need to focus other parts of the screen. This CL fixes such tab transitions. Bug: 1133249 Change-Id: I6b565411687e654547935e425272e8f14f1ebaa6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2532576Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Commit-Queue: Danila Kuzmin <dkuzmin@google.com> Cr-Commit-Position: refs/heads/master@{#829202}
-
Greg Thompson authored
They indicate that the initial trivial move succeeds ~2/3 of the time, and that the fallback then moves its contents nearly every time. BUG=1149458 R=ydago@chromium.org Change-Id: Ib107b8c7d59d595c3f22aed697c1a22ded9ba9bc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2544123 Commit-Queue: Greg Thompson <grt@chromium.org> Commit-Queue: Ilya Sherman <isherman@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Yann Dago <ydago@chromium.org> Auto-Submit: Greg Thompson <grt@chromium.org> Cr-Commit-Position: refs/heads/master@{#829201}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/145e22d4d49f..876a780b5210 2020-11-19 tsepez@chromium.org Save some zero bytes in struct XFA_FMHtmlReserveCode 2020-11-18 tsepez@chromium.org Better bounds-checking in CFDE_TextOut::ReloadLinePiece(). If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pdfium-autoroll Please CC pdfium-deps-rolls@chromium.org 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:1147125 Tbr: pdfium-deps-rolls@chromium.org Change-Id: I27748bf37a68aaf8ff7e81836819b12982ab6091 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2549825Reviewed-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@{#829200}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/1f8ea587c2e2..1a5d5109644a 2020-11-19 aerotwist@chromium.org Tweak metrics pane styles 2020-11-19 aerotwist@chromium.org TypeScriptify focus-changed.js 2020-11-19 wolfi@chromium.org [TS] Port HeapProfilePanel.js to TypeScript 2020-11-19 alexrudenko@chromium.org Enable TypeScript for TopDownProfileDataGridNode 2020-11-19 mathias@chromium.org TypeScriptify profiler/HeapProfileView.js, part 1 2020-11-19 szuend@chromium.org TypeScript-ify ui/SearchableView.js 2020-11-19 szuend@chromium.org TypeScript-ify ui/InspectorView.js 2020-11-19 jacktfranklin@chromium.org [DataGrid]: enforce cell values are primitive 2020-11-19 petermarshall@chromium.org [typescript] TypeScript-ify profiler/CPUProfileFlameChart.js 1/N 2020-11-19 aerotwist@chromium.org TypeScriptify TimelineFlameChartView.js 2020-11-19 kimanh@chromium.org [ts] Typescript-ify TracingLayerTree.js 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,chromium:1125968 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I2b16db37b0e239942722885932bf5a956980d759 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2549829Reviewed-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@{#829199}
-
Elad Alon authored
Change-Id: Ifa001fff187c3f1ec7348693e5ba32fb6eb64dcb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2549081Reviewed-by:
Ian Clelland <iclelland@chromium.org> Commit-Queue: Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#829198}
-
Owen Min authored
With partial reporting also using this field, the old name becomes misleading. Renaming it to is_available. This matches server side renaming: 343096864 Bug: 1137964 Change-Id: Icf606a22c9b8efaa7c962b5d49b54e52432bb204 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2547571 Auto-Submit: Owen Min <zmin@chromium.org> Commit-Queue: Julian Pastarmov <pastarmovj@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Cr-Commit-Position: refs/heads/master@{#829197}
-
chromium-autoroll authored
Roll Chrome Win32 PGO profile from chrome-win32-master-1605732977-09df8fbd862d08eaa283942ed13244c34d12f091.profdata to chrome-win32-master-1605754194-4e76916f5340c97913d651fe425b3570e2df369d.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win32-chromium Please CC pgo-profile-sheriffs@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.chrome.try:win-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I425688f81a27c983a00ef988e85f0026b223aa97 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2549183Reviewed-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@{#829196}
-
Rushan Suleymanov authored
Bug: None Change-Id: Ie7b1a0a016d1b63a71ca313f6e7054246e056c15 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2547022 Commit-Queue: Rushan Suleymanov <rushans@google.com> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#829195}
-
Monica Basta authored
This CL adds the generic colored avatar to the avatar icons shown on 'chrome://settings/manageProfile' that is only shown for local profile (No GAIA account). It also fixes the bug where no selected is shown when the user is using the GAIA avatar as the chrome avatar. In a future CL, |kProfileUsingDefaultAvatar, kProfileUsingGAIAAvatar| prefs will be deleted. The |ManageProfileHandler| should not rely on these prefs. Fixed: 1149539 Change-Id: I9cbce03e62efb20a6c466eac9c7e32d1cbc93f18 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2542062 Commit-Queue: Monica Basta <msalama@chromium.org> Reviewed-by:
David Roger <droger@chromium.org> Reviewed-by:
Esmael Elmoslimany <aee@chromium.org> Cr-Commit-Position: refs/heads/master@{#829194}
-
Findit authored
This reverts commit e13a069e. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 829053 as the culprit for flakes in the build cycles as shown on: https://analysis.chromium.org/p/chromium/flake-portal/analysis/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyQwsSDEZsYWtlQ3VscHJpdCIxY2hyb21pdW0vZTEzYTA2OWUyZmNmZmU3OWM4MmRlNTAzMmEwMzVhMDRjNDIwMmZkMgw Sample Failed Build: https://ci.chromium.org/b/8863210065181297712 Sample Failed Step: services_unittests on (none) GPU on Mac on Mac-10.13.6 Sample Flaky Test: CoreLocationProviderTest.ShouldUseCallbackTest Original change's description: > fallback to Network Provider if wifi is turned off > > If Wifi is disabled Core Location does not work. In this case we will > fallback to the Network Location Provider which can use the IP address > to get an much less precise location. > > Bug: 1135766 > Change-Id: I3f5fa8e78fbb34bcec36dbd6eeb0e6adc06c64c6 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2453437 > Reviewed-by: Reilly Grant <reillyg@chromium.org> > Commit-Queue: James Hollyer <jameshollyer@chromium.org> > Cr-Commit-Position: refs/heads/master@{#829053} Change-Id: Iecd1cf5b4e3a36fdac2b11d5c52754fab8772c31 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1135766 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2549832 Cr-Commit-Position: refs/heads/master@{#829193}
-
Swapnil authored
There are many browsertest related to search related polices such as DefaultSearchProvider related policy and ForceGoogleSafeSearch policy. This CL splits them to new files. Bug: 1148743 Change-Id: Iba18f2e1ce08fbded6b112ee07d683405ca0a653 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2545522 Commit-Queue: Swapnil Gupta <swapnilgupta@google.com> Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#829192}
-
Greg Thompson authored
The histogram had the wrong type, making its interpretation non-obvious. BUG=1149463 R=ydago@chromium.org Change-Id: I394db672d96da3c9f32e4434ae7b57016aabe5c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2543385 Commit-Queue: Greg Thompson <grt@chromium.org> Reviewed-by:
Weilun Shi <sweilun@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Yann Dago <ydago@chromium.org> Auto-Submit: Greg Thompson <grt@chromium.org> Cr-Commit-Position: refs/heads/master@{#829191}
-
Shik Chen authored
The i18n json files are now generated in subdirectories for platform app and SWA. Bug: b/172879638 Test: cca deploy Change-Id: I404b42b2afdca4eb4a628bb49c44365dc7b21741 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2549381 Auto-Submit: Shik Chen <shik@chromium.org> Reviewed-by:
Wei Lee <wtlee@chromium.org> Commit-Queue: Wei Lee <wtlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#829190}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/8d63a7fc4924..c151f873e4ab 2020-11-19 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Chromium from 45b78e7b to 62214500 (493 revisions) 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 cnorthrop@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_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;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: cnorthrop@google.com Change-Id: I6c359a9e7e44367f40aa521f8fa2f52442482aae Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2549282Reviewed-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@{#829189}
-
Benoit Lize authored
Always enable thread cache statistics. Bug: 998048 Change-Id: I6cc5ac2e248baf19582c7170537a94e6292daf5f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2544570Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Yuki Shiino <yukishiino@chromium.org> Commit-Queue: Benoit L <lizeb@chromium.org> Cr-Commit-Position: refs/heads/master@{#829188}
-
Roman Sorokin authored
During Kiosk app launch we might need to configure network. This is guarded by the owner authentication (in case of consumer kiosk). Before this CL it used WebUI AccountPicker screen. This CL moves it to the current User pod screen implementation Bug: 1071779 Change-Id: Iaa1665e8d588d4df0beb5459365159a8292c08f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2540983 Commit-Queue: Roman Sorokin [CET] <rsorokin@chromium.org> Commit-Queue: Denis Kuznetsov [CET] <antrim@chromium.org> Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Cr-Commit-Position: refs/heads/master@{#829187}
-
Maria Kazinova authored
This is needed to properly record PasswordManager.SuccessfulSubmissionIndicatorEvent metric for this type of submission. Bug: 1146373, 1150780 Change-Id: I426746ed0fabadf553cc04cf7143b0c370015ead Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2541764 Commit-Queue: Maria Kazinova <kazinova@google.com> Reviewed-by:
Christos Froussios <cfroussios@chromium.org> Reviewed-by:
Alex Gough <ajgo@chromium.org> Reviewed-by:
Jan Wilken Dörrie <jdoerrie@chromium.org> Cr-Commit-Position: refs/heads/master@{#829186}
-
Bret Sepulveda authored
As a prerequisite to landing cr/339683181. Bug: 1134294 Change-Id: I95a0774957c5ba1cae28faad5916865f50e5a8d7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2510054 Commit-Queue: Bret Sepulveda <bsep@chromium.org> Reviewed-by:
Brian White <bcwhite@chromium.org> Cr-Commit-Position: refs/heads/master@{#829185}
-
arthursonzogni authored
It was previous reset once per navigations, including the same-document ones. This moves it toward DidCommitNewDocument(); Bug: 1113294 Change-Id: I7a947d9b693fd1380da54996e60431642f4cdde1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2538212 Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#829184}
-
chrome://flags#disable-idle-sockets-close-on-memory-pressurePavol Marko authored
This adds a chromeos-specific flag for the feature added in CL:TODO. When the feature is enabled, idle connections will not be closed on memory pressure. Bug: 1150526 Change-Id: If9d2063c30c7ede5039941f1764e5b769a0facab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2547295 Commit-Queue: Pavol Marko <pmarko@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#829183}
-
Roman Sorokin authored
Fixed: 1116058 Change-Id: Icb6ccd0f0f781efeee01473bcfd1e8a56784d2c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2544662 Commit-Queue: Roman Sorokin [CET] <rsorokin@chromium.org> Auto-Submit: Roman Sorokin [CET] <rsorokin@chromium.org> Reviewed-by:
Anatoliy Potapchuk <apotapchuk@chromium.org> Cr-Commit-Position: refs/heads/master@{#829182}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/a3d1e7c68c67..1f8ea587c2e2 2020-11-19 alexrudenko@chromium.org Enable TypeScript for TimelineController.js 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: I1275d8b150f92c123330f89c9d715b665087a81a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2549802Reviewed-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@{#829181}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/ce207be41fd6..dad44f4d824e 2020-11-19 jiawei.shao@intel.com Skip SwapchainTests/SwitchPresentMode on Linux Intel Vulkan drivers If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/dawn-chromium-autoroll Please CC kainino@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:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel Bug: None Tbr: kainino@google.com Change-Id: I41b746695da2ffd1ff96cc8fc616665f6e9003d6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2549801Reviewed-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@{#829180}
-
Mirko Bonadei authored
https://chromium.googlesource.com/chromium/deps/libsrtp.git/+log/6907d995c797..7990ca64c616 $ git log 6907d995c..7990ca64c --date=short --no-merges --format='%ad %ae %s' 2020-11-19 mbonadei Roll libsrtp to 94ac00d5ac..860492290f. Created with: roll-dep src/third_party/libsrtp Bug: None Change-Id: I00c808561eb6f37feef0beaf358300a29890a85e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2549602Reviewed-by:
Danil Chapovalov <danilchap@chromium.org> Commit-Queue: Mirko Bonadei <mbonadei@chromium.org> Cr-Commit-Position: refs/heads/master@{#829179}
-
Shik Chen authored
The binding generation process was changed a bit in https://crrev.com/c/2451589. Bug: b/172879638 Test: cca deploy Change-Id: Ife59e5064bb4ee9226043e4783d5ee71328a00a4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2548593Reviewed-by:
Wei Lee <wtlee@chromium.org> Commit-Queue: Wei Lee <wtlee@chromium.org> Auto-Submit: Shik Chen <shik@chromium.org> Cr-Commit-Position: refs/heads/master@{#829178}
-
Rohit Agarwal authored
Incognito CCT is currently restricted to be used only from 1P context. However, this also restricts the use for testers to test Incognito CCT via a 3P app. This CL uses feature flag kCCTIncognitoAvailableToThirdParty to allow 3P apps to be able to open Incognito CCT. The flag is disabled by default. Bug: 1150360 Change-Id: I2b9d3e51f90eda8e5cd86dac3317e746e1d8d91f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2544974Reviewed-by:
Peter Conn <peconn@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Rohit Agarwal <roagarwal@chromium.org> Cr-Commit-Position: refs/heads/master@{#829177}
-
Nicholas Verne authored
In most cases we remove the (Beta). Otherwise we replace with "Linux development environment". Bug: 1140370 Change-Id: I156ca81b989d3f50f8119f62c8f4a89c6362a383 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2508102 Commit-Queue: Nicholas Verne <nverne@chromium.org> Reviewed-by:
David Munro <davidmunro@google.com> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Auto-Submit: Nicholas Verne <nverne@chromium.org> Cr-Commit-Position: refs/heads/master@{#829176}
-
Przemek Pietrzkiewicz authored
This patch: - fixes a comment which I think meant kCloneAll where it says kEmpty - makes the single arg constructor explicit Bug: None Change-Id: Id0fb554a3caf06cb2d655fb06a8307cfedc2595a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2547302Reviewed-by:
Wez <wez@chromium.org> Commit-Queue: Przemek Pietrzkiewicz <ppi@chromium.org> Cr-Commit-Position: refs/heads/master@{#829175}
-
Ryo Hashimoto authored
BUG=b:171408795 TEST=Launch Play Store Change-Id: I9bff72a850d74bfb226f14ca3a90afca325ad29e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2540047 Commit-Queue: Ryo Hashimoto <hashimoto@chromium.org> Reviewed-by:
Yusuke Sato <yusukes@chromium.org> Cr-Commit-Position: refs/heads/master@{#829174}
-
Jaeyong Bae authored
This patch changes the code to return empty string for CSSStyleDeclaration.cssText. Discussion at: https://github.com/w3c/csswg-drafts/issues/1033 Makes tests pass: external/wpt/css/cssom/cssstyledeclaration-csstext.html Bug: 1146888 Change-Id: Ibca415b7606d2cc5110ca633c87a77fac3e74ca8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2546305Reviewed-by:
Koji Ishii <kojii@chromium.org> Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Commit-Queue: Jaeyong Bae <jdragon.bae@gmail.com> Cr-Commit-Position: refs/heads/master@{#829173}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/3a578ae35233..16973d613fed 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: I49d18b5d093ddbae00b8f0c2c19b3b9db2d8bd45 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2549841Reviewed-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@{#829172}
-
Joe DeBlasio authored
This CL updates the field trial testing config to match the final stage of the MIX-DL rollout on both android and desktop platforms. Strictly speaking, we'll briefly hit a slightly different configuration in Android first, but this is the configuration that is higher risk, the equivalent config has been tested on Desktop, and the configurations don't change the code paths exercised by the field trial testing anyway. Bug: 960819 Change-Id: I251ba5c20a30ab6532d48a22e8e6ed8eb0fee1d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2548310 Auto-Submit: Joe DeBlasio <jdeblasio@chromium.org> Commit-Queue: Ilya Sherman <isherman@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#829171}
-
Moe Ahmadi authored
Canary experiment: cl/339288320 Beta experiment: cl/342939379 Bug: 1136654, 1136649 Change-Id: I447848638b80bf645de919b62ac14a5d499a55c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2547920 Auto-Submit: Moe Ahmadi <mahmadi@chromium.org> Commit-Queue: Ilya Sherman <isherman@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#829170}
-
Rohit Agarwal authored
This CL removes the deprecated method and update the call site to use the overload WebContentsFactory#createWebContents on profile instead. Bug: 1149861 Change-Id: Id5ed7b30646bbd520127280daeae342eb02eff42 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2543351 Commit-Queue: Rohit Agarwal <roagarwal@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Reviewed-by:
David Trainor <dtrainor@chromium.org> Cr-Commit-Position: refs/heads/master@{#829169}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/1f2fcddd3963..671914c28e82 2020-11-18 greg@lunarg.com Fix buffer oob instrumentation for matrix refs (#4025) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/spirv-tools-chromium-autoroll Please CC radial-bots+chrome-roll@google.com,cnorthrop@google.com,kainino@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_angle_vk32_deqp_rel_ng;luci.chromium.try:android_angle_vk32_rel_ng;luci.chromium.try:android_angle_vk64_deqp_rel_ng;luci.chromium.try:android_angle_vk64_rel_ng;luci.chromium.try:linux_angle_deqp_rel_ng;luci.chromium.try:linux-angle-rel;luci.chromium.try:win-angle-rel-32;luci.chromium.try:win-angle-rel-64;luci.chromium.try:win-angle-deqp-rel-32;luci.chromium.try:win-angle-deqp-rel-64 Tbr: radial-bots+chrome-roll@google.com,cnorthrop@google.com,kainino@google.com Change-Id: I4c7e2d7d054f22e1395a3e4052f3a059d3000478 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2549461Reviewed-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@{#829168}
-