- 09 Sep, 2020 40 commits
-
-
Tibor Goldschwendt authored
Fixed: 1119748 Change-Id: I9e1ae79e2c495c6a784869baa77f2e7e9fedca8a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401852 Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Commit-Queue: John Lee <johntlee@chromium.org> Auto-Submit: Tibor Goldschwendt <tiborg@chromium.org> Reviewed-by:
John Lee <johntlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#805526}
-
nancylingwang authored
AppService reads app_info to get the last launch time, so get the last launch time from the old app info for 'was_tracked' case to set the correct time for app_info->last_launch_time. BUG=1124094 Change-Id: I10a58f91d0a9fa67ab36b5463f47f258a31bbb3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391420Reviewed-by:
Long Cheng <lgcheng@google.com> Commit-Queue: Nancy Wang <nancylingwang@chromium.org> Cr-Commit-Position: refs/heads/master@{#805525}
-
Liquan (Max) Gu authored
Change: * Move the UI logic of PaymentRequestImpl#buildUI() into PaymentUIsManager#buildPaymentRequestUI() * Change buildPaymentRequestUI()'s structure to return an error message. This way, PRImpl#buildUI()'s size can be reduced. * PRImpl no longer depends on: - org.chromium.chrome.browser.tab - org.chromium.chrome.browser.tabmodel - org.chromium.chrome.browser.compositor.layouts - org.chromium.chrome.browser.ChromeTabbedActivity Bug: 1102522 Change-Id: I5f61a57b7891ec06a59527852d1a37f14bda031a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2384315 Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org> Reviewed-by:
Rouslan Solomakhin <rouslan@chromium.org> Cr-Commit-Position: refs/heads/master@{#805524}
-
Yutaka Hirano authored
We're introducing a new interface, WebTransport, which will replace QuicTransport. WebTransport may also cover HTTP3Transport, so record use counters rather than relying on MeasureAs. Bug: 1123413 Change-Id: I17c22599eb82463756851a8d781eb6bebef50ac3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399165 Auto-Submit: Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Adam Rice <ricea@chromium.org> Reviewed-by:
Adam Rice <ricea@chromium.org> Cr-Commit-Position: refs/heads/master@{#805523}
-
chrome://multidevice-internalsKyle Horimoto authored
(1) Fix issue which set real PhoneHubManager when the page loads, even if it was already set. This prevents unnecessary re-initialization. (2) Fix issue which displayed the Phone Hub UI even when the flag was disabled; now, we show a button leading users to the flag. (3) Clean up some function names and alphabetize files. Bug: 1106937 Change-Id: Ie11e136f6087d14176081fb6a45a2c587bc6da18 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2402107Reviewed-by:Regan Hsu <hsuregan@chromium.org> Commit-Queue: Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#805522}
-
Dom Schulz authored
This change deletes the manifest.json, and pwa.html files, replacing them with an identical installation using a WebApplicationInfo struct created in C++. The reason for this is to avoid SWA installation flakiness and slowness. Bug: 1085274 Change-Id: I85fcf8589dc269ab2ed60b517ed65f69cc79735d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367397Reviewed-by:
Giovanni Ortuño Urquidi <ortuno@chromium.org> Reviewed-by:
Jiewei Qian <qjw@chromium.org> Reviewed-by:
Trent Apted <tapted@chromium.org> Commit-Queue: Dominic Schulz <dominicschulz@google.com> Cr-Commit-Position: refs/heads/master@{#805521}
-
Aaron Colwell authored
This change converts the site_url param to a SiteInfo in preparation for adding new checks that are based on other SiteInfo fields. This is part of an ongoing effort to replace site URL usage in method signatures with SiteInfo. Bug: 1085275 Change-Id: I67cc62db168f1d107890f66970041796ea9dcb8f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401333 Commit-Queue: Aaron Colwell <acolwell@chromium.org> Commit-Queue: Alex Moshchuk <alexmos@chromium.org> Auto-Submit: Aaron Colwell <acolwell@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#805520}
-
Becca Hughes authored
The other two modules are dummy modules and don't do anything so it makes sense that Kaleidoscope should be at the top so we can test it. Change-Id: Idb9a77ef78234242ac86f97a9127ef4203d10e0e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401862Reviewed-by:
Tibor Goldschwendt <tiborg@chromium.org> Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Auto-Submit: Becca Hughes <beccahughes@chromium.org> Cr-Commit-Position: refs/heads/master@{#805519}
-
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: I61d374985c37a85ac4de024010b85cdc3a8029e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2402052Reviewed-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@{#805518}
-
John Lee authored
Change-Id: I50bb0446d8716a2f2f9372937f753571442fec49 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398954Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Commit-Queue: John Lee <johntlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#805517}
-
Hoch Hochkeppel authored
Fixing a typo in the IAsyncOperation<int> GUID declaration to match the original value it purports to be a copy of. Without this change if this declaration is ever included in the same context as a declaration using the correct GUID from the SDK, the conflicting values will cause failures in several of the related COM calls around QueryInterface. Change-Id: I475ebc58b0b234446499a9cc1fbead6ac76b9305 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2393010Reviewed-by:
Will Harris <wfh@chromium.org> Commit-Queue: Hoch Hochkeppel <mhochk@microsoft.com> Cr-Commit-Position: refs/heads/master@{#805516}
-
Matthew Denton authored
Rmdir() and stat() don't work when using bionic on some architectures. Rmdir() uses __NR_unlinkat with AT_REMOVEDIR and stat uses __NR_fstatat64 and __NR_newstatat with AT_SYMLINK_NOFOLLOW. We should allow these syscalls when COMMAND_RMDIR and COMMAND_STAT are allowed, respectively. Change-Id: I54953e10f899e07ebadf2ee784179e897fcc1dd2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391618 Commit-Queue: Matthew Denton <mpdenton@google.com> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Reviewed-by:
Tom Sepez <tsepez@chromium.org> Cr-Commit-Position: refs/heads/master@{#805515}
-
Weilun Shi authored
Update CustomTabs.Visible and Android.ChromeActivity.Type's description to explain that the log timing has been changed in September 2020. Bug: 1007308 Change-Id: I00c4c23713bbbd968dce63267ca90422d0017563 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399841 Commit-Queue: Weilun Shi <sweilun@chromium.org> Auto-Submit: Weilun Shi <sweilun@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Cr-Commit-Position: refs/heads/master@{#805514}
-
Kehuangli authored
So recevier doesn't need to get stream info from side channel. And the delegate of the receiver can directly get the stream info from receiver. Merge-With: eureka-internal/408117 Bug: internal: 154953397 Test: Unittest. Change-Id: I5915b297cb3f252b7493b36719670f842a5d8c95 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352216Reviewed-by:
Kenneth MacKay <kmackay@chromium.org> Commit-Queue: Kehuang Li <kehuangli@chromium.org> Cr-Commit-Position: refs/heads/master@{#805513}
-
Maksim Ivanov authored
Fix use-after-move (potential) bugs found by the "bugprone-use-after-move" clang-tidy check. Bug: 1122844 Change-Id: I6bf3cff46d06bd2db9a667b5846bee26e7d76dfa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2383020Reviewed-by:
Jonathan Backer <backer@chromium.org> Commit-Queue: Maksim Ivanov <emaxx@chromium.org> Cr-Commit-Position: refs/heads/master@{#805512}
-
Jeroen Dhollander authored
The deep link from the Assistant Settings window still used chrome://settings/googleAssistant instead of the new path chrome://os-settings/googleAssistant. Bug: 956971 Change-Id: Id0cfcbf22613a378f253af805fb76cda12e81357 Tests: ash_unittests --gtest_filter="DeepLinkUtilTest*.*" and manually reproduced. Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398509 Commit-Queue: Jeroen Dhollander <jeroendh@chromium.org> Auto-Submit: Jeroen Dhollander <jeroendh@chromium.org> Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Cr-Commit-Position: refs/heads/master@{#805511}
-
Andrew Grieve authored
This reverts commit 1d5cb6af. Reason for revert: Breaking v8 kitkat bots Original change's description: > Increase android32_ndk_api_level 16 -> 21 > > We only support 21+, so we should build for it. > > Bug: 1116198 > Change-Id: I552a946b245de0f54485ea985e08b53b92186bb1 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367984 > Reviewed-by: Ben Mason <benmason@chromium.org> > Commit-Queue: Ben Mason <benmason@chromium.org> > Auto-Submit: Andrew Grieve <agrieve@chromium.org> > Cr-Commit-Position: refs/heads/master@{#804976} TBR=agrieve@chromium.org,benmason@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1116198, 1126469 Change-Id: Ia59936b975b6a17ec102fea02b9e86ba15de7b7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401268Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Andrew Grieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#805510}
-
Sadrul Habib Chowdhury authored
. Remove a TODO about renaming that does not need to happen anymore. . Use the sequence-number of a BeginFrameArgs in some traces, rather than having a separate identifier. This makes it easier to follow the traces, since various other trace-events also use the same sequence number from BeginFrameArgs. BUG=none Change-Id: Ifb2c8e0f480b884485dbfb8f1af7106200fbd0cd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392401 Auto-Submit: Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Khushal <khushalsagar@chromium.org> Reviewed-by:
Khushal <khushalsagar@chromium.org> Cr-Commit-Position: refs/heads/master@{#805509}
-
Sean Gilhuly authored
Tbr: kylechar@chromium.org Bug: 1126617 Change-Id: I98a8cb91df5366e38414a58581f4a80741cfafa5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2402162Reviewed-by:
Sean Gilhuly <sgilhuly@chromium.org> Reviewed-by:
kylechar <kylechar@chromium.org> Commit-Queue: Sean Gilhuly <sgilhuly@chromium.org> Cr-Commit-Position: refs/heads/master@{#805508}
-
Shrek Shao authored
These tests are seen being flaky in webgl2_conformance_gles_passthrough_tests on Android device Pixel 2. Mark them as RetryOnFailure TBR=kbr@chromium.org Bug: 1126631 Change-Id: I25f9225519e45529e289053d3b58998adb7d66a0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401810Reviewed-by:
Shrek Shao <shrekshao@google.com> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Shrek Shao <shrekshao@google.com> Cr-Commit-Position: refs/heads/master@{#805507}
-
Nate Chapin authored
Bug: 1114444 Change-Id: I2ec72c5dfd2418e5aa70c0de5eb2232306cf0c4b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399608 Commit-Queue: Nate Chapin <japhet@chromium.org> Reviewed-by:
Katie Dillon <kdillon@google.com> Cr-Commit-Position: refs/heads/master@{#805506}
-
Jesse Schettler authored
Add a new Polymer element, scanner-select, to display connected scanners in a dropdown. Styling and finalized strings will be added in subsequent CLs. Bug: 1059779 Change-Id: Ia913879262441094c7f7362b648f990943fde907 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2378138 Commit-Queue: Jesse Schettler <jschettler@chromium.org> Reviewed-by:
Jimmy Gong <jimmyxgong@chromium.org> Cr-Commit-Position: refs/heads/master@{#805505}
-
Maksim Ivanov authored
Drop std::move() calls that have no effect and only trigger the "bugprone-use-after-move" clang-tidy warning. Bug: 1122844 Change-Id: Ibdc6b74cd97ef71288e897317bbe81f8f5c740fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2382758 Commit-Queue: Maksim Ivanov <emaxx@chromium.org> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#805504}
-
David Van Cleve authored
This reverts commit fb37fef9. Reason for revert: seems like this breaks the tree, https://ci.chromium.org/p/chromium/builders/ci/mac-arm64-rel/1171? Original change's description: > Roll src/third_party/libjpeg_turbo/ 9d4f8005b..f38898135 (7 commits) > > https://chromium.googlesource.com/chromium/deps/libjpeg_turbo.git/+log/9d4f8005bc6c..f38898135a3b > > $ git log 9d4f8005b..f38898135 --date=short --no-merges --format='%ad %ae %s' > 2020-07-01 jonathan.wright Implement quantization using Arm NEON intrinsics > 2020-07-01 jonathan.wright Implement sample conversion using Arm NEON intrinsics > 2020-08-25 jonathan.wright Add compiler-independent alignment macro > 2020-07-01 jonathan.wright Add Arm NEON implementation of RGB->Grayscale > 2020-07-01 jonathan.wright Implement RGB->YCbCr using Arm NEON intrinsics > 2020-06-30 jonathan.wright Add Arm NEON implementation of h2v2_downsample > 2020-06-30 jonathan.wright Add Arm NEON implementation of h2v1_downsample > > Created with: > roll-dep src/third_party/libjpeg_turbo > > Bug: 922430 > Change-Id: I4edeccd8e58a529a5a7198448877756e7f7b7e22 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401461 > Reviewed-by: Leon Scroggins <scroggo@google.com> > Commit-Queue: Jonathan Wright <jonathan.wright@arm.com> > Cr-Commit-Position: refs/heads/master@{#805494} TBR=scroggo@google.com,cblume@chromium.org,jonathan.wright@arm.com Change-Id: I3386062045c36b44d7c9ef247dd009b978ccd3f0 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 922430 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401585Reviewed-by:
David Van Cleve <davidvc@chromium.org> Commit-Queue: David Van Cleve <davidvc@chromium.org> Cr-Commit-Position: refs/heads/master@{#805503}
-
Dan Sanders authored
Bug: 1125946 Change-Id: I6fd6072073704a6d2b9baa411acc414ebda5e043 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399083 Commit-Queue: Chrome Cunningham <chcunningham@chromium.org> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Reviewed-by:
Chrome Cunningham <chcunningham@chromium.org> Cr-Commit-Position: refs/heads/master@{#805502}
-
Marijn Kruisselbrink authored
The save file dialog needs to truncate any files that are opened. Before this was using base::File directly. This CL routes truncating through the file system backends to facilitate supporting non-local files. Bug: 1093653 Change-Id: I51c2cf8a776de70375e57be7a8a5d02641226bfa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392414 Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#805501}
-
Darwin Huang authored
This was likely missed earlier, but was noticed during https://crrev.com/c/2401500. Bug: 832129 Change-Id: Id808812aefc73cf3218db3ee915197b4da7937c4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2402101 Commit-Queue: Darwin Huang <huangdarwin@chromium.org> Auto-Submit: Darwin Huang <huangdarwin@chromium.org> Reviewed-by:
Marijn Kruisselbrink <mek@chromium.org> Cr-Commit-Position: refs/heads/master@{#805500}
-
Kevin Ellis authored
When removing a replaced animation, it is important to consider all timelines. Previously, we made the decision on a per timeline basis, resulting in failing to flag some animations as replaceable. Bug: 10293484 Change-Id: I8256f2eb69f710ba1ec04b095446bd30c1b64a97 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401505Reviewed-by:
Xida Chen <xidachen@chromium.org> Commit-Queue: Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#805499}
-
Miguel Casas authored
This CL extends Media.VaapiWrapper.VADisplayStateInitializeSuccess and takes the chance to clean up the owner/cc list. Bug: 1125687 Change-Id: I43b0bc32ad915d7e5680c64fafc73a2719e98146 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401998 Commit-Queue: Miguel Casas <mcasas@chromium.org> Commit-Queue: Tarun Bansal <tbansal@chromium.org> Auto-Submit: Miguel Casas <mcasas@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Cr-Commit-Position: refs/heads/master@{#805498}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/48df087f8a86..cee574832664 2020-09-09 jdapena@igalia.com GCC: init kImageMemoryBarrierData with initializer constructor 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: chromium:819294 Tbr: ianelliott@google.com Change-Id: I4c6a9f9257140433134e766123350219a28d2452 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401869Reviewed-by:
-
Sven Zheng authored
This reverts commit ee48012a. Reason for revert: Breakage. Original change's description: > [lacros] LUCI config for chromeos-amd64-generic-lacros-dbg > > Adds CI bot for chromeos-amd64-generic-lacros-dbg. > Also changes chromeos_amd64-generic_lacros, > chromeos_amd64-generic_lacros_rel to use other pre-defined configs > and it should have no differences. > > Bug: 1121667 > Change-Id: I6405da5c9ec0464fed59effeadcb3758f18ce927 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398976 > Reviewed-by: Yuke Liao <liaoyuke@chromium.org> > Commit-Queue: Sven Zheng <svenzheng@chromium.org> > Cr-Commit-Position: refs/heads/master@{#805467} TBR=erikchen@chromium.org,liaoyuke@chromium.org,svenzheng@chromium.org Change-Id: Ibd04e9914cae8fcd6ad3d35ea6ad6a40970af9f1 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1121667 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2402091Reviewed-by:
Sven Zheng <svenzheng@chromium.org> Commit-Queue: Sven Zheng <svenzheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#805496}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/6acdaf066c12..b0da2f1d4f9e 2020-09-09 heiserya@google.com Update WebPageReplayGo dependency documentation 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 rmhasan@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: None Tbr: rmhasan@google.com Change-Id: I955905340920a1544868bdd751d89d4ca97e2e8b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2402040Reviewed-by:
-
Jonathan Wright authored
https://chromium.googlesource.com/chromium/deps/libjpeg_turbo.git/+log/9d4f8005bc6c..f38898135a3b $ git log 9d4f8005b..f38898135 --date=short --no-merges --format='%ad %ae %s' 2020-07-01 jonathan.wright Implement quantization using Arm NEON intrinsics 2020-07-01 jonathan.wright Implement sample conversion using Arm NEON intrinsics 2020-08-25 jonathan.wright Add compiler-independent alignment macro 2020-07-01 jonathan.wright Add Arm NEON implementation of RGB->Grayscale 2020-07-01 jonathan.wright Implement RGB->YCbCr using Arm NEON intrinsics 2020-06-30 jonathan.wright Add Arm NEON implementation of h2v2_downsample 2020-06-30 jonathan.wright Add Arm NEON implementation of h2v1_downsample Created with: roll-dep src/third_party/libjpeg_turbo Bug: 922430 Change-Id: I4edeccd8e58a529a5a7198448877756e7f7b7e22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401461Reviewed-by:
Leon Scroggins <scroggo@google.com> Commit-Queue: Jonathan Wright <jonathan.wright@arm.com> Cr-Commit-Position: refs/heads/master@{#805494}
-
Peter Boström authored
This makes views::Combobox use a base::RepeatingCallback internally. Pre-existing uses of ComboboxListener are wrapped in a callback in set_listener(). Cleanups removing ComboboxListeners will follow. Bug: 772945 Change-Id: I2c1b4a7637ba5125fd7774e1f18f4751ced9959c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401951 Commit-Queue: Peter Boström <pbos@chromium.org> Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Auto-Submit: Peter Boström <pbos@chromium.org> Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#805493}
-
Prabir Pradhan authored
The geometry sent to the client is in screen coordinates in DP, as opposed to the display's coordinates. Scaling this value does not make sense, as different displays could have different scales. Ideally, we would send a display identfier and the geometry in display coordinates. However, since we don't have a mapping of display_id to wl_output yet in zcr_remote_shell, to avoid adding another soon-to-be-deprecated event to the protocol, we just remove the scaling. BUG=b:167267365 TEST=Manual with client-side change: verify input works on multiple displays with different scale factors. Change-Id: I250bb3f0c631d8783edae39a71b4fb84532d1729 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2388720 Commit-Queue: Prabir Pradhan <prabirmsp@chromium.org> Reviewed-by:
Mitsuru Oshima (Slow: gardener) <oshima@chromium.org> Cr-Commit-Position: refs/heads/master@{#805492}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/ce08265ba5b7..b24900a1aa39 2020-09-09 sugoi@google.com Update PowerVR Samples to ToT If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Please CC swiftshader-team+autoroll@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: I4d8259c816e9ce5f69fc22ccc5765010c06e818e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401877Reviewed-by:
-
Lukasz Anforowicz authored
CorbAllowlistAlsoAppliesToOorCors (aka CORS-for-content-scripts) has been shipping to the stable channel with Chrome85 since Aug 25th (~2 weeks ago). There have been just a handful of allowlisting requests so far - therefore, it seems okay to declare that this change has successfully shipped to the stable channel. This CL transitions enabling CorbAllowlistAlsoAppliesToOorCors away from 1) fieldtrial_testing_config.json and 2) field trial config (this includes preserving/copying the allowlisted extensions from site_isolation/data/CorsAndCorbAllowlist.gcl to //extensions/browser/url_loader_factory_manager.cc). After this CL we still retain an ability to allowlist extensions: 1. Via field trial config (affecting Chrome versions prior to this CL - Chrome 85, Chrome 86 and a little bit of Chrome 87) 2. Via the hardcoded allowlist in //extensions/browser/url_loader_factory_manager.cc (although this ability will go away soon - after https://crrev.com/c/2388709). This CL unblocks the following follow-up CLs: 1. Adding |max_version| to the field trial config (google3 - cl/330527651) 2. Starting deprecation of the allowlist (chromium3 - https://crrev.com/c/2388709) Bug: 920638 Change-Id: I635eb0777dc83a7ad448f57b9de388ae071e0c9b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2359393 Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Reviewed-by:
Charlie Reis <creis@chromium.org> Cr-Commit-Position: refs/heads/master@{#805490}
-
Marc Treib authored
This is essentially a revert of crrev.com/c/1082267 (undoing the actual 1-line change from that CL, but keeping the comment improvements). This is a temporary measure to investigate crbug.com/1120899. Bug: 1120899, 1082267 Change-Id: I7761418c038824218a7fc36b325f1b364f7bbbe5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401460 Commit-Queue: Marc Treib <treib@chromium.org> Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#805489}
-
Siyu An authored
1. Implemented CreateMetadataChangeList function. 2. Load metadata and notify processor ready to sync in the bridge initializer. Bug: 1112095 Change-Id: Id510d65145085d55676a4fc492e560fd194ac292 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399818 Commit-Queue: Siyu An <siyua@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#805488}
-
Reilly Grant authored
Now that we are starting to use the Core Location API for geolocation the Chrome app should probably have the location entitlement. Bug: 1051591 Change-Id: I66ff154a77298179737f12d4c00d43153422e325 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401269Reviewed-by:
Leonard Grey <lgrey@chromium.org> Commit-Queue: Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#805487}
-
