- 09 Dec, 2020 40 commits
-
-
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}
-
Harvey Yang authored
As we're launching IIO Service, which provides all sensors' data to other processes, this commit adds LightProviderInterface and rename AlsReaderImpl as an implementation of the interface to allow a mojo implementation later, which waits for lux values from IIO Service. BUG=b:173485266 TEST=unit tests and run on nightfury(hatch) Change-Id: I8d85a5df2a850254f629ff377ae7e64051a780a1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2552313 Commit-Queue: Cheng-Hao Yang <chenghaoyang@chromium.org> Reviewed-by:
Thanh Nguyen <thanhdng@chromium.org> Reviewed-by:
Jia Meng <jiameng@chromium.org> Cr-Commit-Position: refs/heads/master@{#835054}
-
Asami Doi authored
Currently, a warning message logs to the DevTools console when the offline capability check fails in the "warn_only" mode. This CL enables to show the message in Application > Manifest > Installability in DevTools too (only when the mode is "warn_only"). `WARN_NOT_OFFLINE_CAPABLE` doesn't affect the result of whether or not showing install prompts. Bug: 965802 Change-Id: Iadb169230fe3a82821d011551ad98cd221b259d9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576980 Commit-Queue: Asami Doi <asamidoi@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#835053}
-
Moe Ahmadi authored
Both OmniboxLocalZeroSuggestForAuthenticatedUsers and OmniboxZeroSuggestCaching are enabled by default and should be disabled in the fieldtrial testing config Bug: 1136654, 1136649 Change-Id: I1ae031c14d932ce56265414a92da7faa7ac9e425 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580781 Auto-Submit: Moe Ahmadi <mahmadi@chromium.org> Commit-Queue: Mark Pearson <mpearson@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Cr-Commit-Position: refs/heads/master@{#835052}
-
Ken Buchanan authored
This change: - Appends a 'Sec-WebID' header to flag what kind of traffic this is to the IDP and guard against CSRF. - Restricts WebID to potentially trustworthy origins rather than URLs - Fixes a crash in OnWellKnownLoaded Bug: 1141125 Change-Id: I13d55c67ee79a8060f1947baec778350b4f5b872 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2579823 Commit-Queue: Ken Buchanan <kenrb@chromium.org> Reviewed-by:
Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#835051}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=pbommana@chromium.org Change-Id: I8535b49f7291e601e041ca062f4490efdd12b329 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580586Reviewed-by:
Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#835050}
-
Bao-Duy Tran authored
Almost all of input_methods.txt [1] is obsolete; it's on track for complete deprecation and hopefully removal. It's a remnant from before the migration to extension-based input methods, approx 9 years ago. This CL further trims gen_input_methods.py (follow-up to [2]), hence also the C++ code it autogens, to the minimal that Chrome-on-CrOS still needs from input_methods.txt nowadays -- i.e. an allowlist of XKB layout IDs for login and lock screens. [1] https://source.chromium.org/chromium/chromium/src/+/master:chromeos/ime/input_methods.txt;drc=8cbe6597e4cc8457f4e33ef2ad189f0553f59f54 [2] https://crrev.com/c/2569231 Bug: 1134526 Change-Id: I69c12fed9c3c20c3e77428a4e4a4dcda7496a365 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576301 Commit-Queue: Bao-Duy Tran <tranbaoduy@chromium.org> Reviewed-by:
My Nguyen <myy@chromium.org> Reviewed-by:
Yuichiro Hanada <yhanada@chromium.org> Reviewed-by:
Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#835049}
-
Alexander Timin authored
R=shaseley@chromium.org BUG=1155905 Change-Id: I80c643923a0c607f49e48a3e8813d197f696ec2c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580524 Commit-Queue: Alexander Timin <altimin@chromium.org> Commit-Queue: Scott Haseley <shaseley@chromium.org> Auto-Submit: Alexander Timin <altimin@chromium.org> Reviewed-by:
Scott Haseley <shaseley@chromium.org> Cr-Commit-Position: refs/heads/master@{#835048}
-
Mark Schillaci authored
This CL is the sixth part of an effort to port the existing Desktop feature to Android. This feature enables a user to send an image to Google to process to generate a descriptive alt text if a website does not provide one. Design Doc: go/2020-q1-android-image-descriptions Slide Deck: go/clank-imageDescriptions Launch Bug: 1057168 Original Desktop Design Doc for reference: go/chrome-a11y-annotations-design This is a conservative approach, we use a separate set of profile Prefs for this feature rather than syncing with the Desktop Prefs. This can be updated in time as needed. ---------- This CL adds the following: - kExperimentalAccessibilityLabels flag to chrome://flags - Enables feature flag by default on Android Note: There is no change to: tools/metrics/histrograms/enums.xml as we will reuse the existing values: <int value="-1942057472" label="ExperimentalAccessibilityLabels:enabled"/> <int value="575380532" label="ExperimentalAccessibilityLabels:disabled"/> ---------- AX-Relnotes: Enables experimental accessibility labels feature flag by default on Android, and includes it in chrome://flags. Bug: 1057169 Change-Id: Ia8fab4f112b905a5a7b6ce05e45d7c345dc8b0f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575727Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Mark Schillaci <mschillaci@google.com> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Mark Schillaci <mschillaci@google.com> Cr-Commit-Position: refs/heads/master@{#835047}
-
David Black authored
This is part two of a series of CLs that will expose file change events to observers of a new browser context keyed service. In this CL, the new service is notified of copy and move events originating from Chrome OS specific file system operations which are created by the Chrome OS file system backend. This involved creation of a new chromeos::FileSystemOperation class serving as a thin extension to the default file system operation impl. This thin extension allows changes to storage// code to be minimal. Additional file change events will be wired up in a follow up CL following the same pattern. Design: http://shortn/_xrD1GHuIf1 Bug: 1136173 Change-Id: I9b906b309a1fd6b3d3f5b189c683ae6ffdd65f38 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2551636 Commit-Queue: David Black <dmblack@google.com> Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Marijn Kruisselbrink <mek@chromium.org> Reviewed-by:
Sergei Datsenko <dats@chromium.org> Cr-Commit-Position: refs/heads/master@{#835046}
-
Robbie McElrath authored
BrowserFragmentImpl extending FragmentHostingRemoteFragmentImpl means we have a FragmentController (and therefore a FragmentManager) available to us in the main WebLayer UI. Upcoming page info changes will use this FragmentManager, and mediarouter could be refactored to use this as well instead of creating its own RemoteFragment. Bug: 1077766 Change-Id: Id659555b827feed4293b062f8b0d8c6f4889daba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575753 Commit-Queue: Robbie McElrath <rmcelrath@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#835045}
-
kenkangxgwe authored
* Extract original implementation from display_settings_manager_impl.cc to screen_power_controller_aura.cc * This allows the display to be enabled/disabled when allow_screen_power_off_ is set to be false/true after screen is off. * This handles multiple power requests at the same time (e.g. SetScreenOn() and SetScreenOff() at the same time). * Add logs when screen is successfully powered on/off. * Add unittest to ScreenPowerControllerAura. Bug: b/162546246 Bug: b/173504008 Test: cast_display_settings_unittests --single-process-tests --gtest_filter=ScreenPowerControllerAuraTest.* Test: logcat | grep "screen_power_controller", mute the mic, in low light: display off mode, and toggle the display timeout on and off. Logs should show that "Screen is powered on/off". Change-Id: If470d72eeb11c53e6dea8eefbd63f71e0f6c4dd2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391333 Commit-Queue: Mingyu Kang <kenkangxgwe@google.com> Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Reviewed-by:
Sean Topping <seantopping@chromium.org> Cr-Commit-Position: refs/heads/master@{#835044}
-
Alan Screen authored
Bug: 1151726 Change-Id: I294554670b0ee4fe4281389d0c87cfbae87b1a81 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580878Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Commit-Queue: Alan Screen <awscreen@chromium.org> Cr-Commit-Position: refs/heads/master@{#835043}
-
Chong Gu authored
Bug: 1156885 Change-Id: I7474d2e833a41e6ccbb40828abac9523fcded533 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2581002 Auto-Submit: Chong Gu <chonggu@google.com> Reviewed-by:
Haiyang Pan <hypan@google.com> Commit-Queue: Haiyang Pan <hypan@google.com> Cr-Commit-Position: refs/heads/master@{#835042}
-
Xing Liu authored
This CL implements the core code for weekly notification. 1. When chrome starts, if we have unread page and no notification is scheduled, schedule a new one. 2. Before showing the notification, update the unread page count text. And schedule a new one if needed. The code to open bookmark UI from notification is not implemented in this CL. Bug: 1139073 Change-Id: I7b723ac3b6457ca1cd9c4302316806aa22db8e32 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2558960 Commit-Queue: Xing Liu <xingliu@chromium.org> Reviewed-by:
David Trainor <dtrainor@chromium.org> Cr-Commit-Position: refs/heads/master@{#835041}
-
Mei Liang authored
The TabProperties.TAB_CLOSED_LISTENER and TabProperties.TAB_SELECTED_LISTENER properties can be null when Instant Start is enabled. This CL fixes the crash by performing a null check. Bug: 1153604 Change-Id: If1539f457023bff3de18e6a337e97daa53c6fc2f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580399 Commit-Queue: Mei Liang <meiliang@chromium.org> Reviewed-by:
Yue Zhang <yuezhanggg@chromium.org> Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Cr-Commit-Position: refs/heads/master@{#835040}
-
Peng Huang authored
This is a reland of bc24c252 add failed vulkan related test in the filter. Original change's description: > Disable Vulkan for LACROS > > Bug: 1155622 > Change-Id: I8def57cef648ec4881f666aec614200d13eac972 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577815 > Auto-Submit: Peng Huang <penghuang@chromium.org> > Commit-Queue: Erik Chen <erikchen@chromium.org> > Reviewed-by: Erik Chen <erikchen@chromium.org> > Cr-Commit-Position: refs/heads/master@{#834507} Bug: 1155622 Change-Id: I9dde50222a5d947eab2c8b63bbcd6c5d8f4409fe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2578170 Commit-Queue: Peng Huang <penghuang@chromium.org> Reviewed-by:
Robert Kroeger <rjkroege@chromium.org> Reviewed-by:
Jonathan Backer <backer@chromium.org> Reviewed-by:
Erik Chen <erikchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#835039}
-
Xianzhu Wang authored
Previously we discard subpixel accumulation for all transform animations in case that the transform animation may apply a transform though which the subpixel accumulation can't be propagated, e.g. scale, rotation. However, for a translation-only animation, this caused different pixel-snapped offset of the element from the pixel-snapped offset before the animation and maybe 1 pixel glitch at start/end of the animation. Now check if the transform animation is translation only, and if yes, allow propagation of the subpixel accumulation. Bug: 1155029 Change-Id: I0cf759721b6c121f22310a445b679c7283973889 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2578387Reviewed-by:
Robert Flack <flackr@chromium.org> Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#835038}
-
Brian Sheedy authored
Adds a new version of the GPU unexpected pass finder script backed by ResultDB. This allows it to now detect cases of a test expected to be flaky but passing 100% of the time, along with a number of other improvements such as outputting to a more readable HTML file. Bug: 998329 Change-Id: I96dec74a355c075bfd4badc7bc4e5c5107b950d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2548644 Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Reviewed-by:
Yuly Novikov <ynovikov@chromium.org> Cr-Commit-Position: refs/heads/master@{#835037}
-
Frank Tang authored
Make IOS smaller https://chromium.googlesource.com/chromium/deps/icu.git/+log/6a33b647c..8bb622 TBR=jshin@chromium.org Bug: 1133219 Change-Id: I7e39dbe68b6ef51b1dadca867e2cfd1c0b1cb0dd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580108Reviewed-by:
Frank Tang <ftang@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#835036}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/99b0e4a5f4c0..0e323e7bff96 2020-12-09 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Please CC ajp@google.com,apolito@google.com,ehmaldonado@google.com,sokcevic@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: ajp@google.com,apolito@google.com,ehmaldonado@google.com,sokcevic@google.com Change-Id: I9a01c2d7dc575fc6ab76f0798faef071dc6eb8f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2581064Reviewed-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@{#835035}
-
chromium-autoroll authored
https://chromium.googlesource.com/openscreen.git/+log/963b0a6bd915..66f231597428 2020-12-09 miu@chromium.org Remote virtual connections [2/3]: Add Open/CloseRemoteConnection(). 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: Ib6ae966a41edcf8d556fcef7a7728b627200f04e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2581065Reviewed-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@{#835034}
-
WangHui authored
Update AndroidProtocolHandler to use GURL. BUG=783819 Change-Id: I0fc389fe4190b4263562566e35d6525c32837dfe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2578876 Commit-Queue: HuiWang <wanghui210@huawei.com> Reviewed-by:
Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#835033}
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1607417661-b29be925ba4468c1cb5f7aba9df03f08f5d1a452.profdata to chrome-win64-master-1607450253-68d0fa295c41f196aa098d193a0a21605dcba7f2.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-win64-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:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: Id43bab467d3d7e9394c320b41a03283baad4b06d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580579Reviewed-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@{#835032}
-
Noel Gordon authored
Remove redundant (non-files-ng) file_types.css filter rule. CL:2094516 removed this CSS filter rule use in files-ng for reference. Bug: 1102263 Change-Id: I1160d2a2ac332010164456c20362425d191d1dc4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2581158Reviewed-by:
Alex Danilo <adanilo@chromium.org> Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Commit-Queue: Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#835031}
-
James Vecore authored
The nearby-preview element was missing it's mojo deps html imports. It was passing tests when optimize_webui=true because other files were resolving the dependency in the bundle. Fixed: 1156833 Change-Id: Idf3022f74475c7ca2de021fc15d974104425b7bd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580909 Auto-Submit: James Vecore <vecore@google.com> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Commit-Queue: James Vecore <vecore@google.com> Cr-Commit-Position: refs/heads/master@{#835030}
-
Liquan (Max) Gu authored
Motivation: * Context is the low level details that PaymentUiService should not care about, so this CL delegate the context getter to its callers. * Chrome is moving away from unnecessarily depending on ChromeActivity, so this CL replaces some ChromeActivity use cases with Context. Bug: 1154371 Change-Id: I826d2c531b986ec1498435e175b5b0834112de0e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580084Reviewed-by:
Rouslan Solomakhin <rouslan@chromium.org> Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org> Cr-Commit-Position: refs/heads/master@{#835029}
-
Julie Jeongeun Kim authored
This CL adds checking if PrintCompositeClient exists on PrintViewManagerBase::SetAccessibilityTree() since it could be null with oopif configuration. Bug: 1155909 Change-Id: I15e6b073b60f7a1889ff5b97e4ab27039538a3f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574643Reviewed-by:
Wei Li <weili@chromium.org> Commit-Queue: Julie Kim <jkim@igalia.com> Cr-Commit-Position: refs/heads/master@{#835028}
-
Joe Mason authored
Eliminate the dependency on content/ by passing a callback to bind the mojo interface instead of looking up the RenderThread. This unblocks the removal of the components/renderer/performance_manager directory. R=bgeffon Change-Id: Id2d8ebe02e1234e30a9befc824927ac4bfc3b57f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575604Reviewed-by:
Brian Geffon <bgeffon@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Joe Mason <joenotcharles@chromium.org> Auto-Submit: Joe Mason <joenotcharles@chromium.org> Cr-Commit-Position: refs/heads/master@{#835027}
-
chromium-autoroll authored
Roll Chrome Linux PGO profile from chrome-linux-master-1607450253-17283bab00baae11cd74f4b35406a0ad23f10e88.profdata to chrome-linux-master-1607471901-85f06a8978ebf1d40d9cf80572b77a4ab0bcfbe1.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 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:linux-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I1e52fdfc7a11e5dca6a3e65679a987f49af95c13 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580051Reviewed-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@{#835026}
-