- 13 Nov, 2019 40 commits
-
-
Tibor Goldschwendt authored
Change-Id: Id5315c46499b56e49e6acebe1aff67d84ab6bc7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1903931 Auto-Submit: Tibor Goldschwendt <tiborg@chromium.org> Commit-Queue: Andrew Grieve <agrieve@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Reviewed-by:
Christopher Grant <cjgrant@chromium.org> Cr-Commit-Position: refs/heads/master@{#714955}
-
Aaron Krajeski authored
By the old method both the paint canvas and the recorder canvas would hold the transform, thus it would be applied twice. With this change OffscreenCanvas::TransferToImageBitmap restores the matrix onto the recorder directly if it is deferred. In general, canvas hosts should not reach directly into resource provider's paint canvases. Bug: 1021321 Change-Id: I1f499218c6e58168d13b6fc88ad88d69b4435191 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1904266Reviewed-by:
Fernando Serboncini <fserb@chromium.org> Reviewed-by:
Yi Xu <yiyix@chromium.org> Commit-Queue: Aaron Krajeski <aaronhk@chromium.org> Cr-Commit-Position: refs/heads/master@{#714954}
-
Garrett Beaty authored
Bug: 1011908 Change-Id: I431823141a8d2affe9d9ac24b5e4964626166c1b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1908924 Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Reviewed-by:
Aaron Gable <agable@chromium.org> Cr-Commit-Position: refs/heads/master@{#714953}
-
Lukasz Anforowicz authored
There are multiple calls to GetOriginForURLLoaderFactory made from RenderFrameHostImpl::CommitNavigation. Instead of making these calls, we can make a single call early during CommitNavigation and store the result in a variable that gets reused later on. This refactoring has been suggested when code reviewing another CL here: https://chromium-review.googlesource.com/c/chromium/src/+/1875273/15/content/browser/frame_host/render_frame_host_impl.cc#5420 It turns out that moving the GetOriginForURLLoaderFactory call earlier means that it also gets called for navigations to about:srcdoc. In this case the URLLoaderFactory should be inherited from the parent, so the origin calculated by GetOriginForURLLoaderFactory is not technically needed. OTOH, GetOriginForURLLoaderFactory should in the future calculate the origin to commit, and therefore we should make sure it correctly handles all the cases. In particular, without special-casing about:srcdoc, NavigationBrowserTest.BlockedSrcDocRendererInitiated* tests would hit a CHECK(...CanAccessDataForOrigin...) in GetOriginForURLLoaderFactory. This CL fixes this. Bug: 998247, 920634, 936310 Change-Id: I1ca851c8e574d24f05b4943f6bee186ebd50aa61 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1910865Reviewed-by:
Nasko Oskov <nasko@chromium.org> Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Cr-Commit-Position: refs/heads/master@{#714952}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/c5ec54e51b91..06a394e036ab git log c5ec54e51b91..06a394e036ab --date=short --no-merges --format='%ad %ae %s' 2019-11-13 mbonadei@webrtc.org Revert "Reland "Define WEBRTC_ENABLE_SYMBOL_EXPORT if is_component_build=true."" 2019-11-13 mbonadei@webrtc.org Reland "Define WEBRTC_ENABLE_SYMBOL_EXPORT if is_component_build=true." 2019-11-13 mbonadei@webrtc.org Use explicit template decl/def for RTCNonStandardStatsMember. Created with: gclient setdep -r src/third_party/webrtc@06a394e036ab 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 TBR=webrtc-chromium-sheriffs-robots@google.com Bug: None Change-Id: I3c7b20e7733c19a86155b6d455484d508771f6c4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913653Reviewed-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@{#714951}
-
Elly Fong-Jones authored
TBR=wjmaclean@chromium.org Bug: 1024028 Change-Id: I22a4a2bf37a28243f926b53c03e6ff4741494e9c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913864Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#714950}
-
Peter Kasting authored
Screenshots: https://bugs.chromium.org/p/chromium/issues/detail?id=1024091#c2 Bug: 1024091 Change-Id: I2c318452bafbefc16da3e9c2687911162b26c3f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913509 Auto-Submit: Peter Kasting <pkasting@chromium.org> Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#714949}
-
Weiliang Chen authored
In Android pre-SurfaceControl, we might encounter cases where the video resource is not ready when we first re-open chromium. Match the behavior of GLRenderer, and early return without crashing in SkiaRenderer. Bug: 1016528 Change-Id: I28aae1c46e724c4c97cea4313c395a66f2af13b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913168Reviewed-by:
Robert Kroeger <rjkroege@chromium.org> Commit-Queue: weiliangc <weiliangc@chromium.org> Cr-Commit-Position: refs/heads/master@{#714948}
-
Mirko Bonadei authored
While testing the WebRTC component build [1], lld-link started to complain about undefined symbols from the MS SDK. This is caused by the fact that different parts of Chromium were relying on WebRTC to pass some libraries to the linker but since WebRTC is going to support the component build soon, these libraries will not reach the linker since they will be linked only in the WebRTC shared library. This CL addresses the errors detected here [2]. [1] - https://chromium-review.googlesource.com/c/chromium/src/+/1874722 [2] - https://ci.chromium.org/p/chromium/builders/try/win_chromium_compile_dbg_ng/436771 Bug: webrtc:9419 Change-Id: I7af507a13285f976b5545025e2181ae4e47eded2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913251 Commit-Queue: Mirko Bonadei <mbonadei@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#714947}
-
Garrett Beaty authored
These changes simplify migrating to starlark by removing spurious diffs from the semantic diff. The "Memory Infra tester" builder is actually named "Memory Infra Tester". The cronet notifier had an entry for the removed android-cronet-marshmallow-arm-rel builder. The release-tarballs notifier only notified on builders from a non-existent bucket. Bug: 1011908 Change-Id: I753df31a5496e0a7d73e738776f84ea088668e30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1910346Reviewed-by:
Aaron Gable <agable@chromium.org> Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Cr-Commit-Position: refs/heads/master@{#714946}
-
liberato@chromium.org authored
This will mirror the finch config, once presubmit for the gcl change passes. Right now, it's mad about the field trial testing config. Change-Id: I58ecc99ae5901e0cd6aee407d73aefcfebe36f04 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913485Reviewed-by:
Ilya Sherman <isherman@chromium.org> Commit-Queue: Frank Liberato <liberato@chromium.org> Cr-Commit-Position: refs/heads/master@{#714945}
-
Anatoliy Potapchuk authored
Also, bring back IsLoggedInAsWebKioskApp() for permissions handling. Bug: 1015383,1006230 Change-Id: I66dfda221fd828443f580746c68faf47757d4137 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1911797 Commit-Queue: Anatoliy Potapchuk <apotapchuk@chromium.org> Reviewed-by:
Sergey Poromov <poromov@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#714944}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/8b73d27ddd61..99e73fa8c1c5 git log 8b73d27ddd61..99e73fa8c1c5 --date=short --no-merges --format='%ad %ae %s' 2019-11-13 robertphillips@google.com Remove GL 4-bit stencil option Created with: gclient setdep -r src/third_party/skia@99e73fa8c1c5 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 halcanary@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 TBR=halcanary@google.com Bug: None Change-Id: I95f3084c4912efd832b6818f51b2ddf91dbe0940 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913652Reviewed-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@{#714943}
-
Francois Doray authored
Change-Id: I543ef610bdd8b6ff75033fc6014a37b871b07086 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1909386 Auto-Submit: François Doray <fdoray@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Commit-Queue: François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#714942}
-
danakj authored
This removal was done in 238f6ccc which claims it was to remove the not-run tests from the shard bot's output. The list of TestExpectations no longer appear to affect the output, as only the list of tests to be run on the shard appear in the output.json file. After building the model of 80000 TestExpectations, we then go through them all removing tests that are not going to run on the bot. To do so we do O(TestExpectations * TestsNotRunningOnBot) which is like O(100k * 100k) so it is very slow. Locally, not doing this saves 31 of the 46 seconds spent during startup between: 16:14:54.439 117357 Collecting tests ... ... 16:15:40.689 117357 Found 3626 tests (total 86597); running 3388, skipping 238. On windows bots we see this time go from 65 seconds to 28 seconds, saving 37 seconds, or another 60% of the test collection startup time. R=robertma@chromium.org Bug: 982208 Change-Id: I0570cc5610f296b3f5850973f02fb85946ebaf38 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913165 Commit-Queue: danakj <danakj@chromium.org> Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Reviewed-by:
Robert Ma <robertma@chromium.org> Cr-Commit-Position: refs/heads/master@{#714941}
-
Yifan Luo authored
See https://wpt.fyi/results/fetch/metadata?label=experimental&label=master&aligned. 1. `xslt.tentative.https.sub.html`: delete tests for same-site and cross-site, because these requests are not allowed and has been blocked by browser behavior. 2. `redirect/multiple-redirect-https=downgrade-upgrade.tentative.sub.html` and `redirect/redirect-http-upgrade.tentative.sub.html`: removed from `NeverFixTests` and change the expectation for mode from `nasted-navigate` to `navigate`. 3. `redirect/redirect-https-downgrade.tentative.sub.html`: removed from `NeverFixTests` and change the expectation for Https downgrade script. Bug: 1024198 Change-Id: Ia0cf0ccc2bef38c4525bebab0a050e7b1de9a5e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1912712Reviewed-by:
Mike West <mkwst@chromium.org> Commit-Queue: Yifan Luo <lyf@google.com> Cr-Commit-Position: refs/heads/master@{#714940}
-
Will Harris authored
BUG=978133 Change-Id: I9bdad7579ceedc467b029fcc65f8e3c5d2dae1de Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1912502Reviewed-by:
Greg Thompson <grt@chromium.org> Commit-Queue: Will Harris <wfh@chromium.org> Cr-Commit-Position: refs/heads/master@{#714939}
-
Anthony Vallee-Dubois authored
FCMInvalidationService currently does 2 things: it observes changes to its IdentityProvider and maintains invalidations-related state. The seam between those responsibilities is pretty clear. In order to support invalidations for Machine-Level cloud policies on desktop browsers, we need to use the invalidations-related bits of FCMInvalidationService in a context where there is no IdentityProvider. This is different than the ChromeOS case where there's no Profile but a Device Level Robot Account is available (See AffiliatedInvalidationServiceProvider). Desktop browsers have no such robot account, therefore no IdentityProvider in the context of Machine- Level policies. This CL splits off the profile-agnostic parts of FCMInvalidationService into their own base class: FCMInvalidationServiceBase. This refactor should be a no-op, except it will allow us to add a second implementation of FCMInvalidationServiceBase that doesn't care about the presence of an account. The linked bug and the design doc (go/cbcm-machine-policy-invalidations) contain more context about this change. Bug: 1019791 Change-Id: Ib659aaa7d52f18797c67eaa9faae6d78d746942c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1910423Reviewed-by:
Marc Treib <treib@chromium.org> Reviewed-by:
Tatiana Gornak <melandory@chromium.org> Commit-Queue: anthonyvd <anthonyvd@chromium.org> Cr-Commit-Position: refs/heads/master@{#714938}
-
Owen Min authored
All contents are copied from https://sites.google.com/a/chromium.org/dev/developers/how-tos/enterprise/adding-new-policies. Note that even some contents in the original link are out of date, this CL does not update any of them. Bug: 1022143 Change-Id: I117da6dba6b56cfa41538756f6eb2a4d92d8325d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1902274 Commit-Queue: Owen Min <zmin@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Cr-Commit-Position: refs/heads/master@{#714937}
-
Doug Turner authored
This CL cleans up the use MainParams by removing duplicate functionality provided by version_info. As noted in the bug, this CL also will update the user agent string to be consistent with the Chrome user agent. Bug: 1018236 Change-Id: Iee35d1312861537013eeaeb047b75cd05d877851 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1909282 Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#714936}
-
Andreas Haas authored
The ByteLength field of DOMArrayBuffer changed to size_t. Therefore we have to serialize it as Uint64 now. Bug: v8:4153 Change-Id: I38642b5261f9d64a6307cc609e9ba61a4f35860c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1912201Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#714935}
-
Henrique Nakashima authored
Chromium's only exists for historic reasons, currently serving documentation purposes only. AndroidX's version is supported by Android lint, though the check at build time is not currently working (crbug.com/1022939). This check is still useful for Android Studio. These instances were missed in https://chromium-review.googlesource.com/c/chromium/src/+/1901635. Bug: 889467 Change-Id: I39e5a2039a7eb7ac29d1e5d35e9d22af7c60e951 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1907199Reviewed-by:
Carlos Knippschild <carlosk@chromium.org> Commit-Queue: Henrique Nakashima <hnakashima@chromium.org> Cr-Commit-Position: refs/heads/master@{#714934}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/90f9ed46..e156cb1e 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: I848a71bbf08c2b2b9e49417c153d52091137e9a1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1914187Reviewed-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@{#714933}
-
Kevin Ellis authored
Animation::PostCommit does not alter the state of any flags that affect play state. Bug: 960944 Change-Id: I3aff88c688aed376c046f249fd627187757ac280 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1911387Reviewed-by:
Majid Valipour <majidvp@chromium.org> Commit-Queue: Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#714932}
-
Rayan Kanso authored
Also update the idl definition to the correct value. Change-Id: Ida7936ef43733702f20c5a6efa9ef7a869de09c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1912900Reviewed-by:
Peter Beverloo <peter@chromium.org> Commit-Queue: Rayan Kanso <rayankans@chromium.org> Cr-Commit-Position: refs/heads/master@{#714931}
-
Clemens Backes authored
The API will change on the V8 side (https://crrev.com/c/1914199). The test needs to be rebased after the v8 roll. R=ahaas@chromium.org CC=bbudge@chromium.org Bug: v8:1018029 Change-Id: I917bf516b20bfa1fbf9cf0eb2e4fff64d938dc6e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1914381Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#714930}
-
Owen Min authored
Upload a boolean that indicates whether the extension comes from CWS. Upload a string that represents the app launch url for (legacy) packaged app and hosted_app. Bug: 1024039 Change-Id: Ieda4675fed256b4919266aaf7271fb1b4e538478 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1912832 Commit-Queue: Owen Min <zmin@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Cr-Commit-Position: refs/heads/master@{#714929}
-
Vasilii Sukhanov authored
Bug: 986317 Change-Id: I51809ba947cff7f599727875632a3e34f133630e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1914379Reviewed-by:
Ioana Pandele <ioanap@chromium.org> Commit-Queue: Ioana Pandele <ioanap@chromium.org> Auto-Submit: Vasilii Sukhanov <vasilii@chromium.org> Cr-Commit-Position: refs/heads/master@{#714928}
-
Chris Sharp authored
Bug: 1011100 Change-Id: Icd63616b1cceab782cb767a19489222f3c53b24e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906630Reviewed-by:
Carlos Knippschild <carlosk@chromium.org> Reviewed-by:
Chris Sharp <csharp@chromium.org> Reviewed-by:
Tommy Martino <tmartino@chromium.org> Commit-Queue: Chris Sharp <csharp@chromium.org> Cr-Commit-Position: refs/heads/master@{#714927}
-
Anton Bikineev authored
This CL reorders reallocation scenario as follows: 1) allocating a new buffer; 2) moving elements in the current buffer to the new one ***without tracing them or executing write barriers on them*** 3) resetting HeapVector's pointer to the new buffer; 4) executing write barrier on the new buffer. The followup to the CL will be introducing the same optimization for HashTable. Bug: 1021889 Change-Id: I367165ba26045d3a4ca967c7f9f006ff88be4ed4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1899883 Commit-Queue: Anton Bikineev <bikineev@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#714926}
-
Henrik Boström authored
Invoke the callback-based version of AddIceCandidate() recently added in third_party/webrtc. This CL also... - Adds WPT test coverage for two separate but related issues relating to the timing between SLD and addIceCandidate which may cause edge-case race conditions when exchanging ICE candidates. See referenced bugs. - Remove old AddIceCandidate code path. Bug: chromium:1019222, chromium:1019232 Change-Id: I11d013487325b14739f99617c1d2063a06743524 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906368 Commit-Queue: Henrik Boström <hbos@chromium.org> Reviewed-by:
Harald Alvestrand <hta@chromium.org> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#714925}
-
Chris Lu authored
This change adds strings needed for the banner and modal elements. It includes screenshots for the banner text since those likely require the most context. Bug: 1014959 Change-Id: I19772873bb386dd7726d348b90e776f0ddc628e4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1902717Reviewed-by:
Mark Cogan <marq@chromium.org> Reviewed-by:
Sergio Collazos <sczs@chromium.org> Commit-Queue: Chris Lu <thegreenfrog@chromium.org> Cr-Commit-Position: refs/heads/master@{#714924}
-
Dave Tapuska authored
A new API was exposed to call regexp exec directly instead of having to go through a js call function so use it. BUG=966405 Change-Id: I6e6defcdd1a2c7bded6c1a295d10885151635bad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913467Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Cr-Commit-Position: refs/heads/master@{#714923}
-
Boris Sazonov authored
Bug: None Change-Id: I5ddaa706589b2a7f426dffbd75fdf040bc16f14c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913213 Auto-Submit: Boris Sazonov <bsazonov@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Commit-Queue: Boris Sazonov <bsazonov@chromium.org> Cr-Commit-Position: refs/heads/master@{#714922}
-
Marc Treib authored
Since crrev.com/c/1174655 landed (more than a year ago), HttpBridgeFactory doesn't actually need the CancelationSignal anymore. Removing it also lets us remove a bunch of plumbing. Bug: 951350 Change-Id: Ic4332320845747aacae43bc7062094f6da77b13b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1912715 Commit-Queue: Marc Treib <treib@chromium.org> Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#714921}
-
Matt Menke authored
Make proxy_resolver::mojom::ProxyResolverRequestClient::ResolveDns and proxy_resolver::mojom::ProxyResolverFactoryRequestClient::ResolveDns take in a NetworkIsolationKey. Unfortunately, the only production implementation of these classes only has integration tests, so this CL adds no tests - I'll add them in the CL where I update net::ProxyResolver to take a NetworkIsolationKey, which will likely be a huge CL. Bug: 1021661 Change-Id: Iaefb62fa84cc50bfc90a7f48ada6f77bba3d65d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1903760Reviewed-by:
Eric Roman <eroman@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Commit-Queue: Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#714920}
-
Gauthier Ambard authored
This target was used for downstream compatibility. Land this CL after downstream CL lands. Bug: none Change-Id: I204c794b592d9746e18d4a2083bb46a44cd7199b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913408Reviewed-by:
Mark Cogan <marq@chromium.org> Commit-Queue: Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#714919}
-
Ryan Sturm authored
Currently, NoStatePrefetch only fetches HTML + CSS + Sync JS.We should experiment with also prefetching WebFonts since WebFonts are render blocking on fast connections. This CL adds a finch parameter to LWNSP experiment. Bug: 1021749 Change-Id: I9bbf3c629d620df89aa6ae54d3352d7ba1fb6952 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1901590Reviewed-by:
Robert Ogden <robertogden@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Tarun Bansal <tbansal@chromium.org> Cr-Commit-Position: refs/heads/master@{#714918}
-
Gauthier Ambard authored
This CL adds a DCHECK to make sure that the method to be swizzled in ScopedMethodSwizzler exists. Previously the method was added. Bug: none Change-Id: I9d6a9d935f7cf15cb644df1e70c44f8188f3bdf3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913252 Auto-Submit: Gauthier Ambard <gambard@chromium.org> Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Commit-Queue: Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#714917}
-
Denis Kuznetsov authored
Bug: 955194 Change-Id: Ie12def6987bbbf7b4ff5bdc738bcdb40b87e53fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1912359 Commit-Queue: Denis Kuznetsov [CET] <antrim@chromium.org> Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#714916}
-