- 28 Feb, 2020 40 commits
-
-
Kent Tamura authored
When the location of a box is determined, we should update scrollbar positions by calling SetLocationAndUpdateOverflowControlsIfNeeded() instead of SetLocation(). Bug: 1056936 Change-Id: I173d825c123981d55acba2575d673eef0d73a27b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079772 Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#745397}
-
Jose Lopes authored
This is a repeating callback because it is run as part of an event handler, which can be fired repeatedly: * https://cs.chromium.org/chromium/src/chrome/renderer/media/cast_transport_ipc.cc?rcl=5703e03dce1a4499c9885d2a42342acfe831c36c&l=118 The event handler is called from an IPC handler: * https://cs.chromium.org/chromium/src/chrome/renderer/media/cast_ipc_dispatcher.cc?rcl=5703e03dce1a4499c9885d2a42342acfe831c36c&l=82 registered in: * https://cs.chromium.org/chromium/src/chrome/renderer/media/cast_ipc_dispatcher.cc?rcl=5703e03dce1a4499c9885d2a42342acfe831c36c&l=52 This is part of the base::Callback migration. Context: https://cs.chromium.org/chromium/src/docs/callback.md?rcl=9fcc3764aea8f97e9f6de4a9ee61d554e67edcda&l=40 Bug: 714018 Change-Id: I7986567aa2191c1566d82b55df7d74a89699786a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2073879 Commit-Queue: Jose Lopes <jabolopes@google.com> Reviewed-by:
danakj <danakj@chromium.org> Reviewed-by:
Xiaohan Wang <xhwang@chromium.org> Cr-Commit-Position: refs/heads/master@{#745396}
-
Eriko Kurimoto authored
This CL adds tests to static/dynamic import of non-existing scripts modules shared workers. Without 'static import on classic worker' test, all the tests corresponding to dedicated-worker-import-failure.html have added. 'static import on classic worker' is treated as parse error, and the way to handle parse error differs from fetching non-existing or invalid scripts which are tested in this test file. Therefore, I will add WPTs for parse error in separated files by the following CLs. Change-Id: I1f4555f2ea8597f0c0fc197494f0ba5d1510db75 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2071466 Commit-Queue: Eriko Kurimoto <elkurin@google.com> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#745395}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/b5eeba1bb3d7..63288e382aeb git log b5eeba1bb3d7..63288e382aeb --date=short --first-parent --format='%ad %ae %s' 2020-02-28 phoglund@webrtc.org Whitespace change to kick bots. 2020-02-28 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision dcd1a26c..45a3ae97 (745220:745356) Created with: gclient setdep -r src/third_party/webrtc@63288e382aeb 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/+/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: Iad1e7b7d5f833869d4a28a46d724c89f934d172f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080045Reviewed-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@{#745394}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/glslang/+log/07e1a0a67aee..f13d38f3cd3c git log 07e1a0a67aee..f13d38f3cd3c --date=short --first-parent --format='%ad %ae %s' 2020-02-28 johnkslang@users.noreply.github.com Merge pull request #2092 from corporateshark/master Created with: gclient setdep -r src/third_party/glslang/src@f13d38f3cd3c If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/glslang-chromium-autoroll Please CC radial-bots+chrome-roll@google.com,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/+/master/autoroll/README.md Bug: None Tbr: radial-bots+chrome-roll@google.com,geofflang@google.com Change-Id: Icdb00cc1e6601f99232cb03ab80754867c9cdea0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080042Reviewed-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@{#745393}
-
Fredrik Söderquist authored
marker-path-001-ref.svg: The ref did not include the contribution from the viewBox on the <marker> in some case. Adjust the markerWidth/Height to make the 'viewBox' contribution a scale-factor of one. Set 'overflow' to 'visible' to avoid clipping artifacts. marker-path-022-ref.svg: marker-path-023-ref.svg: Renders the markers twice - both on the shape itself and as "additional" reference markers. Drop the markers from the shape. Update the expectations for wpt/svg/struct/reftests/use-inheritance-001.svg wpt/svg/painting/reftests/marker-path-022.svg and wpt/svg/painting/reftests/marker-path-023.svg Bug: 674797, 785246, 1056492 Change-Id: I164fd7a826f8efdb5c5b5cbc486b81906d32a254 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2077719Reviewed-by:
Stephen Chenney <schenney@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#745392}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/dea22b17966e..4135db4c51d3 Created with: gclient setdep -r src-internal@4135db4c51d3 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 jbudorick@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: jbudorick@google.com Change-Id: Ia87780d4b988a2862f47d9c839f3319304992613 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080040Reviewed-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@{#745391}
-
Andy Paicu authored
This should help new folks get started with making changes in the content settings pages. Change-Id: I30e695536cd96a64198379c6b4ccbaf8562f2f19 No-Presubmit: true No-Tree-Checks: true No-Try: true Change-Id: I30e695536cd96a64198379c6b4ccbaf8562f2f19 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078577 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Reviewed-by:
Andy Paicu <andypaicu@chromium.org> Reviewed-by:
Kamila Hasanbega <hkamila@chromium.org> Cr-Commit-Position: refs/heads/master@{#745390}
-
Yuzu Saijo authored
This CL is based on Dave's CL (https://chromium-review.googlesource.com/c/chromium/src/+/2025567). This CL introduces a PageBroadcast mojom interface. Freezing is a good example which has to happen on the page/RenderViewHost granularity rather than LocalMainFrame/Frame. (Freezing mojo CL: https://chromium-review.googlesource.com/c/chromium/src/+/1999899) This CL will allow us to have page-level mojo messages. BUG=1046424 Change-Id: If6d660eeacc7dfec4175d2de8be7e887a3519209 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2043412 Commit-Queue: Yuzu Saijo <yuzus@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Alexander Timin <altimin@chromium.org> Reviewed-by:
danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#745389}
-
Andrew MacPherson authored
Remove blink::MultiChannelResampler and replace it with the blink::MediaMultiChannelResampler. Bug: 1033408 Change-Id: Ia90022fbf186cf85d1fe5f589819774e63c87746 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975713Reviewed-by:
Hongchan Choi <hongchan@chromium.org> Reviewed-by:
Raymond Toy <rtoy@chromium.org> Commit-Queue: Andrew MacPherson <andrew.macpherson@soundtrap.com> Cr-Commit-Position: refs/heads/master@{#745388}
-
Adam Rice authored
The tests http/tests/uri/escaped-entity.html http/tests/uri/utf8-path.html virtual/text-antialias/international/001.html http/tests/eventsource/eventsource-bad-mime-type.html are flakily timing out on Fuchsia. Mark them in TestExpectations. BUG=1056022 Change-Id: I9991dab28263cf27b48a739454240c41a7e4c17c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078378Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Adam Rice <ricea@chromium.org> Cr-Commit-Position: refs/heads/master@{#745387}
-
Mario Sanchez Prada authored
Following the discussion in chromium-mojo and platform-architecture-dev, we're proposing to add this script to the chromium repository so that external repositories that still depend on the old mojo types (e.g. Android's and ChromeOS's libchrome repos) have a simple and maintained way to downgrade Chromium's .mojom files to the old syntax, while they can't support the new one. This CL includes a new mojom_types_downgrader.py script that can be integrates with those external builds requiring it, plus the necessary unit tests to guarantee that the downgraded files can still be parsed correctly by the bindings generator (i.e. mojom_bindings_generator.py). For extra context, see the relevant discussion in the chromium-mojo ML: https://groups.google.com/a/chromium.org/d/msg/chromium-mojo/BRK0Xeu7bgQ/z00hkpaGEQAJ Bug: 1035484 Change-Id: I4c92345e82a188052b06efce9a1bc749d561cca1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2041759 Commit-Queue: Mario Sanchez Prada <mario@igalia.com> Reviewed-by:
Ken Rockot <rockot@google.com> Cr-Commit-Position: refs/heads/master@{#745386}
-
Colin Blundell authored
This file was deprecated by a copy added to //base in https://chromium-review.googlesource.com/c/chromium/src/+/2071257, and the internal callers of it have now been ported. I verified that no commits have been made to the file since the above CL. Bug: 1031465 Change-Id: Ib14e63a4d4030914227d682141681d6cf838e450 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078534 Commit-Queue: Colin Blundell <blundell@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Cr-Commit-Position: refs/heads/master@{#745385}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/52037e8ecce6..0a3900fb33dc git log 52037e8ecce6..0a3900fb33dc --date=short --first-parent --format='%ad %ae %s' 2020-02-28 skia-recreate-skps@skia-swarming-bots.iam.gserviceaccount.com Update Go Deps 2020-02-28 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). Created with: gclient setdep -r src/third_party/skia@0a3900fb33dc 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 jlavrova@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/+/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 Bug: None Tbr: jlavrova@google.com Change-Id: I54e18d21ce2091112639876c7918ab5b28fa5112 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080037Reviewed-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@{#745384}
-
Kei Nakashima authored
Added size, Capacity, isEmpty, front, back, insert and erase for NewLinkedHashSet. NewLinkedHashSet is a new implementation of LinkedHashSet. LinkedHashSet maintains a linked list to iterate all entries in the order in which they are inserted. We replace it with NewLinkedHashSet for the following purposes: To simplify moving of the backing store. To implement LinkedHashSet on top of existing WTF primitives. In NewLinkedHashSet, the linked list is implementing in a vector (with links begin indices instead of pointers). Design Doc for NewLinkedHashSet is here: https://docs.google.com/document/d/1ts2L8XJcGQYlxdVerVBp8_625h6ky7RNGw21AqMJ9Z0/edit?usp=sharing Change-Id: I327143051ff1f2a1cd36cc9f3ff26923267c5694 Bug-Id: 992506 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2065815 Commit-Queue: Kei Nakashima <keinakashima@google.com> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Bartek Nowierski <bartekn@chromium.org> Reviewed-by:
Keishi Hattori <keishi@chromium.org> Reviewed-by:
Yuki Shiino <yukishiino@chromium.org> Auto-Submit: Kei Nakashima <keinakashima@google.com> Cr-Commit-Position: refs/heads/master@{#745383}
-
Rune Lillesveen authored
Style attribute changes could affect style matching of other elements than the one that gets its style attribute modified because of selectors which have a style attribute selector in the non-right-most compound. For instance: [style] + div In this case the div will be invalidated by an invalidation set for the style attribute scheduled in StyleEngine::AttributeChangedForElement(). This method was not invoked for all variants of style attribute modifications. In particular setting the text for Element.style. This CL centralizes the invalidation handling to cover all cases. Bug: 1056151 Change-Id: Iceb70c284e2bb6b209a4243d61f941670eab323e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078532Reviewed-by:
Xiaocheng Hu <xiaochengh@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#745382}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/590b36126628..dea22b17966e Created with: gclient setdep -r src-internal@dea22b17966e 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 jbudorick@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: jbudorick@google.com Change-Id: I29cddd41a10c6010e68889ad7842a8056efb17f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080033Reviewed-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@{#745381}
-
Sorin Jianu authored
R=ganesh Bug: 1042224 Change-Id: If67b19f36cbbca636f6084eafd2d1f1eae285d09 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079866Reviewed-by:
S. Ganesh <ganesh@chromium.org> Commit-Queue: Sorin Jianu <sorin@chromium.org> Cr-Commit-Position: refs/heads/master@{#745380}
-
Cathy Li authored
This is a reland of 21245a70 Original change's description: > [xsurface]: Update SurfaceAdapter to SurfaceRenderer and spec > > Change-Id: Ib77234174ece4facb35596808fd964a18db04311 > Bug: 1054944 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2048409 > Commit-Queue: Cathy Li <chili@chromium.org> > Reviewed-by: Justin DeWitt <dewittj@chromium.org> > Reviewed-by: Theresa <twellington@chromium.org> > Cr-Commit-Position: refs/heads/master@{#744352} Bug: 1054944 Change-Id: Id83ba6d62046eb6426a4ec15693f39dffff8329b TBR: twellington@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079938 Commit-Queue: Cathy Li <chili@chromium.org> Reviewed-by:
Justin DeWitt <dewittj@chromium.org> Cr-Commit-Position: refs/heads/master@{#745379}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/23d978da38f9..52037e8ecce6 git log 23d978da38f9..52037e8ecce6 --date=short --first-parent --format='%ad %ae %s' 2020-02-28 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader 4d40271e3f09..05f5e0b34ac8 (3 commits) 2020-02-28 herb@google.com Add LLVM floor code for SkVM Created with: gclient setdep -r src/third_party/skia@52037e8ecce6 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 jlavrova@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/+/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 Bug: None Tbr: jlavrova@google.com Change-Id: Ide1092bee040d778fa22938ecca60f256ee23607 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2080031Reviewed-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@{#745378}
-
Joel Hockey authored
Change-Id: I4d37b89eba0b26ac1e801e42edfda08cfb739629 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2076638 Auto-Submit: Joel Hockey <joelhockey@chromium.org> Reviewed-by:
Ben Wells <benwells@chromium.org> Commit-Queue: Joel Hockey <joelhockey@chromium.org> Cr-Commit-Position: refs/heads/master@{#745377}
-
danielng authored
This is a flag for Crostini mic setting changes to be put behind. The flag is specifically for the Crostini mic aspect of phase 1 (see PRD attached to the bug). Bug: 1016193 Change-Id: I89d03cbcbc4497ea6e30c131e452adf6e104010e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079711 Commit-Queue: Daniel Ng <danielng@google.com> Reviewed-by:
Julian Watson <juwa@google.com> Cr-Commit-Position: refs/heads/master@{#745376}
-
Nick Harper authored
Change-Id: I7849bb227ef1e83e2359500357df4e331e3cddb0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079854Reviewed-by:
Ryan Sleevi <rsleevi@chromium.org> Commit-Queue: Ryan Sleevi <rsleevi@chromium.org> Cr-Commit-Position: refs/heads/master@{#745375}
-
Kenichi Ishibashi authored
ServiceWorkerStorage will be encapsulated in a mojo interface and will be moved outside content/. This means that it can't expose any public method which returns a value synchronously. IsDisable() returns a boolean value synchronously so we need to hide it. ServiceWorkerRegistry needs to know if ServiceWorkerStorage is disabled without IsDisabled(). This CL introduces a new field that manages the state. It is updated when a storage operation is failed. This isn't exactly the same, but should have almost the same effect. Bug: 1055677 Change-Id: I1aab48eb4bf624c3d4c077d8e13472b188f8607d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079715 Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#745374}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/e74f711e17c2..03a5e99059af git log e74f711e17c2..03a5e99059af --date=short --first-parent --format='%ad %ae %s' 2020-02-28 dberris@chromium.org Pinpoint: Fix results2 for new executions Created with: gclient setdep -r src/third_party/catapult@03a5e99059af 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 oysteine@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:chromeos-kevin-rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: chromium:1056658 Tbr: oysteine@google.com Change-Id: I61dcf43225da5ce0a85190a2df4323978776ee97 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079936Reviewed-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@{#745373}
-
garzonou authored
Change-Id: Iebfa0f569d2b893004fad01bdaa4ebf2cb14e7ce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068262Reviewed-by:
Hiroshi Ichikawa <ichikawa@chromium.org> Commit-Queue: Hiroshi Ichikawa <ichikawa@chromium.org> Auto-Submit: Jiajun Ou <garzonou@google.com> Cr-Commit-Position: refs/heads/master@{#745372}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/a090e226e224..590b36126628 Created with: gclient setdep -r src-internal@590b36126628 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 jbudorick@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: jbudorick@google.com Change-Id: If01b06476768f798971e65c1842c8b39dde4ea7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079931Reviewed-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@{#745371}
-
Nicholas Hollingum authored
One feature of the mocks that is yet to be implemented is the handling of backup-location choice/re-use. In this CL we implement those features. Specifically: - Backup will use the default location without bringing up a file-chooser (unless it is taken, in which case the file chooser is brought up to confirm the overwrite/rename) - If the user selects "change location" the file chooser will be shown. - If backup completed successfully and upgrade fails, restore will immediately begin from the known backup location, rather than prompting the user to find their backup. Bug: 1024693 Change-Id: Iaa57f7162e7c12b483ba30b205c720dd88ea0c31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068400 Commit-Queue: Nic Hollingum <hollingum@google.com> Reviewed-by:
Sam McNally <sammc@chromium.org> Reviewed-by:
Joel Hockey <joelhockey@chromium.org> Reviewed-by:
Nicholas Verne <nverne@chromium.org> Cr-Commit-Position: refs/heads/master@{#745370}
-
Tim Song authored
BUG=1040648 Change-Id: I58630f7fbffc0132745b0b14f20816a3980a4a97 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079800Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Reviewed-by:
Gil Dekel <gildekel@chromium.org> Commit-Queue: Tim Song <tengs@chromium.org> Cr-Commit-Position: refs/heads/master@{#745369}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/78da538aed52..a60e49738bf1 git log 78da538aed52..a60e49738bf1 --date=short --first-parent --format='%ad %ae %s' 2020-02-28 tobine@google.com Revert "Vulkan:Include precision qualifier in GLSL" Created with: gclient setdep -r src/third_party/angle@a60e49738bf1 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/+/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 Bug: None Tbr: geofflang@google.com Change-Id: I56cddb327695403e2f4d9a1dbd2f03b4f17372fd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079870Reviewed-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@{#745368}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/0e29459cda65..23d978da38f9 git log 0e29459cda65..23d978da38f9 --date=short --first-parent --format='%ad %ae %s' 2020-02-28 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). 2020-02-28 csmartdalton@google.com Move setupGeometry() from GrGLGpu to GrGLOpsRenderPass 2020-02-28 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). Created with: gclient setdep -r src/third_party/skia@23d978da38f9 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 jlavrova@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/+/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 Bug: None Tbr: jlavrova@google.com Change-Id: I6ccb034c8db7e1a823bc1aea345bd5e771ad781b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079951Reviewed-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@{#745367}
-
Miyoung Shin authored
The CL fixes regression of https://crrev.com/c/2049151 and avoids use of uninitialized value in blink::WebGLRenderingContextBase::CreateWebGraphicsContext3DProvider. Bug: 1056440 Change-Id: I6afc71b7384e3c90f85ba4996d44d5857c9cf2fd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078373Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Miyoung Shin <myid.shin@igalia.com> Cr-Commit-Position: refs/heads/master@{#745366}
-
Zhongyi Shi authored
https://quiche.googlesource.com/quiche.git/+log/5f23a2d78434..c7efb6778396 $ git log 5f23a2d78..c7efb6778 --date=short --no-merges --format='%ad %ae %s' 2020-02-25 dschinazi Add -Wrange-loop-analysis warnings to QUIC build config 2020-02-24 nharper Remove QuicCryptoStream::OnSuccessfulVersionNegotiation 2020-02-24 zhongyi gfe-relnote: fix path probe request in IETF QUIC, padded ping with peer address change should not be treated as path probe request. Only a packet contains PATH_CHALLENGE frame is considered as a path probe request. Protected by disabled QUIC version 99. 2020-02-24 wub gfe-relnote: (n/a) Deprecate --gfe2_reloadable_flag_quic_bbr_loss_based_startup_exit. 2020-02-24 wub gfe-relnote: (n/a) Deprecate --gfe2_reloadable_flag_quic_one_bw_sample_per_ack_event2. 2020-02-24 fayang Add DCHECKs to make sure data does not get sent after connection closed. 2020-02-24 quiche-dev gfe-relnote: Fix a Wrange-loop-analysis warnings in quiche. 2020-02-24 wub gfe-relnote: (n/a) Deprecate --gfe2_reloadable_flag_quic_bw_sampler_remove_packets_once_per_congestion_event2. 2020-02-24 quiche-dev LSC: Add std:: qualifications to all references to std::string and std::basic_string. 2020-02-23 quiche-dev LSC: Add std:: qualifications to all references to std::string and std::basic_string. 2020-02-21 nharper Remove one layer of abstraction in QuicCryptoServerStream classes 2020-02-21 wub Internal QUICHE change 2020-02-21 fayang gfe-relnote: In QUIC, do not bother stream ID manager on stream closed if connection has already been closed. Protected by existing gfe2_reloadable_flag_quic_enable_version_t099 or gfe2_reloadable_flag_quic_enable_version_draft_25. 2020-02-21 renjietang Remove stream pointer from QuicSession::WritevData. 2020-02-21 bnc Add and use unique SpdyFramerErrors and QuicErrorCodes for each HpackDecodingError entry. 2020-02-21 fayang gfe-relnote: Add detailed_error_ to error message when failed to parse a received coalesced header. Logging only change, not protected. 2020-02-20 wub gfe-relnote: Notify SendAlgorithm on neutered packets in QUIC. Protected by (enabling blocked) --gfe2_reloadable_flag_quic_avoid_overestimate_bandwidth_with_aggregation. 2020-02-20 renjietang gfe-relnote: In QUIC, remove an outdated memory corruption check that hasn't occurred for a long time. not protected. Created with: roll-dep src/net/third_party/quiche/src src/third_party/quic_trace/src Bug: 1039697 Change-Id: Ie32dcd48ad6260869370c191990e27a637bad48e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2075877 Commit-Queue: Zhongyi Shi <zhongyi@chromium.org> Reviewed-by:
Henrik Boström <hbos@chromium.org> Reviewed-by:
Bence Béky <bnc@chromium.org> Auto-Submit: Zhongyi Shi <zhongyi@chromium.org> Cr-Commit-Position: refs/heads/master@{#745365}
-
Frank Tang authored
Intl.DisplayNames shipped in m81, we should add UsageCounter to track usage. Bug: 1054490 Change-Id: I98c4714709c5600d1094823c4683b59ec3adeaf8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067738 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
Nate Chapin <japhet@chromium.org> Cr-Commit-Position: refs/heads/master@{#745364}
-
Tim Song authored
Because we display a toast when the privacy screen setting changes, we do not want to display it on initialization or switching users. BUG=1040648 Change-Id: I7f507fa401e4c040f8dc3c531a3aaea91e3ff1fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079799 Commit-Queue: Tim Song <tengs@chromium.org> Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Reviewed-by:
Gil Dekel <gildekel@chromium.org> Cr-Commit-Position: refs/heads/master@{#745363}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/21c99c4478fb..e74f711e17c2 git log 21c99c4478fb..e74f711e17c2 --date=short --first-parent --format='%ad %ae %s' 2020-02-28 abennetts@google.com Fix running telemetry test when base_commit is missing a commit_position. 2020-02-28 fancl@chromium.org Increase sampling from 0.5 to 1.0 Created with: gclient setdep -r src/third_party/catapult@e74f711e17c2 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 oysteine@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:chromeos-kevin-rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: chromium:1051943,chromium:1052720 Tbr: oysteine@google.com Change-Id: I6e9a66577761cb645c4aa0d67e23e23eb4eeb57b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079868Reviewed-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@{#745362}
-
Yoichi Osato authored
This CL is refactoring. This CL extracts ResourceRequest::CopyFrom() in main resource loading path that fetch doesn't use. This is a preparation for fetch upload streaming. Bug: 787704 Change-Id: I0b53eca0dac33d1aeffd81ddb39d8c49b9f70824 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2076823Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Yoichi Osato <yoichio@chromium.org> Cr-Commit-Position: refs/heads/master@{#745361}
-
David Munro authored
Test: CQ Bug: chromium:858815 Change-Id: Ica5475ee82cf5f8ec84ac611f4662ab859f97a3f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2073317Reviewed-by:
Ryo Hashimoto <hashimoto@chromium.org> Commit-Queue: Ryo Hashimoto <hashimoto@chromium.org> Auto-Submit: David Munro <davidmunro@google.com> Cr-Commit-Position: refs/heads/master@{#745360}
-
Joel Hockey authored
Terminal must have dedicated logic to invoke ShowCrostiniUpdateComponentView. Most crostini apps start crostini first and show a spinner whilst this is happening before launching the app. The crostini startup logic for this case detects when to show the update component view. Terminal System App launches immediately so that it can show the status of crostini starting, so it requires extra logic. TerminalSource dummy files have been extended to include terminal.html and terminal.js which invokes chrome.terminalPrivate.openTerminalProcess to test this logic. Change-Id: I68ec7b769e038947d107024e36312e9c0689f862 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2079719 Commit-Queue: Joel Hockey <joelhockey@chromium.org> Reviewed-by:
Nicholas Verne <nverne@chromium.org> Cr-Commit-Position: refs/heads/master@{#745359}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=abdulsyed@chromium.org Change-Id: I7f5bfd80accfdf96073f2a13693248521433bab8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078741Reviewed-by:
Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#745358}
-