- 20 Jan, 2020 40 commits
-
-
Fredrik Söderquist authored
This will allow disabling event dispatching altogether in cases where we can reliably do that (SVGImage). It may also help with not sending events when seeking the timeline. Bug: 1021630, 1039886 Change-Id: I82e7b453b3b6abb1d71d064c33c89db7657c8b06 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007572Reviewed-by:
Philip Rogers <pdr@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#733399}
-
Mihai Sardarescu authored
The corresponding feature flag was already removed from the application a while back. This CL removes it from flag-metadata.json as well. Bug: NONE Change-Id: I6929e19c4c61445b03458b80c3e44ff2e18da068 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010772 Auto-Submit: Mihai Sardarescu <msarda@chromium.org> Commit-Queue: Mihai Sardarescu <msarda@chromium.org> Commit-Queue: David Roger <droger@chromium.org> Reviewed-by:
David Roger <droger@chromium.org> Cr-Commit-Position: refs/heads/master@{#733398}
-
jonross authored
GpuProcessHostDisableGLBrowserTest.CreateAndDestroy wants to use software compositing, not the hardware path. The vulkan_content_browsertests were enforcing that software fallback not be allowed. Causing this test to crash. However BrowserTestBase::UseSoftwareCompositing already is in use by tests which wish to explicitly be software compositing only. I'm adding this to the setup of the test to allow it to run in the vulkan_content_browsertests suite. TEST=vulkan_content_browsertests GpuProcessHostDisableGLBrowserTest.CreateAndDestroy Bug: 1009664 Change-Id: I85f00e2e3a4bf710d946ac69d46bd3e0e0879233 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003251Reviewed-by:
Jonathan Backer <backer@chromium.org> Commit-Queue: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/master@{#733397}
-
Sylvain Defresne authored
Instead of forward declaring ChromeBrowserState in the ios namespace, use a header. This will allow moving the class to the global namespace without having to change all the forward declaration at the same time. This CL was uploaded by git cl split. R=gambard@chromium.org Bug: 1042208 Change-Id: If065e4216e783e5356f4014696d2ebc853208f12 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007726 Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Commit-Queue: Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#733396}
-
Tom McKee authored
In the User Timing spec, it is an error to make a PerformanceMark with the same name as a read-only attribute from the PerformanceTiming interface[1]. E.g. it is an error to call `performance.mark("navigationStart")` as this would lead to ambiguity when trying to resolve calls like `performance.measure("m", "navigationStart")`. Since the read-only attributes are defined on the PerformanceTiming interface[2], it makes more sense to declare a name/attribute mapping locally instead of in the PerformanceUserTiming class. [1]: https://w3c.github.io/user-timing/#the-performancemark-constructor [2]: https://www.w3.org/TR/navigation-timing/#sec-navigation-timing-interface Bug: 805566 Change-Id: I2466d123a0d93965555c06d2434cb839fafabb72 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1967567 Commit-Queue: Tom McKee <tommckee@chromium.org> Reviewed-by:
Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#733395}
-
haozhe authored
Currently, we are sorting animations by creation order. This update the animation compositing order to first sort by animation class priority, as per spec (https://drafts.csswg.org/web-animations/#dom-document-getanimations). This inter-element composition order is used and tested by getAnimations. Bug: 993365 Change-Id: I30dd1c504165baa1120b73ab7e18f0b775df8bff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993677 Commit-Queue: Hao Sheng <haozhes@chromium.org> Reviewed-by:
Robert Flack <flackr@chromium.org> Reviewed-by:
Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#733394}
-
kylechar authored
The function signature is no longer different so just use SwapBuffers(). Bug: none Change-Id: I7f244b3dddafd95eb3e534df3cf9e639b3aff5e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008055Reviewed-by:
Peng Huang <penghuang@chromium.org> Commit-Queue: kylechar <kylechar@chromium.org> Cr-Commit-Position: refs/heads/master@{#733393}
-
Nina Satragno authored
Test is failing on the Mac10.13 Tests builder See https://ci.chromium.org/p/chromium/builders/ci/Mac10.13%20Tests%20%28dbg%29/16844 https://ci.chromium.org/p/chromium/builders/ci/Mac10.13%20Tests%20%28dbg%29/16843 https://ci.chromium.org/p/chromium/builders/ci/Mac10.13%20Tests%20%28dbg%29/16842 TBR=dbeam@chromium.org Bug: 1043665 Change-Id: If938bea126e7607e9c74787bac567cac04658c0b No-try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010178Reviewed-by:
Nina Satragno <nsatragno@chromium.org> Commit-Queue: Nina Satragno <nsatragno@chromium.org> Cr-Commit-Position: refs/heads/master@{#733392}
-
Sylvain Defresne authored
Instead of forward declaring ChromeBrowserState in the ios namespace, use a header. This will allow moving the class to the global namespace without having to change all the forward declaration at the same time. This CL was uploaded by git cl split. R=olivierrobin@chromium.org Bug: 1042208 Change-Id: I15d44cfb7e142a9c7fc41373d454ee997c7ed6fa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010784 Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Olivier Robin <olivierrobin@chromium.org> Commit-Queue: Olivier Robin <olivierrobin@chromium.org> Cr-Commit-Position: refs/heads/master@{#733391}
-
Stepan Khapugin authored
MainController observes WSL to know when the last {normal|incognito} tab is closed. Conceptually, this seems like a Scene-level concern. However, clearing browsing data might be an App-level concept, so I keep the logic in MainController for now. Bug: none Change-Id: I0b3453518f4f0390a34f77ce27817f4af1f4d650 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003135 Commit-Queue: Stepan Khapugin <stkhapugin@chromium.org> Reviewed-by:
Mark Cogan <marq@chromium.org> Cr-Commit-Position: refs/heads/master@{#733390}
-
Dave Tapuska authored
Change-Id: I6a91ea0021077507e968ce2be0adde5588118d74 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010169Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Cr-Commit-Position: refs/heads/master@{#733389}
-
Sylvain Defresne authored
This reverts commit 53513b6a. Reason for revert: Use the wrong path. Original change's description: > [ios] Allow use of chrome_browser_provider_forward.h from provider > > The provider are not permitted to have dependency on //ios/chrome, > however they were able to forward-declare ChromeBrowserProvider so > they ended up with indirect dependency. > > To allow moving the class to the global namespace, allow them to > include the forwarding header since this does not increase the > amount of "bad" dependency. > > Bug: 1042208, 1043657 > Change-Id: I838167daa14f16ab65983fd3ebf61267f1a9eedd > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010796 > Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> > Reviewed-by: Mark Cogan <marq@chromium.org> > Commit-Queue: Sylvain Defresne <sdefresne@chromium.org> > Cr-Commit-Position: refs/heads/master@{#733375} TBR=marq@chromium.org,sdefresne@chromium.org Change-Id: Iaa7ff98d55ac57fefb448ff0b9ed246cb2495069 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1042208, 1043657 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010864Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Commit-Queue: Sylvain Defresne <sdefresne@chromium.org> Cr-Commit-Position: refs/heads/master@{#733388}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/3322aafc36d4..ef05567733eb git log 3322aafc36d4..ef05567733eb --date=short --first-parent --format='%ad %ae %s' 2020-01-20 bsalomon@google.com Don't pass final W/H to convolve_gaussian() in SkGpuBlurUtils. Created with: gclient setdep -r src/third_party/skia@ef05567733eb 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 benjaminwagner@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: benjaminwagner@google.com Change-Id: Ib1da9b3954a6d2a8ccd84096ca3f80a5b71c6de0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008260Reviewed-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@{#733387}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/c33c078292af..53ad544d73bc git log c33c078292af..53ad544d73bc --date=short --first-parent --format='%ad %ae %s' 2020-01-18 cjmcdonald@chromium.org Add SDK/Unmount endpoint 2020-01-18 bpastene@chromium.org Revert "chrome_chromeos_lkgm: Skip betty & betty-pi-arc when updating the LKGM." 2020-01-17 yueherngl@google.com servo: remove 11011.B firmware branch builder 2020-01-17 lamontjones@chromium.org toolchain_util: allow editing unquoted strings 2020-01-17 cjmcdonald@chromium.org Build API: Add logic to handle toolchain changes 2020-01-17 chrome-bot@chromium.org Update config settings by config-updater. 2020-01-17 yueherngl@google.com servo: tie the build to nautlius instead of octopus Created with: gclient setdep -r src/third_party/chromite@53ad544d73bc If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/chromite-chromium-autoroll Please CC chrome-os-gardeners@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:chromeos-kevin-rel Bug: None Tbr: chrome-os-gardeners@google.com Change-Id: Ia8b1dafc2da5d89657d3752d26b82e699dd0d9e0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008259Reviewed-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@{#733386}
-
Tom McKee authored
When running the GPU process, we use dependency injection to customize its behaviour through the ExternalDependencies struct. VizMainImpl's constructor takes an ExternalDependencies parameter and std::moves it to a member field. Some of the code, however, continued to reference the parameter instead of the field. This lead to the code assuming that some dependencies were stubbed out. This CL updates VizMainImpl's constructor to consistently check the member field for the injected values and adds tests to check that some injected values end up in use. Bug: 1040583 Change-Id: If1c7922f4c7286c2a73afd33572b287ad29f64ce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992701Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Tom McKee <tommckee@chromium.org> Cr-Commit-Position: refs/heads/master@{#733385}
-
Sylvain Defresne authored
Instead of forward declaring ChromeBrowserState in the ios namespace, use a header. This will allow moving the class to the global namespace without having to change all the forward declaration at the same time. This CL was uploaded by git cl split. R=marq@chromium.org Bug: 1042208 Change-Id: I0c71b5c3173df9e89d8f616f2d02a844c99880c0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007760 Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Mark Cogan <marq@chromium.org> Commit-Queue: Sylvain Defresne <sdefresne@chromium.org> Cr-Commit-Position: refs/heads/master@{#733384}
-
Nina Satragno authored
Test is failing with timeout. https://ci.chromium.org/p/chromium/builders/ci/linux-chromeos-rel/33950 https://ci.chromium.org/p/chromium/builders/ci/linux-chromeos-rel/33949 Bug: 1043661 TBR=achuith TBR'ing achuith since he seems to have context. Change-Id: I8a40f54f62398b1e08544b00b5c57888d28b36db Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010171Reviewed-by:
Nina Satragno <nsatragno@chromium.org> Commit-Queue: Nina Satragno <nsatragno@chromium.org> Cr-Commit-Position: refs/heads/master@{#733383}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/f5c1f79a282d..9fbe9ae1c109 git log f5c1f79a282d..9fbe9ae1c109 --date=short --first-parent --format='%ad %ae %s' 2020-01-20 titovartem@google.com Add support of negotiating multiple codecs in PC framework 2020-01-20 danilchap@webrtc.org Rewrite RTC_CHECK macros to work in constexpr expression in gcc 2020-01-20 danilchap@webrtc.org Merge RtpPacket HasExtension and IsExtensionReserved functions Created with: gclient setdep -r src/third_party/webrtc@9fbe9ae1c109 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: If89edc197fc679efe85a50f95a5079434b1c6dff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008256Reviewed-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@{#733382}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/07344a40..b56d35e2 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,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: Ia499a637a920d32b7846ca0bbbf896bb3201c22f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010923Reviewed-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@{#733381}
-
Yuki Shiino authored
This patch eventually cancels the change in https://crrev.com/c/1989232 because the web_idl/ and bind_gen/ directories have already been following PEP8. Bug: 839389 Change-Id: I6730f41e632f786e1bba6adc20ddc105d43860b7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010752Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Cr-Commit-Position: refs/heads/master@{#733380}
-
Alex Chau authored
Bug: 1043148 Change-Id: I0789a40948bf74123ce50685726034d11ceedbd5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007764Reviewed-by:
Peter Beverloo <peter@chromium.org> Commit-Queue: Alex Chau <alexchau@chromium.org> Cr-Commit-Position: refs/heads/master@{#733379}
-
Sylvain Defresne authored
Instead of forward declaring ChromeBrowserState in the ios namespace, use a header. This will allow moving the class to the global namespace without having to change all the forward declaration at the same time. This CL was uploaded by git cl split. R=droger@chromium.org Bug: 1042208 Change-Id: I5fbed15d8a69cf472a24dcf0f855f617b0b9f62c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007814 Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
David Roger <droger@chromium.org> Commit-Queue: Sylvain Defresne <sdefresne@chromium.org> Cr-Commit-Position: refs/heads/master@{#733378}
-
Jonathan Ross authored
We recently re-enabled a set of tests we believed were fixed: https://chromium-review.googlesource.com/c/chromium/src/+/2006132 However the media/ tests we enabled apparently still flake, but only on Windows. This patch re-adds them to the flag expectations. TBR=backer@chromium.org TEST=skia_renderer_gl_blink_web_tests Bug: 1026375 Change-Id: I141b6c75a7515f178d8c092c29705d99eb79697a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008255Reviewed-by:
Jonathan Ross <jonross@chromium.org> Reviewed-by:
Jonathan Backer <backer@chromium.org> Commit-Queue: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/master@{#733377}
-
Yuki Shiino authored
posixpath.abspath("d:\\a\\b") doesn't work because posixpath doesn't recognize a drive letter. This patch fixes the issue. Bug: 839389 Change-Id: Ifef644dd1e9b26e6a4e572f485e7cbabf7148871 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010751 Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Cr-Commit-Position: refs/heads/master@{#733376}
-
Sylvain Defresne authored
The provider are not permitted to have dependency on //ios/chrome, however they were able to forward-declare ChromeBrowserProvider so they ended up with indirect dependency. To allow moving the class to the global namespace, allow them to include the forwarding header since this does not increase the amount of "bad" dependency. Bug: 1042208, 1043657 Change-Id: I838167daa14f16ab65983fd3ebf61267f1a9eedd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010796 Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Mark Cogan <marq@chromium.org> Commit-Queue: Sylvain Defresne <sdefresne@chromium.org> Cr-Commit-Position: refs/heads/master@{#733375}
-
Chromium WPT Sync authored
Using wpt-import in Chromium e2347e02. With Chromium commits locally applied on WPT: 8a985066 "[Trusted Types] Implement require-trusted-types-for" 0f8fd66b "[WPT/common/security-features] Support sub projects and split referrer-policy 4K tests" 2012a39c "Update timeout and split slow COOP WPTs" Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md Directory owners for changes in this CL: foolip@chromium.org, robertma@chromium.org, smcgruer@chromium.org: external/wpt/infrastructure NOAUTOREVERT=true TBR=robertma No-Export: true Change-Id: I4b19d6c728fffde0ce696b8b011104f009c6f547 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010922Reviewed-by:
WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#733374}
-
Yuki Shiino authored
- Adds V8DOMConfiguration::InstallMethods - Fixes/adds bindings::V8SetReturnValue - Adds ToImpl/ToImplWithTypeCheck and DomTemplate for backward compatibility - Adds check of argument length - Adds member variable definitions of trampoline functions Bug: 839389 Change-Id: Id15984167f876279fe498631fc83aadf4cdd3040 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010593Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Cr-Commit-Position: refs/heads/master@{#733373}
-
Sylvain Defresne authored
Instead of forward declaring ChromeBrowserState in the ios namespace, use a header. This will allow moving the class to the global namespace without having to change all the forward declaration at the same time. This CL was uploaded by git cl split. R=marq@chromium.org Bug: 1042208 Change-Id: I1349bdd47e3b14b023bf292539822cb22a37a0ae Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007287 Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Mark Cogan <marq@chromium.org> Commit-Queue: Sylvain Defresne <sdefresne@chromium.org> Cr-Commit-Position: refs/heads/master@{#733372}
-
Sylvain Defresne authored
Instead of forward declaring ChromeBrowserState in the ios namespace, use a header. This will allow moving the class to the global namespace without having to change all the forward declaration at the same time. This CL was uploaded by git cl split. R=noyau@chromium.org Bug: 1042208 Change-Id: Iebe7231c7edbd4508ea1b9bd34c08c5f9c1a89eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007583 Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Eric Noyau <noyau@chromium.org> Commit-Queue: Eric Noyau <noyau@chromium.org> Cr-Commit-Position: refs/heads/master@{#733371}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/7ec654fdcab5..85de0bc72ef7 git log 7ec654fdcab5..85de0bc72ef7 --date=short --first-parent --format='%ad %ae %s' 2020-01-20 tvanderlippe@chromium.org Fix typescript compilation with ts_library 2020-01-20 aerotwist@chromium.org Adds Puppeteer types 2020-01-20 bmeurer@chromium.org Roll upstream changes. Created with: gclient setdep -r src/third_party/devtools-frontend/src@85de0bc72ef7 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/+/master/autoroll/README.md Bug: chromium:1011811 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Iad3451ad495ca0f936aff89111ff80083e0f1008 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008257Reviewed-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@{#733370}
-
Jan Wilken Dörrie authored
This change removes the Password Leak Detection base::Feature and feature flag. The feature has been launched in M79 and is completely rolled out, which is why it is safe to remove this code now. Bug: 986298 Change-Id: If1f07423e7ef3a55415c6849340b178bc6affdca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007757Reviewed-by:
Javier Ernesto Flores Robles <javierrobles@chromium.org> Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Reviewed-by:
Eric Noyau <noyau@chromium.org> Reviewed-by:
Ioana Pandele <ioanap@chromium.org> Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org> Cr-Commit-Position: refs/heads/master@{#733369}
-
Tom McKee authored
During a load of the main frame, both the RenderWidget and its owned LayerTreeHost, need to be told that there was a navigation. It used to be that the RenderFrameImpl would notify the RenderWidget then reach into the RenderWidget for a reference to the owned LayerTreeHost and signal it too. This violates the "tell, don't get" principle; it makes more sense for the RenderWidget to forward its signal to the LayerTreeHost than to require calling code to know to update the LayerTreeHost. This CL changes the RenderWidget to forward the 'DidNavigate' signal to its LayerTreeHost and simplifies the neighbouring interfaces. Change-Id: I6050f70a194e7030041d56556ddce5f92c3e2deb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002724Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Tom McKee <tommckee@chromium.org> Cr-Commit-Position: refs/heads/master@{#733368}
-
chrome://flagsarthursonzogni authored
This is about the chrome flags: - disable-pushstate-throttle - disable-ipc-flooding-protection They have previously been deprecated. This patch remove them. It is still possible to use them with the command line switches. See also: - https://chromium-review.googlesource.com/c/chromium/src/+/1268016 - https://chromium-review.googlesource.com/c/chromium/src/+/1341526 Bug: 882238 Change-Id: I296e863c63070e8a61ed31babc9276a6e6982e17 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007819Reviewed-by:
Camille Lamy <clamy@chromium.org> Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#733367}
-
Rushan Suleymanov authored
Add sharing_message_specifics proto. Sharing message data type is not ecnryptable and has no local sync. There is no implementation for the datatype yet. Bug: 1034925 Bug: 1034926 Change-Id: I71790d18be609d4795ca435f87fa131942ae2fd5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1997500Reviewed-by:
ssid <ssid@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Alex Chau <alexchau@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Reviewed-by:
vitaliii <vitaliii@chromium.org> Commit-Queue: Rushan Suleymanov <rushans@google.com> Cr-Commit-Position: refs/heads/master@{#733366}
-
Dominique Fauteux-Chapleau authored
Bug: 1042319 Change-Id: Ie33e4f358d35bb6ed5314e19035536c4860afbd3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003349 Commit-Queue: Dominique Fauteux-Chapleau <domfc@chromium.org> Reviewed-by:
Daniel Rubery <drubery@chromium.org> Reviewed-by:
Roger Tawa <rogerta@chromium.org> Cr-Commit-Position: refs/heads/master@{#733365}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/d1a0b3340fc2..cfd2711e575d Created with: gclient setdep -r src-internal@cfd2711e575d 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: I2e6e0ed154deabce8ca68af714476ad93d7da556 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008254Reviewed-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@{#733364}
-
Sylvain Defresne authored
Instead of forward declaring ChromeBrowserState in the ios namespace, use a header. This will allow moving the class to the global namespace without having to change all the forward declaration at the same time. This CL was uploaded by git cl split. R=noyau@chromium.org Bug: 1042208 Change-Id: I7b90f7a9896a688b95adf8437677a4b544d791da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007586 Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Eric Noyau <noyau@chromium.org> Commit-Queue: Eric Noyau <noyau@chromium.org> Cr-Commit-Position: refs/heads/master@{#733363}
-
Erik Chen authored
Most other platforms either unconditionally, or are moving towards unconditionally building with custom libcxx. This comment suggests that there was always the intention to move unconditionally to libc++: https://bugs.chromium.org/p/chromium/issues/detail?id=554841#c3 And this bug suggests that we're already paying most of the engineering cost for making this config work: https://bugs.chromium.org/p/chromium/issues/detail?id=996754 Change-Id: I030f65b5921c4f5572fafcaf975eff24e804f3ed Bug: 1043560 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010226 Commit-Queue: Nico Weber <thakis@chromium.org> Auto-Submit: Erik Chen <erikchen@chromium.org> Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#733362}
-
Mikhail Khokhlov authored
TBMv3 now works on all platforms, so we can enable this. Bug: 990304 Change-Id: I56ab4022dc54d4b332e8fd748cb7e601f3f506ed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007724Reviewed-by:
Deepanjan Roy <dproy@chromium.org> Commit-Queue: Mikhail Khokhlov <khokhlov@google.com> Cr-Commit-Position: refs/heads/master@{#733361}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/material-foundation/material-font-disk-loader-ios/+log/93acc021e303..8e30188777b0 git log 93acc021e303..8e30188777b0 --date=short --first-parent --format='%ad %ae %s' 2017-02-17 willlarche@users.noreply.github.com [Docs] Clarity in README (#1) Created with: gclient setdep -r src/ios/third_party/material_font_disk_loader_ios/src@8e30188777b0 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/material-font-disk-loader-ios-chromium Please CC bling-p10-rolls@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:ios-internal-mdc Bug: None Tbr: bling-p10-rolls@google.com Change-Id: Ia8cd48c698de345bd39027eb33a3afdfbabae735 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008343Reviewed-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@{#733360}
-