- 07 Dec, 2020 40 commits
-
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/7c84426d2abe..7bcd79eccf28 2020-12-07 sugoi@google.com Fix some minor tracing mistakes 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: I110124463bc7ec59f04b9feedfbeeba0fe2e4b52 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577432Reviewed-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@{#834221}
-
Leo Lai authored
We are deprecating tpm-related APIs by cryptohome. BUG=b:172748724 TEST=build ok. Change-Id: Ieda901dfcc6908e83e4e694ad77cfe83de8cae9b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569197Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Commit-Queue: Leo Lai <cylai@google.com> Cr-Commit-Position: refs/heads/master@{#834220}
-
Leo Lai authored
There are several places where error is put as "erorr" by mistake. Bug: None Change-Id: I871710965f2162e8ed678b6cd1463b1b88382e80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570832Reviewed-by:
Brandon Tolsch <btolsch@chromium.org> Reviewed-by:
Richard Knoll <knollr@chromium.org> Reviewed-by:
Bence Béky <bnc@chromium.org> Reviewed-by:
Ben Wells <benwells@chromium.org> Commit-Queue: Leo Lai <cylai@google.com> Cr-Commit-Position: refs/heads/master@{#834219}
-
Czirkos Zoltan authored
When printing, the footer template for showing page number is: <span class='pageNumber'></span>/<span class='totalPages'></span> When the footer intersects the bottom margin, it is hidden. However, previously only the two spans were hidden, and the slash character stayed at the bottom of the page. This patch fixes that by hiding the div.text containers instead, whenever they intersect the margins. Bug: 1069445 Change-Id: Ia41d58fe146188ad4819075319f0655240e65908 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2144141Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Commit-Queue: Denis Kuznetsov [CET] <antrim@chromium.org> Cr-Commit-Position: refs/heads/master@{#834218}
-
Maksim Ivanov authored
Fix use-after-move (potential) bugs found by the "bugprone-use-after-move" clang-tidy check. Also add a new std::move() call in this file, to optimize passing one of the arguments. Bug: 1122844 Change-Id: I0526ff7b4b8b4e9c080cb56b54b020c31f240492 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2563824 Commit-Queue: Wez <wez@chromium.org> Reviewed-by:
Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#834217}
-
Rune Lillesveen authored
We have three instances of using AllowMarkStyleDirtyFromRecalcScope to allow marking elements style-dirty during style recalc. One of them is for text input elements where we mark the InnerEditor() element dirty when the input element gets new style. We typically don't mark style during UpdateStyleAndLayoutTreeForContainer(), which is called for container query updates during layout. This CL adds a test to check that it still works. Bug: 1146097 Change-Id: I432308bc96cd938e22ea424975a7c19a35aaf6a3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2573139 Commit-Queue: Rune Lillesveen <futhark@chromium.org> Reviewed-by:
Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#834216}
-
Vasiliy Telezhnikov authored
This CL adds support for --tint-composited-content command line flag that helps to see what content was composited and what went to overlays. Change-Id: I71e2d72b87be9d37ae0787482a20b531483802f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575827Reviewed-by:
Bo <boliu@chromium.org> Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org> Cr-Commit-Position: refs/heads/master@{#834215}
-
Hans Wennborg authored
See http://lists.llvm.org/pipermail/llvm-dev/2020-December/147175.html Bug: none Change-Id: Ifd6abe11b833961d9ff25bdd6e9d3315523cd95f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577360Reviewed-by:
Nico Weber <thakis@chromium.org> Commit-Queue: Hans Wennborg <hans@chromium.org> Cr-Commit-Position: refs/heads/master@{#834214}
-
Greg Thompson authored
BUG=1156091 TBR=shimazu@chromium.org Change-Id: I35d67c44693c0e3e9da3371a1b1a657f978c3d55 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574950Reviewed-by:
Greg Thompson <grt@chromium.org> Commit-Queue: Greg Thompson <grt@chromium.org> Cr-Commit-Position: refs/heads/master@{#834213}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/src/third_party/freetype2.git/+log/9f94d8533cef..272ae5ee2ab1 2020-12-07 wl@gnu.org * src/*: More fixes for using a '\n' in `FT_TRACE` and `FT_ERROR`. 2020-12-07 wl@gnu.org */*: s/FT_LOGGING/FT_DEBUG_LOGGING/. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/freetype-chromium Please CC bungeman@google.com,drott@google.com,thestig@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:linux_chromium_msan_rel_ng;luci.chromium.try:linux-blink-rel;luci.chromium.try:mac10.12-blink-rel;luci.chromium.try:win10-blink-rel;luci.chromium.try:win7-blink-rel Tbr: bungeman@google.com,drott@google.com,thestig@google.com Change-Id: I64ad85f729dd9849ba2d9988c129eb53b2d99cc6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575505Reviewed-by:
chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Reviewed-by:
Ben Wagner <bungeman@chromium.org> Commit-Queue: Ben Wagner <bungeman@chromium.org> Cr-Commit-Position: refs/heads/master@{#834212}
-
Jan Krcal authored
This CL changes the way profile picker layout changes when moving between the WebUI screens and the Gaia sign-in screen. Instead of destroying everything and creating new WebViews, we just swap the WebContents and swap the visibility of the native toolbar. This results in a much smoother UX, especially when moving back and forth between the first profile creation screen and the Gaia sign-in screen. The performance cost for this is keeping two WebContents in memory for the lifetime of the signed-in profile creation, which is acceptable on desktop. This CL does not actually create any content for the toolbar, this will come in the next CL. The actual toolbar view is created in this CL and its visibility is toggled in order to allow browser tests to properly detect the layout change (the previous way does not work after this change). Bug: 1126913 Change-Id: I5db63f4e73d37797d3b59c27f3454130ed12babc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2571096 Commit-Queue: Jan Krcal <jkrcal@chromium.org> Auto-Submit: Jan Krcal <jkrcal@chromium.org> Reviewed-by:
David Roger <droger@chromium.org> Cr-Commit-Position: refs/heads/master@{#834211}
-
Leo Lai authored
We are deprecating GetTpmStatus by cryptohome. Also, dropping the status of boot lockbox because it isn't supported by cryptohome anymore. BUG=b:172748724 TEST=browser_tests. Change-Id: Iefe7060ba64aec11f12fce188cb0f1c146124b6b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569431 Commit-Queue: Leo Lai <cylai@google.com> Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Cr-Commit-Position: refs/heads/master@{#834210}
-
Justin DeWitt authored
Bug: 1155360 Change-Id: Iaf0af878775f72b305fcd5c6fa0cbabcbab9cd36 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575425Reviewed-by:
Brandon Wylie <wylieb@chromium.org> Reviewed-by:
Filip Gorski <fgorski@chromium.org> Commit-Queue: Filip Gorski <fgorski@chromium.org> Auto-Submit: Justin DeWitt <dewittj@chromium.org> Cr-Commit-Position: refs/heads/master@{#834209}
-
Dominik Röttsches authored
Upgrade underline to non-simple when a thickness is set. Without this change, only modifying the text-decoration-thickness property was disregarded when no other properties are set, as the hasSimpleUnderline() optimization was used in this case in ComputedStyle. Add a non-match type WPT test to ensure that a difference is seen when two different thicknesses are set. Fixed: 1154537 Change-Id: Id0413fc3f44e154b509e21b5f857f13f8d80a8f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577457Reviewed-by:
Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Dominik Röttsches <drott@chromium.org> Auto-Submit: Dominik Röttsches <drott@chromium.org> Cr-Commit-Position: refs/heads/master@{#834208}
-
Leo Lai authored
we are migrating tpm status calls to TpmManagerClient. BUG=b:172748724 TEST=build ok. Change-Id: I83e32ab20bf367d4934e7b96fc30ab4c2fc5d4b5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569196Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Commit-Queue: Leo Lai <cylai@google.com> Cr-Commit-Position: refs/heads/master@{#834207}
-
Rune Lillesveen authored
If the style recalc root is neither the root element, nor body, we can skip propagation from root/body. Skipping that early is more important when you have many containers for container queries which means RecalcStyle will be called multiple times during layout. TEST=external/wpt/css/css-writing-modes/ Bug: 1146097 Change-Id: I12514f54cec3400f028eb7efbb5ec34ce241d672 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574280Reviewed-by:
Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#834206}
-
Yunke Zhou authored
Replace cr-dialog with oobe-help-dialog so shelf buttons are disabled properly when dialog is opened. Bug: 1119338 Change-Id: Iebeff98b7b451c17f2679d69ce8819c5e259d418 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2563481Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Commit-Queue: Yunke Zhou <yunkez@google.com> Cr-Commit-Position: refs/heads/master@{#834205}
-
Aaron Leventhal authored
There doesn't seem to be a good reason for this special case, and the condition is in an odd place. If a list marker is inside of an ignored/invisible subtree, it is still marked ignored/invisible. Bug: None Change-Id: I5f3b5b9f1c253658201e554b27e13f3178223bd1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2572936Reviewed-by:
Alice Boxhall <aboxhall@chromium.org> Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Cr-Commit-Position: refs/heads/master@{#834204}
-
Richard Stotz authored
The error message points to win_cross.md, as can be seen in the script https://source.chromium.org/chromium/chromium/tools/depot_tools/+/master:win_toolchain/get_toolchain_if_necessary.py;l=531 Bug: none Change-Id: I562653b401ec039db4f8a83b4bc38e11f8d4d5db Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577459Reviewed-by:
Mike West <mkwst@chromium.org> Commit-Queue: Richard Stotz <rstz@chromium.org> Cr-Commit-Position: refs/heads/master@{#834203}
-
Oriol Brufau authored
Before this patch, setting a value to a property already in the list of declarations, would just update its value, without reordering. The problem was that the order is important when there is a mix of logical and physical properties: el.style.paddingTop = "1px"; el.style.paddingBlockStart = "2px"; el.style.cssText; // "padding-top: 1px; padding-block-start: 2px" el.style.paddingTop = "3px"; el.style.cssText; // "padding-top: 3px; padding-block-start: 2px" getComputedStyle(el).paddingTop; // "2px" -- no effect! Therefore, this patch implements this part of the spec: > If there are CSS declarations in declarations whose property name is > in the same logical property group as property, but has a different > mapping logic, target declaration must be at an index after all of > those CSS declarations. Spec: https://drafts.csswg.org/cssom/#set-a-css-declaration Bug: 1155858 TEST=external/wpt/css/cssom/cssstyledeclaration-setter-logical.html Change-Id: Idb89661c6740dd1bbe3948b58475900e1a353d2f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575081 Commit-Queue: Oriol Brufau <obrufau@igalia.com> Reviewed-by:
Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#834202}
-
Andy Paicu authored
This is a somewhat speculative fix for the crash in the linked bug. The working hypothesis is that an Android infobar might be calling into `ReasonForUsingQuietUi` after some IPC has already taken place and another event has reset the `current_request_ui_to_use_` member. Either way a more robust `ReasonForUsingQuietUi` should be a net gain. Bug: 1104881 Change-Id: I69825216892c969e968704e97ba162c52cbc4efb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569657Reviewed-by:
Illia Klimov <elklm@chromium.org> Commit-Queue: Kamila Hasanbega <hkamila@chromium.org> Cr-Commit-Position: refs/heads/master@{#834201}
-
Oriol Brufau authored
In order to have proper CSSOM support for logical properties, we will need to determine whether two properties belong to the same logical property group but with a different mapping logic. Before this patch, we only knew the physical properties belonging to the same logical property group as a given logical property. But given a physical property, we didn't know if there were logical properties that could map to it. Therefore this patch adds: - CSSProperty::IsInLogicalPropertyGroup, which returns true for logical properties and for their corresponding physical ones. - CSSProperty::IsInSameLogicalPropertyGroupWithDifferentMappingLogic which checks what the name says, given a CSSPropertyID. - CSSDirectionAwareResolver::LogicalMapping and PhysicalMapping, representing the properties of a logical property group with a flow- relative or a physical mapping logic, respectively. In css_properties.json5, the terminology becomes closer to the spec: - direction_aware_options becomes logical_property_group, and physical properties have it too. - direction_aware_options.physical_group becomes logical_property_group.name - direction_aware_options.resolver accepts physical axis and box sides (horizontal, vertical, top, right, bottom, left). This patch should have no effect in practice. Bug: 1155858 Change-Id: I1a01e80a2405315d9caaf057e6bfd465f3615cce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574940 Commit-Queue: Oriol Brufau <obrufau@igalia.com> Reviewed-by:
Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#834200}
-
Nico Weber authored
I couldn't find the toolchain guarantees doc the other day, so as a first step link to it here. We should probably reorganize the docs a bit -- the perf regression bit in updating_clang.md looks like it belongs in the sheriffing doc, and the "which files belong in the main package" should arguably move to the toolchain guarantees doc. Bug: none Change-Id: I6b9018748c47f5942a970e8bcc76bcf1107784e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576583Reviewed-by:
Hans Wennborg <hans@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#834199}
-
Wolfgang Beyer authored
This CL adds a test which ensures that a `document.write()` when the document is still open does not trigger sending a `Page.documentOpened` CDP event. `Page.documentOpened` CL: https://crrev.com/c/2498482 Design Doc: http://doc/1l-XzjFMdASjRzX4-vMxOoK-MXoxY5uhCe0GNfDsXeDo Change-Id: Ibbe7d539db6ee85168c99972a8e2779dcc982b03 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567007Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Commit-Queue: Wolfgang Beyer <wolfi@chromium.org> Cr-Commit-Position: refs/heads/master@{#834198}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/393159147685..ea969d287bfe 2020-12-07 perkj@webrtc.org Reland Addd class InterArrivalDelta to goog_cc 2020-12-07 akonradi@google.com Remove nesting of Naggy/Strict/NiceMock 2020-12-06 jonaso@webrtc.org Add field trial WebRTC-AllowMACBasedIPv6 2020-12-06 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision a04842f6..29886952 (833885:834077) 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: I0a9b9c175603bd6c786d3fcda7d777e8834bab57 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577423Reviewed-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@{#834197}
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1607309475-be47e6675d78a40c2743c701a82c248ac3d955c3.profdata to chrome-win64-master-1607331580-48b245bff1ba8e6eb069e7a15838de53304e6a37.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: I077de263674d24a9f1b90b1f1d82b2978b5bfedf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575508Reviewed-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@{#834196}
-
Hayato Ito authored
This is a follow-up to https://crrev.com/c/2560526. This CL changes the implementation of WebBundle subresource loading from "renderer oriented" to "network service oriented". Before this CL, a renderer parses a WebBundle and serves a subresource from there directly. After this CL, they are done in the Network Service, instead of a renderer. The motivation we're changing our design is "we should honor CORB [1]". A renderer shouldn't have cross-origin data in their memory. See the design doc [2] for details. Note this CL removes blink/renderer/platform/loader/fetch/url_loader/web_bundle_subresource_loader_test.cc, which was already moved to services/network/web_bundle_url_loader_factory_unittest.cc in a previous CL. - [1]: https://source.chromium.org/chromium/chromium/src/+/master:services/network/cross_origin_read_blocking_explainer.md - [2]: https://docs.google.com/document/d/1_AqUBS4Gr45MPPtXGTUl7Q0DMIEw2zUeWO0zo6Sj0z4/edit Bug: 1082020 Change-Id: I78b0e81b573f735c84334a4cd2271c248609c2e8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2564924 Commit-Queue: Hayato Ito <hayato@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Kunihiko Sakamoto <ksakamoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#834195}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1607320769-d0ad4f5a17a630b334cdaa2bc2220f2b7c7c5cc2.profdata to chrome-mac-master-1607341806-857507b5a91b3ce5824fe454e7d197a8b05189bf.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 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:mac-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: Ia8a57c37d2860aa5e5014759c9b554e31e5400cd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577427Reviewed-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@{#834194}
-
Przemek Pietrzkiewicz authored
This patch implements chromium.cast.DataReset in CastRunner. Upon request to reset persistent state, we: - Block launching new components in the main context - Move all data under /cache to a staging directory that is deleted upon next startup of CastRunner Bug: 1146474, 1146480 Test: run_cast_runner_integration_tests Test: verified manually on device that a file in the cache directory of CastRunner is gone after DataReset and reboot Change-Id: I713133540302a1c0535c778e5957e2c87e0f669b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2537840 Commit-Queue: Przemek Pietrzkiewicz <ppi@google.com> Reviewed-by:
Wez <wez@chromium.org> Reviewed-by:
Benjamin Lerman <qsr@chromium.org> Cr-Commit-Position: refs/heads/master@{#834193}
-
chromium-autoroll authored
Roll Chrome Linux PGO profile from chrome-linux-master-1607320769-89cdddd8995ad3be12a676e570aae350fc15988d.profdata to chrome-linux-master-1607341806-34092e6e948e6283aae1770f567faca0b14a9512.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: Ica66cc4562dd9a92eb97e1f3fe50dab799702a01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577429Reviewed-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@{#834192}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/b36ad7e1d111..698d1c0a0acb 2020-12-07 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS. 2020-12-07 sigurds@chromium.org Don't generate types for deprecated Console domain 2020-12-07 tvanderlippe@chromium.org Upgrade third_party/acorn to 8.0.4 2020-12-07 jacktfranklin@chromium.org [Dark Mode]: small CSS files 2020-12-07 sigurds@chromium.org Remove twin definitions from ConsoleModel 2020-12-07 wolfi@chromium.org Update link url 2020-12-07 jacktfranklin@chromium.org [Dark mode] disable patching for customPreviewComponent.css 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:1152082,chromium:1152736,chromium:1153099 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Id13ed33a6517131b32ef1e12d080e2ac9a55f592 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576427Reviewed-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@{#834191}
-
Side Yilmaz authored
This CL gets Profile from WebContents and pass it through the NavigationSheetCoordinator. Bug: 1048632 Change-Id: I5c9f3aca1c9b840f810eb780fc8d05be4be9df2a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569738Reviewed-by:
Jinsuk Kim <jinsukkim@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Side YILMAZ <sideyilmaz@chromium.org> Cr-Commit-Position: refs/heads/master@{#834190}
-
Ali Tofigh authored
The std::map in StatsResponse::Report is only used to iterate though the elements. Profiling on Mac shows that a replacing the std::map with a std::vector shaves off about 40% CPU time spent in StatsResponse::Report in some common video conferencing scenarios. Bug: 1156090 Change-Id: I3070000bb534deb18fb0fd9b18b83a947fae64a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576240Reviewed-by:
Henrik Boström <hbos@chromium.org> Commit-Queue: Ali Tofigh <alito@chromium.org> Cr-Commit-Position: refs/heads/master@{#834189}
-
Pavol Marko authored
GetDeviceAttributeUpdatePermission resolves the current user by OAuth token and then checks if that user may change the device's attributes. This is only sensible for manual enrollment where a user has actually authenticated and we have an OAuth token for the user. For enrollment modes without explicit user auth, such as attestation-based enrollment or enrollment-token-based enrollment, the enrolling user is not known so this check is not possible. For now, assume that device attributes should not be changed in this, as there is no way to find out if the enrolling user is permitted to change them. Bug: 942013 Change-Id: I5f7e08ca2af223d0dbcac3839c6eb2b2f45e62b2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2566820 Commit-Queue: Pavol Marko <pmarko@chromium.org> Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Cr-Commit-Position: refs/heads/master@{#834188}
-
Morten Stenshorne authored
TBR=foolip@chromium.org Bug: 1154574 Change-Id: Ib632013e53de9b69d579890fe0c7b6f3dccb6f8e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577200Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#834187}
-
Victor Vianna authored
The test has been disabled for >2 years. Let's to try to re-enable it. Bug: 860200 Change-Id: Ia425f68d99f3e056226d367f66ab03ac85a13e4b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574702 Commit-Queue: Jan Krcal <jkrcal@chromium.org> Auto-Submit: Victor Vianna <victorvianna@google.com> Reviewed-by:
Jan Krcal <jkrcal@chromium.org> Cr-Commit-Position: refs/heads/master@{#834186}
-
Mikhail Khokhlov authored
https://android.googlesource.com/platform/external/perfetto.git/+log/0fdb2247e82e..c56ea91f6bd1 2020-12-04 primiano@google.com Merge "service: Add MaybeSaveTraceForBugreport()" Includes empty implementation of SaveTraceForBugreport. Change-Id: Ia351be67f1ad24c87ee9b2f8ee56c0916bf39450 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574744Reviewed-by:
Eric Seckler <eseckler@chromium.org> Reviewed-by:
Primiano Tucci <primiano@chromium.org> Commit-Queue: Mikhail Khokhlov <khokhlov@google.com> Cr-Commit-Position: refs/heads/master@{#834185}
-
Victor Vianna authored
There's been a spike of flakes on this bot following 2020-12-03, let's disable the test. https://findit-for-me.appspot.com/p/chromium/flake-portal/flakes/occurrences?key=ag9zfmZpbmRpdC1mb3ItbWVyVgsSBUZsYWtlIktjaHJvbWl1bUBzeW5jX2ludGVncmF0aW9uX3Rlc3RzQFR3b0NsaWVudFdlYkFwcHNCTU9TeW5jVGVzdC5Vbmluc3RhbGxTeW5jZWQM Bug: 1108172 Change-Id: I3c142419ee690165bde93c9d84fe94a4225a18f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577358 Commit-Queue: Jan Krcal <jkrcal@chromium.org> Auto-Submit: Victor Vianna <victorvianna@google.com> Reviewed-by:
Jan Krcal <jkrcal@chromium.org> Cr-Commit-Position: refs/heads/master@{#834184}
-
Robbie Gibson authored
The new ThumbStripMediator handles observing the regular/incognito WebStateLists to add the ViewRevealingVerticalPanHandler as a scrollViewProxy observer. This allows it to get scroll delegate callbacks from the active webstate. This CL also slightly fixes the BVC thumb strip hide/reveal behavior to correctly change the scroll view's content insets as well as the content offset. Bug: 1094335 Change-Id: I006a3e72a06b1e327ce0984cf84bc69c2e95fe7a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2563556Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Reviewed-by:
Chris Lu <thegreenfrog@chromium.org> Commit-Queue: Robbie Gibson <rkgibson@google.com> Cr-Commit-Position: refs/heads/master@{#834183}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/71bbb3b22e98..cf023b3a8cd1 2020-12-07 angle-autoroll@skia-public.iam.gserviceaccount.com Roll SwiftShader from bae138de13ac to 7c84426d2abe (8 revisions) 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 geofflang@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: geofflang@google.com Change-Id: Ie8cf67c182edc94b1da57edd08c35b1f1229bc26 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577418Reviewed-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@{#834182}
-