- 09 Dec, 2020 40 commits
-
-
Jan Wilken Dörrie authored
This change moves base::Contains into a new base/containers/contains.h header. This organizes base/stl_util.h a bit, which has become somewhat of a dumping ground. Bug: 970209 Change-Id: I7f0df1a1cbfb323f060f2b7a67bcf9c139aa589e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2578941Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org> Cr-Commit-Position: refs/heads/master@{#835094}
-
Thomas Guilbert authored
This CL updates LocalFileSystemOperation to use OnceClosures instead of closures. Bug: 1152272 Change-Id: I5aef5b841cdc9f0553aa06a53329d1f7be4c0d80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576692 Commit-Queue: Thomas Guilbert <tguilbert@chromium.org> Auto-Submit: Thomas Guilbert <tguilbert@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#835093}
-
Makoto Shimazu authored
This is a clean up task after ServiceWorkerOnUI. EmbeddedWorkerInstance::CreateFactoryBundles() now returns the parameters without callbacks. Bug: 1138155 Change-Id: Ifc896fb6c1c3e8d897f7d9ca1abed6fa5ddd9c41 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576962 Commit-Queue: Makoto Shimazu <shimazu@chromium.org> Reviewed-by:
Asami Doi <asamidoi@chromium.org> Cr-Commit-Position: refs/heads/master@{#835092}
-
Alan Cutter authored
This CL adds a UI tweak to web app windows where instead of flashing the origin we flash the app name in the title bar on launch. Before: https://bugs.chromium.org/p/chromium/issues/attachment?aid=480010&signed_aid=kCtHgWsEYOU09MTBmCOz_w==&inline=1 After: https://bugs.chromium.org/p/chromium/issues/attachment?aid=480009&signed_aid=MXfRHF_FvvLj76okiIayNg==&inline=1 Bug: 1156934 Change-Id: Ie5a32a5cf7acae69085378eb63ed5183b7c3f0f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2581162 Commit-Queue: Alan Cutter <alancutter@chromium.org> Reviewed-by:
Eric Willigers <ericwilligers@chromium.org> Cr-Commit-Position: refs/heads/master@{#835091}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/bb1cad334635..2979a9c445f4 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 shend@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: shend@google.com Change-Id: I165b2d25196d944dca0d4cb6be13a63e0a675d4f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2579946Reviewed-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@{#835090}
-
Elly Fong-Jones authored
It is very flaky on arm64. Bug: 1154345 Change-Id: I7305f56291c191fcdcec6c6c89408459d53a13ed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580165 Commit-Queue: Chris Hamilton <chrisha@chromium.org> Reviewed-by:
Chris Hamilton <chrisha@chromium.org> Cr-Commit-Position: refs/heads/master@{#835089}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/fde98cbddd43..5e744acfad58 2020-12-09 skia-autoroll@skia-public.iam.gserviceaccount.com Roll ANGLE from 251ba5cb119f to 27e52ca05dc7 (24 revisions) 2020-12-09 skia-autoroll@skia-public.iam.gserviceaccount.com Roll Dawn from 3668d352bc5f to 30805557e651 (33 revisions) 2020-12-09 reed@google.com Revert "Revert "Use explicit samplingoptions"" 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 jmbetancourt@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: jmbetancourt@google.com Test: Test: Test:Test: Test: Seven Deadly Sins MECTest: Test: angle_perftests --gtest_filter="*whatsapp*" Change-Id: I769234db0e270ce3a241c7d7269c346a6f41afa0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2581073Reviewed-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@{#835088}
-
Darren Shen authored
Both the web and ARC++ IME frameworks support moving the caret after InsertText, but this functionality is not exposed to IMEs. Our new IME needs this feature, so this patch adds an option to move the cursor to TextInputClient. Unfortunately, the web and ARC++ APIs are slightly different: - Web allows the the cursor to be moved anywhere. - ARC++ doesn't allow the cursor to be moved inside the inserted text. Therefore, although both web and ARC++ take in an integer cursor position parameter, they have very different meanings. To avoid confusion, we use an enum to indicate whether the cursor should be before or after the inserted text (since that's the minimal feature that the IME needs). To keep this CL small, we will first introduce the enum with only a single value (move cursor after text). A future CL will add the additional parameter. Bug: 1155331 Change-Id: I5eb9e5c23fef290b9962b1dee327c76343f08f5c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576062Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#835087}
-
Noel Gordon authored
Mojo requests from the SWA WebContents appear on the receiving SWA page handler mojo endpoint for servicing - that servicing will be handled by the SWA UI class or its delegate. Add the SWA UI class to the page handler mojo pipe constructor. Mention it is the owning |this| since the page handler pipe is both created and owned by the SWA UI class. Bug: 1113981 Change-Id: Ic32e748df303cbaf26b82fe15d39c8b02cee92c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580980Reviewed-by:
Alex Danilo <adanilo@chromium.org> Commit-Queue: Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#835086}
-
spdonghao authored
Bug: 1155761 Change-Id: I9c98e3c0066c98e9d9fe7fad43442c0615bda4be Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576112Reviewed-by:
Xi Han <hanxi@chromium.org> Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Commit-Queue: Hao Dong <spdonghao@chromium.org> Cr-Commit-Position: refs/heads/master@{#835085}
-
Darren Shen authored
Most IME tests currently use a class called DummyTextInputClient, which is a mix of a mock and a fake. This makes it quite difficult to use. Following testing best practices, we introduce a proper WIP fake for TextInputClient that complies with the TextInputClient interface. Future CLs will migrate more and more tests to FakeTextInputClient. DummyTextInputClient will eventually be removed. Bug: 1148157 Change-Id: Ib6e356d75d8f316ceff95c55fe905eeb505361a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576061 Auto-Submit: Darren Shen <shend@chromium.org> Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by:
Jing Wang <jiwan@chromium.org> Cr-Commit-Position: refs/heads/master@{#835084}
-
Josiah K authored
AX-Relnotes: N/A. Bug: 1156494 Change-Id: I99fb4980235a9be55b5c5e8674d43f0c1326899a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577734Reviewed-by:
Jimmy Gong <jimmyxgong@chromium.org> Commit-Queue: Jimmy Gong <jimmyxgong@chromium.org> Auto-Submit: Josiah Krutz <josiahk@google.com> Cr-Commit-Position: refs/heads/master@{#835083}
-
Thomas Guilbert authored
This CL converts SyncTaskManager::Task and SyncTaskManager::Continuation to OnceCallbacks. Since some of the closures are stored in a priority queue (which doesn't support move-only types), they are wrapped with base::AdaptCallbackForRepeating. There is also an opportunistic deletion of some dead code, and renaming a test callback to something more useful. Bug: 1152272 Change-Id: I39fd928029e215b118f0c09cbaf84780862197cd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576443 Commit-Queue: Thomas Guilbert <tguilbert@chromium.org> Auto-Submit: Thomas Guilbert <tguilbert@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#835082}
-
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: I197685bc456fad5e6404c8c6758ca57fdc596c9e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2581066Reviewed-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@{#835081}
-
Mason Freed authored
Bug: 966758,937746 Change-Id: I7315e4b9a1a818d470c31000c4b605270e22391c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580432 Auto-Submit: Mason Freed <masonfreed@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#835080}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/42f37e5c..2523885b 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: I50919fae43139f43aaf83ad5dcb7329a86a07f29 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580227Reviewed-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@{#835079}
-
Hui Yingst authored
CodeHealthRotation: Migrate RunScriptExceptionHandler to base::OnceCallback in extensions/renderer/. Bug: 1152265 Change-Id: I90a519bfb5c979f25a405800a5a1b92e12c89d3b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574070 Commit-Queue: Hui Yingst <nigi@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/master@{#835078}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/f691b3b5096a..27e52ca05dc7 2020-12-09 jdarpinian@chromium.org Fix build when angle_has_build == false 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 syoussefi@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: syoussefi@google.com Change-Id: I00b204183f35182d97facf78b379f287c0b40f10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580769Reviewed-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@{#835077}
-
Hui Yingst authored
Bug: 1099020 Change-Id: I1cf7d7f1403bc9639568b451b409660edc9e264d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2560911 Commit-Queue: Hui Yingst <nigi@chromium.org> Reviewed-by:
K. Moon <kmoon@chromium.org> Cr-Commit-Position: refs/heads/master@{#835076}
-
chromium-autoroll authored
https://chromium.googlesource.com/openscreen.git/+log/66f231597428..e28aa0ca9448 2020-12-09 miu@chromium.org Remote virtual connections [3/3]: Connection messages are special-cased. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/openscreen-chromium Please CC jophba@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: None Tbr: jophba@chromium.org Change-Id: Ifceb55805769252691128c8d9a87f404046c14ad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2581071Reviewed-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@{#835075}
-
Mitsuru Oshima authored
---- new in patch sets This is reland of crrev.com/c/2550366. Non ash-chrome platform needs to drive native event loop to receive BeginFrame, therefore doesn't work well with mock time. It needs to run loop using non mock time until the callback is reported. I also fixed the frame generator's timing to 16, which was reverted in another CL. I'll make same change to animation throughput reporter's unit test in a separate CL. ----- new in patch sets: end This class measures the throughput from the time first animation is started on a compositor, to the time last animation ended. This is useful to measure the total animation throughput during a transition that has many animations applied such as login, overview etc. Bug: 1150492 Test: covered by unittest Change-Id: I299f837f5eef435c0e9d59ddfc491e2cab98a6c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574658 Commit-Queue: Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Robert Flack <flackr@chromium.org> Cr-Commit-Position: refs/heads/master@{#835074}
-
Jérémie Boulic authored
Module generation for the following JS files in //ui/file_manager/: - file_manager/common/js/trash.js - file_manager/background/js/file_operation_util.js - file_manager/common/js/file_operation_progress_event.js //u/f/externs/file_operation_progress_event.js moved to //u/f/file_manager/common/js/file_operation_common.js. Converting: - fileOperationUtil.Error => FileOperationError - fileOperationUtil.EventRouter.EventType => FileOperationProgressEvent.EventType This breaks the circular dependency where fileOperationUtil used types from file_operation_progress_event.js, which used types from fileOperationUtil. Bug: 1133186 Change-Id: I8d7270cb037907388086a5b8c0fb2da35b65b070 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576994Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Commit-Queue: Jeremie Boulic <jboulic@chromium.org> Cr-Commit-Position: refs/heads/master@{#835073}
-
Jia authored
Leaving the team, hence remove myself from metrics owners. Change-Id: I28e17e5517441dbd3c0554e517a136d2f91a53b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580978Reviewed-by:
Tony Yeoman <tby@chromium.org> Commit-Queue: Jia Meng <jiameng@chromium.org> Cr-Commit-Position: refs/heads/master@{#835072}
-
Darren Shen authored
There is currently an intermediate KeyboardEvent type that is used to convert between ui::KeyEvent <-> input_ime::KeyboardEvent. However, there's really no need for the intermdiate KeyboardEvent. There are several benefits to removing it: - KeyboardEvent uses strings for key/code, which is less efficient and more error prone than enums and chars. - Generally more efficient to avoid unnecessary intermediate structures. - KeyboardEvent is for extensions, but ARC++ and the "native" IME are not extensions. - KeyboardEvent loses information about dead keys, which is needed by "native" IMEs. Bug: b/174612548 Change-Id: Idb59bc9eabb01680440648d6752984d3c9eb7adf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567089 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by:
Yuichiro Hanada <yhanada@chromium.org> Reviewed-by:
My Nguyen <myy@chromium.org> Reviewed-by:
Keith Lee <keithlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#835071}
-
Ahmed Mehfooz authored
Bug: 1156183 Change-Id: Ia12c20f622ff114e20b7a26124680fe963017fee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577889Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Ahmed Mehfooz <amehfooz@chromium.org> Cr-Commit-Position: refs/heads/master@{#835070}
-
Tetsui Ohkubo authored
In https://crrev.com/c/2011622, it was suggested to use window coordinates for passing gesture exclusion region. This CL moves the scaling logic to exo as suggested. TEST=manual(Use the tester app in the bug. Open the app in tablet mode and confirm that it correctly reacts / rejects back gesture near the border in the middle. Confirmed it works as intended on P and R.) BUG=b:172889170 Change-Id: Ib3c4f94b10d4cdf0d43f83602cdb58c9a7bf69c8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567085 Commit-Queue: Tetsui Ohkubo <tetsui@chromium.org> Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Yuichiro Hanada <yhanada@chromium.org> Cr-Commit-Position: refs/heads/master@{#835069}
-
Luciano Pacheco authored
Visually checked both: --enable-features=AudioPlayerJsModules --disable-features=AudioPlayerJsModules Bug: 1133186, 1151829 Change-Id: I00fe977cd3e7c73e53e2f297bb5c6c84fe85359b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2552330 Commit-Queue: Luciano Pacheco <lucmult@chromium.org> Reviewed-by:
Jeremie Boulic <jboulic@chromium.org> Cr-Commit-Position: refs/heads/master@{#835068}
-
Curt Clemens authored
Add a help caption to the bottom of the nearby settings subpage. Screenshot: https://screenshot.googleplex.com/8mEEaY47XHtMasK.png Bug: 1154743 Change-Id: I4762a00d4d2b30d90e13a71973bf9ed33c5e7d09 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2579728Reviewed-by:
James Vecore <vecore@google.com> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Commit-Queue: Curt Clemens <cclem@google.com> Cr-Commit-Position: refs/heads/master@{#835067}
-
Marco Paniconi authored
https://aomedia.googlesource.com/aom.git/+log/87c414ed32b5..43927e4611e7 $ git log 87c414ed3..43927e461 --date=short --no-merges --format='%ad %ae %s' 2020-12-04 jianj Remove highbd sad from low bitdepth build 2020-12-03 jingning Clean up input args in av1_estimate_txfm_yrd() 2020-12-04 wtc Fix spelling error of "dropped" 2020-11-20 jianj Add documentation about CONFIG_REALTIME_ONLY flag 2020-12-03 jingning Use avg compound SAD and variance functions 2020-12-03 chengchen Use 8x8 block size for screen content in the first pass 2020-11-30 chengchen Allow first pass to encode with other square block sizes 2020-12-03 marpan rtc: Use zeromv mode for speed >= 9 2020-12-03 kmalladi Add av1_calc_indices_dim2_avx2() 2020-12-01 jingning Rework rd cost estimation for mode decisions (...) 2020-11-02 marpan rtc: Allow scene detection for vbr mode 2020-10-26 urvang SUPERRES_AUTO: Allow superres for low qindices too 2020-10-30 urvang SUPERRES_AUTO: don't save/restore cur_frame->buf. 2020-10-30 wtc Add -Wimplicit-function-declaration as C flag only 2020-11-01 jingning Simplify update_mask_best_mv in compound mode search 2020-11-01 jingning Make compound mask return the seg_mask by default 2020-11-01 jingning Remove redundant disable_wedge_search_var_thresh setting 2020-10-30 jianj Disable obmc,restoration,warped/global motion in realtime test. 2020-10-16 deepa.kg Add speed feature to reuse tpl stats 2020-06-11 wtc chroma_check: don't access UV planes if monochrome Created with: roll-dep src/third_party/libaom/source/libaom R=jzern@google.com Change-Id: If5bdb7836e245defa5745c25affd93e91e678024 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580481Reviewed-by:
James Zern <jzern@google.com> Commit-Queue: Marco Paniconi <marpan@google.com> Cr-Commit-Position: refs/heads/master@{#835066}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/26a24ee9aebf..c6b219431a16 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-win-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: Ie02ebe91575adeeaec27eaf391597a6e60e51ee3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580209Reviewed-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@{#835065}
-
shuanghu authored
Bug: b:172063497 Test: components_unittests --gtest_filter="ArcVmClientAdapterTest.*" Change-Id: I53a6174cdfa64c9607bcbf64da90d8855e735fc3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2581018Reviewed-by:
Yusuke Sato <yusukes@chromium.org> Commit-Queue: Yusuke Sato <yusukes@chromium.org> Commit-Queue: Sherry Hu <shuanghu@google.com> Cr-Commit-Position: refs/heads/master@{#835064}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/eca04eeeb8d8..fde98cbddd43 2020-12-09 reed@google.com Revert "Use explicit samplingoptions" 2020-12-09 johnstiles@google.com Add $genHType versions of frexp and ldexp. 2020-12-09 michaelludwig@google.com Simplify layer management in SkCanvas 2020-12-08 bsalomon@google.com Remove RGB8 Mali-400 workaround 2020-12-08 reed@google.com Use explicit samplingoptions 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 jmbetancourt@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: chromium:1150368 Tbr: jmbetancourt@google.com Change-Id: Id83e204eaf7bdb1de769b30f874eafbd32b2f2cb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580768Reviewed-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@{#835063}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/19739b881bea..7cbfe50ac1b1 2020-12-09 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS. 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: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I435cb3edf17123a776557d6237f2febc0d5333bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580772Reviewed-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@{#835062}
-
Hui Yingst authored
This CL migrates base::Bind to base::BindOnce/Repeating in extensions/renderer/wake_event_page*, and migrates MakeRequestCallback and OnResponseCall to base::OnceCallback/RepeatingCallback. Bug: 1152265 Change-Id: I883f5dbcb050688bc45f85b96d0b6b8628f2cdef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2573386 Commit-Queue: Hui Yingst <nigi@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/master@{#835061}
-
Timothy Loh authored
This CL updates the USB service (UsbDeviceManager) when running on Chrome OS to restrict access to mass storage devices and interfaces to only Guest VMs. This is in preparation for allowing access to these interfaces from the permission broker (crrev.com/c/2530573), for sharing to VMs. Currently the permission broker denies access to mass storage devices unless set in the allowlist policy, in which case chrome.usb and VM sharing would be able to access them (WebUSB has it's own filtering). As it appears this allowlist wasn't supposed to support mass storage devices, this CL will deny access chrome.usb access to these devices. The function EnumerateDevicesAndSetVmSharingClient() is added to allow access these devices to be shared to VMs. When this function is used, mass storage devices will be enumerated and shown when added/removed as usual. Any other clients (e.g. WebUSB, chrome.usb) will not see these devices, so we don't need to update them. In UsbDevice, mass storage interfaces will be locked down when a device is opened, so they are not able to be claimed. This ensures that devices with both mass storage and other interfaces will continue to deny access to the mass storage interfaces when used in WebUSB or chrome.usb. The flow for attaching USB devices to VMs doesn't use UsbDevice objects, but rather calls UsbDeviceManager::OpenFileDescriptor() and passes the FD to concierge directly. This API does not verify the caller is using the FD for VM sharing, but other components will not be able to open mass storage devices by accident here as they will not have access to the device's guid. Bug: 1146325 Change-Id: I844114a35e9653f55cad4a242d8939aa88cf56f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2548705Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Commit-Queue: Timothy Loh <timloh@chromium.org> Cr-Commit-Position: refs/heads/master@{#835060}
-
Theo Johnson-kanu authored
Bug: 1151253 Change-Id: Idcfcebe7f7edc8b2da95f7e168fe28fc9cd42803 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2579810Reviewed-by:
Azeem Arshad <azeemarshad@chromium.org> Commit-Queue: Nnamdi Theodore Johnson-kanu <tjohnsonkanu@google.com> Cr-Commit-Position: refs/heads/master@{#835059}
-
Matt Wolenetz authored
This change: 1) Exposes as static synchronous helpers the WebCodecs MakeMediaConfig methods' internals so that MediaSource can use them to obtain media::{Audio,Video}DecoderConfigs from WebCodecs {Audio,Video}DecoderConfigs. 2) Implements MediaSource::AddSourceBufferUsingConfig for encoded configs (not decodedMediaType), plumbing the media decoder config through the usual steps in MSE addSourceBuffer, and through new methods in WebMediaSource and WebMediaSourceImpl to let ChunkDemuxer::AddId know it will be expected to handle WebCodecs encoded chunk appends for the associated SourceBuffer. 3) Adds a tentative folder for MSE-for-WebCodecs web_tests and adds a test for the current behavior of addSourceBuffer(webcodecs decoder config) that this CL adds. Later changes will continue plumbing of the configs in ChunkDemuxer and SourceBufferState, and also add implementations and ChunkDemuxer/etc support for appendEncoded{Audio,Video}Chunks. The h264 parser and avcc conditionally created in #1, above, could then be used by SourceBuffer processing of appended EncodedVideoChunks, too. BUG=1144908 Change-Id: I90c1d90c3a28d5cc1e33b1e50e32f4cfea639784 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2548844 Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Chrome Cunningham <chcunningham@chromium.org> Reviewed-by:
Dan Sanders <sandersd@chromium.org> Cr-Commit-Position: refs/heads/master@{#835058}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/4565794f5eda..e43bd0925d76 2020-12-09 yuhengh@chromium.org WebUI metric: Implement benchmark_value 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 wenbinzhang@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:chromeos-kevin-rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: chromium:1099917 Tbr: wenbinzhang@google.com Change-Id: I942efd6995737e02a7365d588136dfcf033472c4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580764Reviewed-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@{#835057}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/a737e5f65ca1..c6b219431a16 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: Ib4072075b8ecc94ad98e33a0b0d4df457e5528a0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580205Reviewed-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@{#835056}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/e213663d1bc2..bb1cad334635 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 shend@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: shend@google.com Change-Id: I2db00065bacb5d2ce45c066bd7b2c080a7e4e9d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580765Reviewed-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@{#835055}
-