- 20 Jun, 2020 13 commits
-
-
Adam Langley authored
When prelighting credential IDs for getting an assertion, only send the matching credential ID on the following up=1 request, rather than the whole matching batch. Change-Id: I41534e82306b82c2332b44deb6466a9ee46c2905 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2250893 Commit-Queue: Adam Langley <agl@chromium.org> Reviewed-by:
Martin Kreichgauer <martinkr@google.com> Cr-Commit-Position: refs/heads/master@{#780525}
-
Daniel McArdle authored
In https://crrev.com/c/2089958, httpssvc_metrics_unittest.cc added 1.5% more tests to net_unittests (39202 to 39790). We can compute the number of tests that httpssvc_metrics_unittest.cc produces by looking at both occurrences of INSTANTIATE_TEST_SUITE_P and the number of parameterized tests. This accounts for (3*2*2)*(3*2*2)*2*2 + 2*6 = 588 tests = 39790 - 39202. This CL eliminates some redundancy in the instantiation of HttpssvcMetricsTestDomainParsing, bringing us to (3*2*2)*(2*1*1)*2*2 + 2*6 = 108 tests, which only contributes 0.28% more tests from a baseline of 39202. Bug: 1096073 Change-Id: I8d37f5ebcf883f7c116d46db9d6aa52c8bb75e7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2248751Reviewed-by:
Eric Orth <ericorth@chromium.org> Commit-Queue: Dan McArdle <dmcardle@chromium.org> Cr-Commit-Position: refs/heads/master@{#780524}
-
Aga Wronska authored
Two list items from 'G Suite for Education accounts' are removed: * Info about child data * Resources for schoolwork This cl needs to be merged back to M84, so it will be followed by a cleanup cl that removes string resources. The new screen look: https://photos.app.goo.gl/FzJqSEu8YXvXg7Pg9 Bug: 1097371 Test: Manually Change-Id: I8e4e23e7f6d19c52220ddaacf1d3690541ae1064 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2255027Reviewed-by:
Yilkal Abe <yilkal@chromium.org> Commit-Queue: Aga Wronska <agawronska@chromium.org> Cr-Commit-Position: refs/heads/master@{#780523}
-
Natalie Chouinard authored
Move styles shared by Chrome and WebLayer to //components. This is necessary to make shared changes to ChromeBasePreference to address https://crbug.com/1095981. Bug: 1095981 Change-Id: I615e5005fbe790053f3a6d3f93c8b4f94cf78b71 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2254453 Commit-Queue: Natalie Chouinard <chouinard@chromium.org> Reviewed-by:
Robbie McElrath <rmcelrath@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#780522}
-
Trent Begin authored
This change fills out a polymer component to parse the network-health information into a reabable table. This component is currently displayed in the chrome://network debugging ui. Bug: chromium:1076178 Change-Id: I51ded6483ae8368d3ad10b133df97aa57217f955 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2252570Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Commit-Queue: Trent Begin <tbegin@chromium.org> Cr-Commit-Position: refs/heads/master@{#780521}
-
Chase Phillips authored
Bumping file-handling-api flag from expiry milestone M82 to M88 so it continues to exist in the Chrome UI. While here, I'm removing oyiptong from owners, adding myself, and removing the @chromium.org portions to align with other flag entries. Bug: 1096282 Change-Id: Iae5905a8a112cd8921f22842d11aeaa75e1eaf58 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2250931 Auto-Submit: Chase Phillips <cmp@chromium.org> Commit-Queue: Chase Phillips <cmp@chromium.org> Commit-Queue: Olivier Yiptong <oyiptong@chromium.org> Reviewed-by:
Olivier Yiptong <oyiptong@chromium.org> Cr-Commit-Position: refs/heads/master@{#780520}
-
Natalie Chouinard authored
The PreferenceScreenLayout and PreferenceMediumText styles are non-standard and not used in the default settings screens, so inlining/ renaming them to discourage reuse. Fixing the Clear Browsing Data text style is tracked in crbug.com/1081933. Cleanup of the homepage editor change is not tracked because it will eventually be replaced through theHomepageSettingsUIConversion. Bug: 1077375 Change-Id: I955c4364770e68eb84c14fa3832450ccf1f56303 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2254714 Commit-Queue: Natalie Chouinard <chouinard@chromium.org> Reviewed-by:
Wenyu Fu <wenyufu@chromium.org> Reviewed-by:
-
Alex Moshchuk authored
DetermineSiteInstanceForURL has some logic for placing a subframe into its parent's SiteInstance if neither frame requires a dedicated process. This was a best-effort heuristic for process consolidation in a common case, but it is no longer needed given that default SiteInstances are now implemented and enabled by default in issue 787576. Bug: 1015882 Change-Id: Idb23813ea422bc8934bad0be29cf4eb575d686fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876979 Commit-Queue: Aaron Colwell <acolwell@chromium.org> Auto-Submit: Alex Moshchuk <alexmos@chromium.org> Reviewed-by:
Aaron Colwell <acolwell@chromium.org> Cr-Commit-Position: refs/heads/master@{#780518}
-
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: Ibd58616cc18980f298e04358e9d5820ac78bc12a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2255168Reviewed-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@{#780517}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/be637db5897d..f434fdc6ed11 2020-06-19 idanr@google.com Add minimum buffer size validation 2020-06-19 enga@chromium.org Protect against huge buffer allocations on macOS 10.12, 10.13 2020-06-19 enga@chromium.org Skip Buffer OOM tests when using ASAN 2020-06-19 cwallez@chromium.org dawn_wire: Factor the common command serialization pattern. 2020-06-19 enga@chromium.org Add support for multisampled sampling 2020-06-19 cwallez@chromium.org Vulkan: Simplify PNextChainBuilder 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: I16daec077997c8b52fc94c0ca39ce38d7f848851 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2255109Reviewed-by:
-
David Bertoni authored
The WindowOpenApiTest.WindowOpenSized was disabled on Mac but it is no longer broken. Note: This test was NOT disabled because it was flaky. Bug: 225601 Change-Id: I6d6193f7fa745f6189887e849d596855a0fc5b91 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2252928Reviewed-by:
Archana Simha <archanasimha@chromium.org> Commit-Queue: David Bertoni <dbertoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#780515}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/5ff7ad23ae08..1f80186d5001 2020-06-19 iannucci@chromium.org [led] Roll to latest version. 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 agable@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: chromium:1096045 Tbr: agable@chromium.org Change-Id: I0eb98e57a8228fbe87464e353420e67ee6b53373 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2255105Reviewed-by:
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1592585969-c70917dc3124c4b50e9e9ae9a9c8ca3f9c90b67e.profdata to chrome-win64-master-1592596428-41282d9701735ad20c4a3d4d4eabd6f8bdf0aa77.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 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:win64-chrome Tbr: jeffyoon@google.com,liaoyuke@google.com Change-Id: I82286ad65625ac9a7942dcb4a577c194ee5da01b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2255538Reviewed-by:
-
- 19 Jun, 2020 27 commits
-
-
Scott Lee authored
To produce the absolute path of an artifact file, TestFailure classes join results_directory, ArtifactsSubDirectory(), and artifact_filename. https://source.chromium.org/chromium/chromium/src/+/master:third_party/blink/tools/blinkpy/web_tests/models/test_failures.py;l=140-141;drc=32408e19204a7ffceebfe774d7e99f2041cf4338?originalUrl=https:%2F%2Fcs.chromium.org%2F ArtifactsSubDirectory() and artifact_filename are merged and stored as a key in result.artifacts. Therefore, to find the abs path of an artifact in a test failure, TestResultSink should use results_directory, not artifacts_directory. R=robertma@chromium.org CC=chanli@chromium.org,iannucci@chromium.org,nodir@chromium.org Change-Id: Ibf42bbdd24a5fa24229dc06409c072c828351173 Bug: 1084459 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2250515 Commit-Queue: Scott Lee <ddoman@chromium.org> Reviewed-by:
Rakib Hasan <rmhasan@google.com> Reviewed-by:
Robert Ma <robertma@chromium.org> Cr-Commit-Position: refs/heads/master@{#780512}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/d044efb50daa..d62d2aeab560 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 btolsch@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: btolsch@google.com Change-Id: Icba6ca950cdca427c8cabc41f61720b0c26b44b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2255163Reviewed-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@{#780511}
-
Wenyu Fu authored
Bug: 1089501 Change-Id: I5eb857fe8acb8008b05c3f52db066b832c2dbddf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2254700Reviewed-by:
Steven Holte <holte@chromium.org> Commit-Queue: Wenyu Fu <wenyufu@chromium.org> Cr-Commit-Position: refs/heads/master@{#780510}
-
Ali Juma authored
This adds additional EG test coverage for Safe Browsing, for scenarios identified by the test team when they were manually testing this feature. Change-Id: Id27ff75a0e92ba7501aeb250ab0112d8eb9a278b Bug: 1093510 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2246995 Commit-Queue: Ali Juma <ajuma@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#780509}
-
S. Ganesh authored
Bug: 1092936 Change-Id: If11473a8fb9893b528cf1a6a19c23ecfe96da815 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253018Reviewed-by:
Sorin Jianu <sorin@chromium.org> Commit-Queue: S. Ganesh <ganesh@chromium.org> Cr-Commit-Position: refs/heads/master@{#780508}
-
Peng Huang authored
Display problems are reported with Huawei and Honor devices with Mali GPU. The GPU driver version of them are < 19.0.0. The same problem can not be reproduced with other devices with Mali GPU with driver 19.0.0. So disable vulkan finch for Mali driver < 19.0.0. Bug: 1096222 Change-Id: Ib15fc865c4a173fc4413c4a4bbb3521bb4cc07cb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2251177 Auto-Submit: Peng Huang <penghuang@chromium.org> Reviewed-by:
Vasiliy Telezhnikov <vasilyt@chromium.org> Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Commit-Queue: Peng Huang <penghuang@chromium.org> Cr-Commit-Position: refs/heads/master@{#780507}
-
Tommy Li authored
Adds the kExpanded / kCollapsed accessibility header node data to section headers. Also fires off the kExpandedChanged event when this changes. Bug: 1078183, 1052522 Change-Id: Ie037ebede9003ebf486ec3e3ba0124e3b1b0057b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2247139 Commit-Queue: Tommy Li <tommycli@chromium.org> Reviewed-by:
Aaron Leventhal <aleventhal@chromium.org> Cr-Commit-Position: refs/heads/master@{#780506}
-
John Abd-El-Malek authored
Bug: 1097260 Change-Id: I28a9eed52f254364c8782f6b6fe95f1e637cbbcc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2255559 Commit-Queue: John Abd-El-Malek <jam@chromium.org> Commit-Queue: Clark DuVall <cduvall@chromium.org> Auto-Submit: John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#780505}
-
Andres Calderon Jaramillo authored
In the newly introduced VideoDecoder, we create a native buffer for video decoding on demand in the PlatformVideoFramePool. This buffer eventually makes it to the MailboxVideoFrameConverter in order to produce a SharedImage for the client. This CL ensures that the NativePixmap created in the PlatformVideoFramePool can be re-used in the MailboxVideoFrameConverter. Before this CL, we would call CreateNativePixmapFromHandle() unnecessarily when creating the SharedImage for a buffer. That's because we didn't propagate the GpuMemoryBufferId correctly from the PlatformVideoFramePool to the MailboxVideoFrameConverter and the check in [1] would fail. As a result, we would end up creating an additional DRM framebuffer which is unnecessary because the allocation in the PlatformVideoFramePool would have already created one. Thus, the video.MemCheck.h264_hw test would fail because of having created too many objects. To propagate the GpuMemoryBufferId correctly, we create a GpuMemoryBuffer VideoFrame in the PlatformVideoFramePool (instead of a dma-buf VideoFrame). That way, when MailboxVideoFrameConverter calls CreateGpuMemoryBufferHandle(), it gets a GpuMemoryBufferHandle with the same ID that PlatformVideoFramePool gets. Additionally, we make MailboxVideoFrameConverter use kPlatformVideoFramePoolClientId since that identifies the namespace of the GpuMemoryBufferIds in question. Note that for SCANOUT_VDA_WRITE buffers (which we use for video decoding), we end up creating a ClientNativePixmapOpaque when creating a GpuMemoryBufferImplNativePixmap. This is problematic because a ClientNativePixmapOpaque doesn't let us query the stride and we need to know it in order to create a GpuMemoryBuffer VideoFrame. Therefore, GpuMemoryBufferImplNativePixmap::stride() is changed so that it's not necessary to have a gfx::ClientNativePixmap to query the stride. Instead, we query the underlying NativePixmapHandle directly. For that same reason, we must introduce a workaround in the VideoFrameValidator: when we get a GMB VideoFrame, we cannot map it directly because ClientNativePixmapOpaque doesn't allow us to. Therefore, we extract the dma-buf FDs and use the regular dma-buf mapping path. [1] https://cs.chromium.org/chromium/src/gpu/ipc/service/gpu_memory_buffer_factory_native_pixmap.cc?l=152&rcl=d96e9f16ae852ec9dbd15bf17df3d440402413bb Bug: 1091450, 1093644 Test: video.MemCheck.h264_hw_switch, video.DecodeAccelVD.h264 on eve Change-Id: I3d60efa362b66bd2f01139296d4ed756c8777ef8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2233534 Commit-Queue: Andres Calderon Jaramillo <andrescj@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Daniele Castagna <dcastagna@chromium.org> Reviewed-by:
Hirokazu Honda <hiroh@chromium.org> Reviewed-by:
Chih-Yu Huang <akahuang@chromium.org> Cr-Commit-Position: refs/heads/master@{#780504}
-
Xi Han authored
In this CL, we add histogram: "Startup.Android.FeedContentFirstLoadedTime.Instant(.NoInstant)". It records the time duration from a cold start till the Feeds articles are first loaded on the StartSurface. The histograms are recorded as deferred tasks after startup only if StartSurface is shown when Chrome is launched from a cold start. A new interface method ContentChangedListener#onAddFinished() is added. It notifies FeedSurfaceMediator when the Feeds content is added to the RecyclerView. Bug: 1092931 Change-Id: Ice5fb669505f87e17af30daeecc6a2567205d504 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2240131 Commit-Queue: Xi Han <hanxi@chromium.org> Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Reviewed-by:
Carlos Knippschild <carlosk@chromium.org> Cr-Commit-Position: refs/heads/master@{#780503}
-
Joshua LeVasseur authored
If enabled, forward crashes to the system's crash handler, rather than processing them internally via Breakpad/Crashpad. This introduces a new GN argument, use_system_crash_handler, which enables forwarding to the system crash handler. By default it instead uses the builtin crash handling from Breakpad/Crashpad. Only supports the external_mojo processes. Also enable crash forwarding by default for the crash_uploader, since it doesn't include internal crash handling. Merge-With: eureka-internal/413496 Bug: internal b/156659049 Bug: internal b/157693574 Test: build Change-Id: Iced0d8ce02f7367ac8c9f2ef46d232f2d4b27732 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2222971Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Reviewed-by:
Kenneth MacKay <kmackay@chromium.org> Commit-Queue: Joshua LeVasseur <jlevasseur@chromium.org> Cr-Commit-Position: refs/heads/master@{#780502}
-
Jeffrey Cohen authored
This allows screenshots to be shared by looping back to the share sheet. A new JNI call to make a Uri from an arbitrary bitmap is also included. Bug: 1093372 Change-Id: I444634f5a19ac5a9b3b30c961127de7fe5cda72e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2243496 Commit-Queue: Jeffrey Cohen <jeffreycohen@chromium.org> Reviewed-by:
Tanya Gupta <tgupta@chromium.org> Reviewed-by:
David Trainor <dtrainor@chromium.org> Reviewed-by:
Kyle Milka <kmilka@chromium.org> Reviewed-by:
Kristi Park <kristipark@chromium.org> Cr-Commit-Position: refs/heads/master@{#780501}
-
Sergey Poromov authored
This delay may lead to a crash if WebContents in destroyed in between. Bug: 1097111 Change-Id: If77cc3ffc7866cf8ff0c0a8043549595724583fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253981Reviewed-by:
Dominique Fauteux-Chapleau <domfc@chromium.org> Commit-Queue: Sergey Poromov <poromov@chromium.org> Cr-Commit-Position: refs/heads/master@{#780500}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/50e7bb530903..e74db562ce8c 2020-06-19 brcui@microsoft.com Update Settings telemetry panel keys to fix Locations tab If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: chromium:1096745 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Ib260ab9a5936a5ca5da9d107f876a8446a1c5c96 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2255167Reviewed-by:
-
Christian Larson authored
Before completing the VideoCaptureDeviceMFWin::Init() function we should wait on MF_CAPTURE_ENGINE_INITIALIZED. The Capture Source is not fully constructed until the MF_CAPTURE_ENGINE_INITIALIZED event fires and calling methods before this time can cause unstable behavior. Bug: 1076730 Change-Id: I239077a4d9a599643b9e2c4ed0e26219a2dbb58f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2238879Reviewed-by:
Bruce Dawson <brucedawson@chromium.org> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Commit-Queue: Christian Larson <chrila@microsoft.com> Cr-Commit-Position: refs/heads/master@{#780498}
-
Maggie Chen authored
Optimization: If clipping is on, clip the overlay quad first. Then the occluding damage rect will intersect with the clipped overlay quad. Bug:1096097 Change-Id: I741cbd45f5ed11118185a69b03753fe6108563ca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2249597Reviewed-by:
Sunny Sachanandani <sunnyps@chromium.org> Commit-Queue: Maggie Chen <magchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#780497}
-
chromium-autoroll authored
https://chromium.googlesource.com/openscreen.git/+log/64150e03b378..f8393bee83f1 2020-06-19 jrw@google.com Made certificate_proto fuzzable. 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: Ieb60628a3d1071e1c11696d6eec15f984560b2a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2255164Reviewed-by:
-
Henrique Ferreiro authored
The main change in this CL is using the same cursor fallback selection machinery for both Aura/X11 and Ozone/X11. In addition to that: Cursor loading now uses cursor names, instead of a mix of cursor names and shapes (as introduced in [0]), given that all shapes can be loaded by Xcursor using their corresponding name. The CSS name is preferred over other options, relying on cursor themes usually linking known cursor names to cursors defined in the theme, or alternatively, picking alternative cursors as defined in a fallback table. It fixes the w-resize fallback changing it to left_side and replaces v-scroll and h-scroll (introduced in [1]) with all-scroll, as they are only available on Windows. [0]: https://crrev.com/c/1998353 [1]: https://crrev.com/c/1638924 Bug: 1029142 Change-Id: If50698d5305135be43cda4eeb48532d23816754f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2245704 Commit-Queue: Henrique Ferreiro <hferreiro@igalia.com> Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/master@{#780495}
-
Yi Xu authored
Change-Id: Ib9f3c32779cc410b010c6f3940fa75f2b16bb65f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2252696Reviewed-by:
Khushal <khushalsagar@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Commit-Queue: Yi Xu <yiyix@chromium.org> Cr-Commit-Position: refs/heads/master@{#780494}
-
Jose Dapena Paz authored
Bug: 819294 Change-Id: Ibf5b13cdccaa371b7f5972bf511aeb20ed1bf9c8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2252000 Commit-Queue: José Dapena Paz <jdapena@igalia.com> Reviewed-by:
Robert Kroeger <rjkroege@chromium.org> Cr-Commit-Position: refs/heads/master@{#780493}
-
Scott Lee authored
R=robertma@chromium.org CC=chanli@chromium.org,iannucci@chromium.org,nodir@chromium.org Bug: 1084459 Change-Id: I5927eae3308757027aab956dcc5086e7dc596983 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253140 Commit-Queue: Scott Lee <ddoman@chromium.org> Reviewed-by:
-
Chris Cunningham authored
Change-Id: Ib74ee08c23c077c729923397cae17c72811d83f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2255022 Auto-Submit: Chrome Cunningham <chcunningham@chromium.org> Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#780491}
-
Brian Geffon authored
When reading procfs files we shouldn't use the base file operations as they are annotated as MAY_BLOCK. This CL introduces an equivalent to base::ReadFileToString which doesn't have any blocking annotations. Bug: 1090623 Change-Id: I159f239caf1fe0613de9fdb92cd5fca687cb955b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2229153 Commit-Queue: Brian Geffon <bgeffon@chromium.org> Reviewed-by:
François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#780490}
-
Sergey Ulanov authored
baseaudiocontext-audioworklet.https.html is flaky due to dependency on FuchsiaMediaResourceProvider, which is currently not implemented in content_shell TBR=chonggu@google.com Bug: 1061226, 1096611 Change-Id: I79d642bc0353117dde81cfa566881ac2075c5156 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2255518Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> Cr-Commit-Position: refs/heads/master@{#780489}
-
Philip Rogers authored
Bug: 1097346 Change-Id: I09239e7647e182e1094ffed28aecd12c89f31fa8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2255218 Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#780488}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/1909f444..a9ea1674 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: I1b2ccd305c8f23771f56f18205b369db1e41c708 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2254881Reviewed-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@{#780487}
-
Aleks Totic authored
Algorithm helpers that distribute widths to columns. Bug: 958381 Change-Id: I2a876e81c8caa6ef4743f3c4ae5fd4f45f6fec15 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2242129Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Aleks Totic <atotic@chromium.org> Cr-Commit-Position: refs/heads/master@{#780486}
-
