- 11 Sep, 2020 40 commits
-
-
George Steel authored
Remove CompositedLayerMapping::ComputeTransformOrigin (dead) Remove CompositedLayerMapping::UpdateTransform (orphan declaration) Current version is in FragmentPaintPropertyTreeBuilder::UpdateTransform() Change-Id: Ia0236bb1114c210b8458c1be3a0abb8f5b4fac97 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404155Reviewed-by:
Robert Flack <flackr@chromium.org> Commit-Queue: George Steel <gtsteel@chromium.org> Cr-Commit-Position: refs/heads/master@{#806194}
-
Per Åhgren authored
On ARM devices, WebRTC always performs the audio processing at a maximum of 32 kHz. The reason for this is that previously the 48 kHz splitting filters used caused issues related to CPU-performance on ARM. This has now been addressed and this CL activates 48 kHz processing at 32 kHz. The CL also adds a kill-switch that can be used to turn off this support for ARM devices, in case it would turn out to be an issue. Bug: webrtc:6181 Change-Id: I3c31d6d1724a784e56391def673a3d7140ece457 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404921 Commit-Queue: Olga Sharonova <olka@chromium.org> Reviewed-by:
Olga Sharonova <olka@chromium.org> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#806193}
-
Guillaume Jenkins authored
Adds support for the simple policy MetricsReportingEnabled. Change-Id: Id9959f8c8ffae88483ae39a2d93cc9d11e0f47ab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404480Reviewed-by:
Owen Min <zmin@chromium.org> Reviewed-by:
sebsg <sebsg@chromium.org> Commit-Queue: Guillaume Jenkins <gujen@google.com> Cr-Commit-Position: refs/heads/master@{#806192}
-
Gang Wu authored
When we call AppTask#getTaskInfo may get IllegalArgumentException, we can use AndroidTaskUtils#getTaskInfoFromTask to handle it. Bug: 1126525 Change-Id: I5bf9b2cf02b6c3afc3854a8e249c30ba8c6f3928 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2405745Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Gang Wu <gangwu@chromium.org> Cr-Commit-Position: refs/heads/master@{#806191}
-
Gang Wu authored
Bug: 1127147 Change-Id: I97814249051ca11d29f3f02cea44558be2b522fd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404112Reviewed-by:
-
Daniel Classon authored
Adds deep links to the About Page and Detailed Build Info subpage. Bug: 1084154 Change-Id: I5ac564c18c2cdc21facaa21803f4169a99fcd2f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2402281 Commit-Queue: Daniel Classon <dclasson@google.com> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#806189}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/bbe69951b416..6518d77a2200 2020-09-11 brianosman@google.com Disambiguate '.' from '::' in the SkSL parser 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 reed@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: reed@google.com Change-Id: I89b903d2c6aa51d32abd1b01057c36ad276dc708 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406105Reviewed-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@{#806188}
-
Internal Frameworks Autoroller authored
TBR=bling-team@google.com Change-Id: Ic11013f4b2532d003977d43d833197741b4095e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2405568Reviewed-by:
Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#806187}
-
Chromium WPT Sync authored
Using wpt-import in Chromium 5f919066. With Chromium commits locally applied on WPT: d3d1f16b "Visited background-color alpha channel in Forced Colors Mode" Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md NOAUTOREVERT=true TBR=smcgruer@google.com No-Export: true Change-Id: Ia3381ef720db3e6e4915b9bfc709cb0b2086eddf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404625Reviewed-by:
WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#806186}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1599803297-f57c520d1d1c3cda3710a7861122a030eca358e8.profdata to chrome-mac-master-1599825590-2ec297440160ee45d77cb43d7acba877f19de7a0.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-mac-chromium Please CC sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@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:mac-chrome Tbr: sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@google.com Change-Id: I986f1d5bffc6f7e8aed6dbb381b8e0b3606b7b3e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406106Reviewed-by:
-
Brian Salomon authored
This is a more structured way of specifying planar configurations that makes it easier to add new configurations (i.e. alpha planes) and will allow Skia to improve rendering quality by having a more precise specification of the YUVA planar structure (e.g. correct handling odd-dimensioned images with chroma subsampling and eventually accounting for different sitings). QueryYUVA now is told whether 16bit (either unorm or float) is supported by the GPU decode cache based on texture format support. Bug: skia:10632 Change-Id: Ibb240358a43a7f742d5ed7a5618b64a53fa4efc2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2365353Reviewed-by:
Khushal <khushalsagar@chromium.org> Reviewed-by:
Leon Scroggins <scroggo@google.com> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Brian Salomon <bsalomon@google.com> Cr-Commit-Position: refs/heads/master@{#806184}
-
Denis Kuznetsov authored
oobe-dialog have switched to cr-lazy implementation. Instantiation of cr-lazy template and focusing button happens in same JS event, and it seems to work incorrectly with a11y tree (at time of focus() the button is not considered a part of the tree). Fix that by postponing focus() call to the next render event. Bug: 1024092 Change-Id: I435aa720c0eac176789ff82650a27ead2b7c45c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401458Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Commit-Queue: Denis Kuznetsov [CET] <antrim@chromium.org> Cr-Commit-Position: refs/heads/master@{#806183}
-
Yifan Luo authored
Bug: 1116418 Change-Id: I770f1032deb1558203fee33528ec08ae475e3c00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2396217 Commit-Queue: Yifan Luo <lyf@chromium.org> Reviewed-by:
Daniel Vogelheim <vogelheim@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#806182}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/3103138c4fb2..bdf5ca45928c 2020-09-11 tvanderlippe@chromium.org Load accessibility_test_runner as module 2020-09-11 szuend@chromium.org [ts] Remove unnecessary @ts-nocheck from FilePathScoreFunction.js 2020-09-11 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS. 2020-09-11 tvanderlippe@chromium.org [globals] self.Runtime.cachedResources 2020-09-11 patrick.brosset@microsoft.com Grid: Give the grid overlay more contrast 2020-09-11 szuend@chromium.org [ts] Type-check sources/DebuggerPausedMessage.js with TypeScript 2020-09-11 szuend@chromium.org [ts] Type-check sources/SimpleHistoryManager.js with TypeScript 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:1047356,chromium:1058320,chromium:1105476 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I83e3d7e8c83f286ccb60d78168155eeb3ddcd331 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406101Reviewed-by:
-
Ilya Nikolaevskiy authored
This forward webrtc SinkWants signal to the capturers. Currently only tab capturer respects these signals and it's done on a best-effort basis. Therefore, adaptation code is going to stay in case of capturer not supporting the signal in current conditions. Bug: chromium:1116430 Change-Id: I70da52786241564c2cd2c668ac882651789d367d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2386743 Commit-Queue: Ilya Nikolaevskiy <ilnik@chromium.org> Auto-Submit: Ilya Nikolaevskiy <ilnik@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/f5c373b5fb1d..3dc4780d8e58 2020-09-11 philipel@webrtc.org Added VideoContentType to OnDecodedFrame callback. 2020-09-11 nisse@webrtc.org Make NetEqController::TargetLevelMs const, part 2 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@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 Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I3b1864ddd40036ea09e641c1961e6eef1e2ac5f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406144Reviewed-by:
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/5dc147f282ab..9edd1a906f57 2020-09-11 fmayer@google.com Remove outdated comment. 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: None Tbr: perfetto-bugs@google.com Change-Id: Id444026862eb43b0cfd09b26f6ee5d37ac9f2c2c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406100Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/d9ddf43a38c7..0112b94ac90e 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 orphis@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: orphis@google.com Change-Id: I62f197e6d5c64a57903baca3fb8166edfcf214e4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406140Reviewed-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@{#806177}
-
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 cr-fuchsia+bot@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 Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast Tbr: cr-fuchsia+bot@chromium.org Change-Id: I0ce3d9636c24b700d61bc1f0f9ef32872356b9aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406119Reviewed-by:
-
Torne (Richard Coles) authored
The HTTP cache in WebView is limited to 20MB but the generated code caches were being left at the default size automatically calculated based on disk space, which is typically much larger. Since the source file needs to be present in the HTTP cache for code cache entries to be used, it's not useful for the code cache to be so big. Set the code cache size to 10MB; there are two code caches, so this will result in a ~40MB cache dir in total; 2x as much as before the code cache was implemented. This avoids apps complaining that WebView is using hundreds of megabytes of space in their cache dir (causing users to complain about the amount of space the app is using). Bug: 1126485 Change-Id: I44666c0ff745b5f4c43f5776c6177368ee4a6e48 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404565Reviewed-by:
Mythri Alle <mythria@chromium.org> Reviewed-by:
Anna Malova <amalova@chromium.org> Commit-Queue: Richard Coles <torne@chromium.org> Cr-Commit-Position: refs/heads/master@{#806175}
-
Roman Sorokin authored
Bug: 1108996, 1032194 Change-Id: Ib92003f7ed789e858831b518e54a36629940e2fe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406212 Auto-Submit: Roman Sorokin [CET] <rsorokin@chromium.org> Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Commit-Queue: Roman Sorokin [CET] <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#806174}
-
Jonathan Backer authored
Blocklist was based on information from: https://en.wikipedia.org/wiki/Mali_(GPU) https://en.wikipedia.org/wiki/Adreno and UMA statistics. Bug: 1126922 Change-Id: I6504933eb1f4461ecf9ca8fbf59aa59b0ddd225a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2403626Reviewed-by:
Jonathan Backer <backer@chromium.org> Reviewed-by:
Vasiliy Telezhnikov <vasilyt@chromium.org> Commit-Queue: Jonathan Backer <backer@chromium.org> Cr-Commit-Position: refs/heads/master@{#806173}
-
Johann authored
Most of the files served by run_blink_httpd.py are from the git checkout. A few are not, so make sure developers know they can specify the checkout directory with -t. Change-Id: If66ebce1db41e05e46e792e310838ee0ed2741ab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2405715 Auto-Submit: Johann Koenig <johannkoenig@google.com> Reviewed-by:
Robert Ma <robertma@chromium.org> Commit-Queue: Robert Ma <robertma@chromium.org> Cr-Commit-Position: refs/heads/master@{#806172}
-
chromium-autoroll authored
Roll Chrome Linux PGO profile from chrome-linux-master-1599803297-c5d0441082dd5a8fa2a2c84cdf40fe1c77138c5e.profdata to chrome-linux-master-1599825590-2ad7f8d1aefd3309725ac2db96fd5021cdb15d15.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-linux-chromium Please CC sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@google.com,chrome-brapp-engprod@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-chrome Tbr: sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@google.com,chrome-brapp-engprod@google.com Change-Id: I7598c3fe5d4aada07fc44ca200a2c2fba8ce567f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406102Reviewed-by:
-
Quinten Yearsley authored
Change-Id: Ic2cc5ead2956718281e45d5adf8ce2a29e47dc4b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401815 Auto-Submit: Quinten Yearsley <qyearsley@chromium.org> Commit-Queue: Robert Ma <robertma@chromium.org> Reviewed-by:
-
Jan Wilken Dörrie authored
This change removes the kCredUIPromptForWindowsCredentialsFeature flag, which made it possible to fallback to the legacy authentication logic. Using the new logic making use of CredUIPromptForWindowsCredentials is confirmed to work correctly, which is why this removal is safe. Bug: 574581, 1126051 Change-Id: Iee54bdbe845b7acb3a452309b94fe62aa5f61174 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406213 Auto-Submit: Jan Wilken Dörrie <jdoerrie@chromium.org> Commit-Queue: Vasilii Sukhanov <vasilii@chromium.org> Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Cr-Commit-Position: refs/heads/master@{#806169}
-
Tim van der Lippe authored
They are replaced by DevTools unittests in https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2406154 TBR=aerotwist@chromium.org Change-Id: Iec1e479e8716f3656406efb3c55684cc188a5f4f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404446Reviewed-by:
Tim van der Lippe <tvanderlippe@chromium.org> Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org> Auto-Submit: Tim van der Lippe <tvanderlippe@chromium.org> Cr-Commit-Position: refs/heads/master@{#806168}
-
Emanuel Krivoy authored
At the moment NativeIO can only be used from origins that use HTTPS or are served locally, but all potentially trustworthy origins (especially Chrome extensions) should have access to it. Relying on this centrally managed definition also has the advantage that, as our view of trustworthiness changes, so does NativeIO's behavior. Also add a web platform test that confirms that NativeIO is not accessible from untrustworthy origins. Bug: 914488 Change-Id: I925a4bf39912c9747c006b1f80bc06a8ec606b23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353452 Commit-Queue: Emanuel Krivoy <krivoy@google.com> Reviewed-by:
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/617d3f67c3d9..5dc147f282ab 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: I44214b8a6d190aa5ec50c4b21a4b348ce4ba354d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2405996Reviewed-by:
-
Harald Alvestrand authored
This ensures that candidates generated at callee arrive after making the caller ready to receive them. Bug: chromium:1122106 Change-Id: Iae0643da57029db8df6b98ef417ee2d4136b2daa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404346 Commit-Queue: Harald Alvestrand <hta@chromium.org> Reviewed-by:
Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#806165}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/9a7e7b08a74e..4331ba7ac01d 2020-09-11 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Vulkan-Tools from ccab4cc42372 to d19622688af4 (1 revision) 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 ianelliott@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: ianelliott@google.com Change-Id: Ida51c42eae42a3c94f0add7668d9e769ee30a87d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406139Reviewed-by:
-
Jan Wilken Dörrie authored
This mitigation was added during the launch of Password Sync USS. Since deleting all sync metadata is intrusive and unprecedented, the feature toggle was added as safety mechanism and has always been enabled by default. Looking at UMA, it's safe to drop this feature. It is doing the right thing in the rare occasion of failure in reading sync metadata. Bug: 1126051 Change-Id: I8c19b60d30d1d1389b2ab9078ace3f5b0af078dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404448Reviewed-by:
Mohamed Amir Yosef <mamir@chromium.org> Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org> Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org> Auto-Submit: Jan Wilken Dörrie <jdoerrie@chromium.org> Cr-Commit-Position: refs/heads/master@{#806163}
-
Jordan Oroshiba authored
PermissionInfo.Type contained a subset of ContentSettingTypes. Since both this and the previously existing ContentSettingException.Type needed to be translated to and from ContentSettingType for save, these intermediary types only created more obfuscation of what is happening in the code. Bug: 1103597 Change-Id: Ie8bb7dbf388c48042291e1d2cb403299c35cefad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2340878 Commit-Queue: Jordan Oroshiba <oroshiba@google.com> Reviewed-by:
Finnur Thorarinsson <finnur@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Reviewed-by:
Ehimare Okoyomon <eokoyomon@chromium.org> Reviewed-by:
Christian Dullweber <dullweber@chromium.org> Cr-Commit-Position: refs/heads/master@{#806162}
-
Anthony Cui authored
Consolidate translation check and execution logic between TranslateManager and RenderViewContextMenu Consolidated logic by having RenderViewContextMenu::ExecTranslate call TranslateManager::InitiateManualTranslation, and RenderViewContextMenu::AppendPageItems call TranslateManager:CanManuallyTranslate. Bug: 898168 Change-Id: If91cf98626f73d0c357522f8fdca840695185bc2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2385636Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Megan Jablonski <megjablon@chromium.org> Commit-Queue: Anthony Cui <cuianthony@chromium.org> Cr-Commit-Position: refs/heads/master@{#806161}
-
Adam Langley authored
A GCMDriver is needed in order to register a handler and, by exposing this accessor, users need only get an InstanceIDDriver. Change-Id: I49cc32e6e78a418ca9352745cf07ec4ee2e256aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2405533 Auto-Submit: Adam Langley <agl@chromium.org> Commit-Queue: Peter Beverloo <peter@chromium.org> Reviewed-by:
Peter Beverloo <peter@chromium.org> Cr-Commit-Position: refs/heads/master@{#806160}
-
Maksim Ivanov authored
Fix use-after-move (potential) bugs found by the "bugprone-use-after-move" clang-tidy check. Bug: 1122844 Change-Id: I521dc064f7ae4522b25a3c7c003d608616acba05 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401521 Commit-Queue: Asanka Herath <asanka@chromium.org> Reviewed-by:
Asanka Herath <asanka@chromium.org> Cr-Commit-Position: refs/heads/master@{#806159}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/0b1f73521ce7..3103138c4fb2 2020-09-11 szuend@chromium.org [ts] Type-check sources/Plugin.js with TypeScript 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: I5b1426300df6454d42dfc24de37d79dd3a7b5320 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406138Reviewed-by:
-
Maksim Sisov authored
DisplayRenderer uses DisplayColorSpace to get suitable output buffer format for Reshape(). However, Wayland didn't set that and default value (RBGA_8888) was used instead. This didn't work well as Wayland may have crashed because this specific buffer format wasn't supported. My observation showed that Chromium supports either BGRA_8888 or RGBA_8888 as default buffer formats. Thus, figure out, which of them is supported and use that when creating Display. This fixes a crash that results in the following error - wl_display@1.error(zwp_linux_buffer_params_v1@16, 7, "failed to import supplied dmabufs: Unsupported buffer format 875708993") Bug: 1123382, 1121912 Change-Id: I7b3745726143f9c71db5bc8942be9933e67b7a96 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401041 Commit-Queue: Maksim Sisov (GMT+3) <msisov@igalia.com> Reviewed-by:
Peng Huang <penghuang@chromium.org> Cr-Commit-Position: refs/heads/master@{#806157}
-
Mario Sanchez Prada authored
These two methods are the only ones, among those that implement the mojom::FrameHost interface in RenderFrameHostImpl, that are kept in the public section of RFHI instead of being private, as it's the case for the other methods of mojom::FrameHost. Doing some quick investigation, I found out that the only places where these methods are directly accessed from outside of RFHI are related to tests (i.e. either tests or test-focused helpers), so it seems like it would make sense to move these 2 methods, along with the other ones, to the private section and adapt those tests and test-related helpers that need access to them. This CL does that, hopefully making it clearer in the future that the implementation of mojom::FrameHost should be private to RFHI. Bug: 1093920, 1102421 Change-Id: I5bf23c59082eb982d152083f96d264522cc58a4a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2403261Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Commit-Queue: Mario Sanchez Prada <mario@igalia.com> Cr-Commit-Position: refs/heads/master@{#806156}
-
Richard Knoll authored
Synchronizing displayed notifications helps to clean up already closed notifications from the NotificationDatabase. This implements this functionality for ChromeOS via the MessageCenter. Bug: None Change-Id: I660f2263451ca734887da63f0c7ab43cd12ab2b5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391087 Commit-Queue: Richard Knoll <knollr@chromium.org> Reviewed-by:
-
