- 22 Aug, 2020 40 commits
-
-
Arthur Eubanks authored
Bug: 1114873 Change-Id: I100b125bb7955a5e8d31ea21fd20eed9b451d66a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367799 Commit-Queue: Nico Weber <thakis@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#800856}
-
Rahul Singh authored
This CL addresses a couple issues with Windows Video Capture. 1. VideoFacingMode was incorrectly set for inbuilt cameras. This was because we were using model_id to find devices in devices_info. For inbuilt cameras this was an empty string. As a result, on devices with multiple inbuilt cameras, all cameras had the same model_id and the VideoFacingMode was set for the wrong camera. Solution: Changed the code to use device_id instead of model_id. 2. Rear camera feed was incorrectly rotated. This was because we had the same camera rotation values for Front and Rear cameras. With this, when a device was rotated 90 or 270 degrees, the rear camera was off by 180 degrees. Solution: Set the camera rotation value in GetCameraRotation() for the 90 degree and 270 degree case after checking the VideoFacingMode. Testing: Verified that with these changes: 1. Windows devices with front and back cameras showed the correct rotation behavior for both cameras. 2. Devices with external cameras connected over USB were unaffected. Bug: 1090754 Change-Id: I44c13a9e77c050fe27875b8b22f5e2ee2f09f95b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2357556Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Commit-Queue: Rahul Singh <rahsin@microsoft.com> Cr-Commit-Position: refs/heads/master@{#800855}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/56694eedcf31..877d9df3d0c0 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 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: Change-Id: Ie16cd5a1e5cc9790f06d70ac305eb263baf53354 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370652Reviewed-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@{#800854}
-
Daniele Castagna authored
We're working toward the goal of always using double buffering in CrOS. This flag is useful to test Chrome with only double buffer. Bug: None Test: None Change-Id: I86e3be97ee91a62742ca07c8a93a68b4c3db7cd4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370426 Auto-Submit: Daniele Castagna <dcastagna@chromium.org> Commit-Queue: Daniele Castagna <dcastagna@chromium.org> Commit-Queue: Andres Calderon Jaramillo <andrescj@chromium.org> Reviewed-by:
Andres Calderon Jaramillo <andrescj@chromium.org> Cr-Commit-Position: refs/heads/master@{#800853}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/bf7acb2707b8..d16d65476219 2020-08-22 reed@google.com use pathbuilder 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 stani@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: stani@google.com Change-Id: Ib5cf92c70909f64f96ee3c03d760e6767e3e3bf8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370647Reviewed-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@{#800852}
-
Xianzhu Wang authored
For CompositeSVG, we should inform both PaintArtifactCompositor and PaintLayerCompositor about raster invalidation tracking. Bug: 1101002 Change-Id: If0d10ea1243e0c999a512fa28bd451436881b959 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370562 Auto-Submit: Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Philip Rogers <pdr@chromium.org> Reviewed-by:
Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#800851}
-
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: I6be8e01ca6445c1a0a0c9f3e453a974489a54627 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370643Reviewed-by:
-
Fritz Koenig authored
Modifier is most meaningful as a hex value as it is a bitfield. BUG=none TEST=none Change-Id: I9cc35aa773b5360a2ffa8f3584e554b351263247 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363721 Commit-Queue: Fritz Koenig <frkoenig@chromium.org> Reviewed-by:
Thomas Guilbert <tguilbert@chromium.org> Reviewed-by:
Alexandre Courbot <acourbot@chromium.org> Auto-Submit: Fritz Koenig <frkoenig@chromium.org> Cr-Commit-Position: refs/heads/master@{#800849}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/c599f924c1c0..56694eedcf31 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 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: Change-Id: I4d174c946e51b5f3c1ceba6b5b0c84c00ba2a485 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370336Reviewed-by:
-
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-betty-pi-arc-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-eve-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-kevin-chrome TBR=chrome-os-gardeners@google.com Change-Id: Iab1be4c753354b492c83116fa62211164e95f179 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370423Reviewed-by:
ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#800847}
-
Ben Mason authored
TBR=govind@chromium.org Change-Id: I9ce35cfffab496f76cc79ed2b79f15487b87e12c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370425Reviewed-by:
Ben Mason <benmason@chromium.org> Commit-Queue: Ben Mason <benmason@chromium.org> Cr-Commit-Position: refs/heads/master@{#800846}
-
Philip Rogers authored
The spec [1] states that will-change: opacity should create a stacking context for inlines in the same way that non-zero opacity does. This was fixed by https://crrev.com/776581 ("Unify CSS grouping properties") but we didn't have a testcase. This patch adds a WPT test of this behavior. [1] https://drafts.csswg.org/css-will-change/#will-change Bug: 1119651 Change-Id: I7abd4006b61039d9302f8ac9036848aeb37df476 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370095 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Auto-Submit: Philip Rogers <pdr@chromium.org> Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#800845}
-
chromium-internal-autoroll authored
Release_Notes:http://go/help_app-x20/relnotes/Nightly/help_app_nightly_202008220800_RC00.html https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/help_app/app/+/PPRWlbFgcLiLZEouIVVYQInyQNO7es0BR2SEuWBYrIQC If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/help-app-chromium-autoroll Please CC help-app@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.chrome.try:linux-chromeos-chrome Bug: None Tbr: help-app@grotations.appspotmail.com Change-Id: I793758f344415349d7a3965bea4aa085d7483923 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370330Reviewed-by:
-
chromium-internal-autoroll authored
Release_Notes:http://go/media_app-x20/relnotes/Nightly/media_app_202008220800_RC00.html https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/media_app/app/+/YGPMOe2eHARlZiJiLGYNp2n_35FHrR4LpmgA4FEHiC8C If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/media-app-chromium-autoroll Please CC media-app@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.chrome.try:linux-chromeos-chrome Bug: b/164112614 Tbr: media-app@grotations.appspotmail.com Change-Id: Iba2415cc1c60373d6fa97eeb32f3b0472b61df36 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370329Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/2856a9b1a98f..c599f924c1c0 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 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: Change-Id: Icafa58b9af9af85ac064025cb22558264c00a972 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370323Reviewed-by:
-
Sangwoo authored
1. Get decoration bounds path from graphics context Previously, path info in TextDecorationInfo was not same with the bounds which GraphicsContext actually paint. In order to remove this mismatch, get decoration path from GraphicsContext and set it to TextDecorationInfo. 2. Inflate decoration bounds by -0.5 when getting text intercepts. Skia returns TextIntercepts even when a glyph cross the decoration bounds less than 1px. In order to ignore some of these, inflate the decoration bounds by -0.5px. TODO: It'd be better to get path from GraphicsContext for solid line too. Bug: 808603 Change-Id: I5f57760b3c948dfd649b573adeecbaf8de7a5b5b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2355161 Commit-Queue: Stephen Chenney <schenney@chromium.org> Reviewed-by:Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#800841}
-
Daniel Classon authored
Add deep links to the old Sync subpage of the People page (/syncSetup). Bug: 1084154 Change-Id: Icc07986d861a1e463fb9e8da8436b9747cf3b1fa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363815 Commit-Queue: Kyle Horimoto <khorimoto@chromium.org> Reviewed-by:
Jimmy Gong <jimmyxgong@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#800840}
-
Xianzhu Wang authored
We already don't propagate subpixels across non-translation transforms in blink. However, for will-change:transform and transform animations, the compositor may change a transform from a translation to a non-translation transform not known by blink, and previously propagated subpixel might become inappropriate, so we should also prevent subpixel propagation for them. Bug: 931950 Change-Id: I302c2e1140f7ff566e2aeaaaeb92c3e9a90c9bf3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368237 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#800839}
-
Nate Fischer authored
No change to logic, only docs. This updates java_cpp_strings docs: * The first paragraph incorrectly stated this uses comments to determine the Java class name. This corrects that statement. * Merges the two GN steps into one, explains it's a best practice to add this to an android_library (or create a new one if there is none), and recommends private visibility for :java_switches_srcjar. Test: Upload to gerrit > open file > click "gitiles" Change-Id: I4ae45da15f7db02a9d4c101de1a23c40f154b464 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2369652 Commit-Queue: Bo <boliu@chromium.org> Auto-Submit: Nate Fischer <ntfschr@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#800838}
-
David Bienvenu authored
A few other mostly cpplint fixes, no functional changes. Bug: 1010217 Change-Id: I0a723054e430242adea6f75b9ee33fc7fceb250d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368418Reviewed-by:
Collin Baker <collinbaker@chromium.org> Commit-Queue: David Bienvenu <davidbienvenu@chromium.org> Cr-Commit-Position: refs/heads/master@{#800837}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1598054321-87d797542a8415d31d407f7b135c9596dfac4588.profdata to chrome-mac-master-1598095166-910bc29dade724220300819e5b5396b40eab51f4.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-mac-chromium Please CC sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: chrome/try:mac-chrome Tbr: sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@google.com Change-Id: Ie827d11f9219217690cdb775dc76a4cb0ed40e0e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370215Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/88624993b0ee..b4a4611be4d7 2020-08-22 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: I023a1a4c12fe81bd3d56e597c3e9a2d457d74392 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370214Reviewed-by:
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/e8dc820fbc1e..ce78ce2e2868 2020-08-22 cwallez@chromium.org Tiny cleanup of GetMappedRange. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/dawn-chromium-autoroll Please CC cwallez@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel Bug: None Tbr: cwallez@google.com Change-Id: Ifd944a86dbcf90edec04324276f16c33cedd5917 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370209Reviewed-by:
-
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: I8c2fc6b69851868ead1b2020cc5a912cae2358c0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370212Reviewed-by:
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/fbb49b4f7f86..233cb555112c 2020-08-22 eladalon@webrtc.org Make RTCError::sctp_cause_code const If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: Iab407a80ea384d81f09662b780a80cef3a73a21f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370210Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/46b51582a581..2856a9b1a98f 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 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: Change-Id: I085d6599fc403e2df3fca2335240c741557ce1b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370206Reviewed-by:
-
Internal Frameworks Autoroller authored
TBR=bling-team@google.com Change-Id: I2dcdf99e35414e9573578fa3a5be3a52c285811a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370184Reviewed-by:
Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#800830}
-
Xiaodan Zhu authored
Bug: 1116229 Change-Id: I583ea76360fcaab0d5a9ec55adf80ff6432a0b9b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368824Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Commit-Queue: Xiaodan Zhu <zxdan@chromium.org> Cr-Commit-Position: refs/heads/master@{#800829}
-
Sammie Quon authored
Requested in crrev.com/c/2354798. This will simplfy things down the line as we use more index lookup and remove const from some parameters in RootWindowDeskSwitchAnimator. Test: manual, existing tests Bug: 1111445 Change-Id: I7250d969b95f08da5819c73ca325bce2db0ea5bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2369518Reviewed-by:
-
Mitsuru Oshima authored
This is a revised version of original attempt crrev.comc/c/2166804. Instead of creating a new layers, this clone and animate the window's layer, but makes sure that the animating layer is at the bottom of other layers within the window. * It adds a invisible view with a layer at the bottom of the non_client_view (no frame w/o this, so we can exclude such case). * Adds the animating layer as a child of this view, with "SetMasksToBounds(false)" so that it will not be clipped during animation. * Once animation is done, this animating, old layer will be removed. Bug: 1073685 Test: covered by unittests. Change-Id: Ib9ae60694fb461dda354fea4fd52e4e01186a6a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2335811Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Mitsuru Oshima <oshima@chromium.org> Cr-Commit-Position: refs/heads/master@{#800827}
-
Aya ElAttar authored
- Changed constructing the clipboard data endpoint, in case its type is a kUrl, from using GetLastCommittedURL of renderFrameHost to GetLastCommittedOrigin instead to avoid getting "about:blank" for Google Docs. Bug: 1116103 Change-Id: I0bea243358a995bad342afb63e9da55d3455e55b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362849Reviewed-by:
Charlie Reis <creis@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Aya Elsayed <ayaelattar@chromium.org> Cr-Commit-Position: refs/heads/master@{#800826}
-
Rob Buis authored
Implement basic operator DOM and styling support. Map lspace, rspace, minsize and maxsize attributes to internal properties [1]. Since lspace is shared with mpadded the MathPaddedLSpace internal property is renamed to MathLSpace. Note that this CL does not have a visual effect yet, that will happen once we introduce the operator layout algorithm and operator dictionary. [1] https://mathml-refresh.github.io/mathml-core/#operator-fence-separator-or-accent-mo Bug: 6606 Change-Id: I0999f26ec7f5765715fdf7ceab5a91296e6463bb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2340919Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Commit-Queue: Rob Buis <rbuis@igalia.com> Cr-Commit-Position: refs/heads/master@{#800825}
-
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-betty-pi-arc-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-eve-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-kevin-chrome TBR=chrome-os-gardeners@google.com Change-Id: Iaf5acebcf0b2845d26b81e43d048cb193a75cbe0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370013Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/682f9141d174..1d331c9131bd 2020-08-22 cclao@google.com Vulkan: Use context staging buffer for copyImageDataToBuffer 2020-08-22 cnorthrop@google.com Capture/Replay: Fixes for PUBG:Mobile 2020-08-21 jmadill@chromium.org Feedback Loop Redesign 3/3: Remove feedback loop tracking. 2020-08-21 ianelliott@google.com Vulkan: Fix compilation error 2020-08-21 ianelliott@google.com Vulkan: do not end render pass when invalidating If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC cnorthrop@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: cnorthrop@google.com Test: Test: Capture first 2000 frames of PUBG:MobileTest: Test: PUBG MOBILE on AndroidTest: Test: angle_deqp_gles3_tests --gtest_filter=dEQP.GLES3/functional_fbo_invalidate_* --use-angle=vulkanTest: Test: angle_white_box_tests --gtest_filter=VulkanPerformanceCounterTest.InvalidatingAndUsingDepthDoesNotBreakRenderPass/* Change-Id: I53392122aac5c3d7f87fae1da8a43a79546f1505 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2369246Reviewed-by:
-
sauski authored
To support E2E testing of the HaTS Next implementation, logic is added to always launch a test survey when a tab is opened and the testing flag is enabled. Logic is also added to prevent multiple HaTS Next survey from opening at the same time, as these are not modal and not bound to a specific tab, displaying multiple survey simultaneously was previously possible. Bug: 1110888 Change-Id: I324c08460f468e5ba9281f7b18b763acd1d4a317 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2359031Reviewed-by:
Bret Sepulveda <bsep@chromium.org> Reviewed-by:
Theodore Olsauskas-Warren <sauski@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Commit-Queue: Theodore Olsauskas-Warren <sauski@chromium.org> Cr-Commit-Position: refs/heads/master@{#800822}
-
Brian Geffon authored
This CL is the equivalent for per-process reclaim for ARC++, which is also referred to as WorkingSetTrim (this is the name Windows used in Chrome). ARC++ apps can be reclaimed when the system is under memory pressure. The following tunables exist to control this behavior: - Limit the frequency at which we fetch the ARC process list. - Limit the frequency at which an individual ARC app may be reclaimed. - Specify the amount of time an app must have been inactive to be reclaimed. - Specify the maximum number of individual ARC apps which can be reclaimed per round. - Control whether both system processes or apps are reclaimed. Again this only applies when the system is under moderate memory pressure, when there is no memory pressure we will never reclaim ARC apps. BUG=chromium:973963 Change-Id: I211590b123dfff5aaa5738d3025d1eb830fac427 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2335816 Commit-Queue: Brian Geffon <bgeffon@chromium.org> Reviewed-by:
Chris Hamilton <chrisha@chromium.org> Reviewed-by:
Yury Khmel <khmel@chromium.org> Reviewed-by:
Yusuke Sato <yusukes@chromium.org> Cr-Commit-Position: refs/heads/master@{#800821}
-
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: I4aed042e0fea2c394d169135274053272c8680fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2369247Reviewed-by:
-
Lei Zhang authored
- Add a base chrome_pdf::InputEvent class. - Switch pp::InputEvent usage to chrome_pdf::InputEvent in PDFiumEngine. - Switch PPAPI input modifiers to chrome_pdf::InputEventModifier equivalents. With these changes, PPAPI input event usage is limited to just input_event_conversions.cc, out_of_process_instance.cc, and pdfium_assert_matching_enums.cc. Bug: 1091834 Change-Id: If62f82746ed86da913a5ba77771112ddce45bf41 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367119 Commit-Queue: Lei Zhang <thestig@chromium.org> Reviewed-by: Ankit Kumar
🌪 ️ <ankk@microsoft.com> Reviewed-by:K. Moon <kmoon@chromium.org> Cr-Commit-Position: refs/heads/master@{#800819}
-
kouhei authored
Bug: None Change-Id: I4c9d95eef2f96b03e89d9cac08711b9e47c50784 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367258Reviewed-by:
Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by:
Dominic Farolino <dom@chromium.org> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Commit-Queue: Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/master@{#800818}
-
Lei Zhang authored
It works around a problem that is not applicable to Chromium. Change-Id: I8eaaf8ed1340e9892461e89535b3d896c822ce0b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2369504 Commit-Queue: Victor Costan <pwnall@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#800817}
-
