- 28 May, 2019 40 commits
-
-
Robert Ogden authored
The stale timestamp histogram is not logged with the new UI unless the page info dialog is opened which can't be done in a ChromeDriver test. Bug: 966667 Change-Id: I7ea17209352a1e18b0b4012da4c396c96125a51e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632116 Commit-Queue: Robert Ogden <robertogden@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Cr-Commit-Position: refs/heads/master@{#663947}
-
arthursonzogni authored
When a frame is unloading in one process, it must not be visible from the other processes at some point. Previously, it was done when the frame completed the unload, now it will be done when it starts unloading. To achieve that, the RenderFrameProxyHost are removed when the frame starts unloading. Moreover, no new RenderFrameProxyHosts are created in a frame with an unloading current document. + 2 tests added, originally made by lukasza@chromium.org (Thanks!) Addition in the reland: ======================= + 1 regression test. A subframe is focused and unloaded, then another document commit. To prevent the previous regression, the focused frame is reset when unloading starts, instead of when it ends. Bug: 960006, 950625 Change-Id: I225118ee6385b3f843107adefe05d605d27703cd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626412 Auto-Submit: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Łukasz Anforowicz <lukasza@chromium.org> Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Commit-Queue: Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#663946}
-
danakj authored
RegisterInProcessThreads() is called to set up using single process with child processes running in threads. It must be called for: - Chrome unit tests - Android Content browser tests - Android Chrome browser tests Currently it is called in ContentBrowserTestSuite and ChromeUnitTestSuite which excludes the 3rd case. This adds a call in ChromeTestSuiteRunner, which is used to run Chrome browser tests. Bug: 961849 Change-Id: I371eb8777ba1fbe8b1dd7f4426dc15144392cad9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1610717Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#663945}
-
Peter Kasting authored
* Convert some to range-based for * Convert some to STL algorithms * int -> size_t for object counts in a few places * Other misc. cleanup, e.g. removing unnecessary {} Bug: 940126 Change-Id: I9c50e1d40cef2f09d1e8dee9b051ab34cf0c59b1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1629712 Commit-Queue: Peter Kasting <pkasting@chromium.org> Reviewed-by:
Michael Wasserman <msw@chromium.org> Auto-Submit: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#663944}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/d04aaa3a841a..0cb2fdefc219 git log d04aaa3a841a..0cb2fdefc219 --date=short --no-merges --format='%ad %ae %s' 2019-05-28 michaelludwig@google.com Use color analysis opts only if XP keeps the color FPs 2019-05-28 fmalita@chromium.org [skottie] Support multiple text fragments Created with: gclient setdep -r src/third_party/skia@0cb2fdefc219 The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. 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=kjlubick@google.com Change-Id: I1743119f19cc00c20ecfe63f691acef6fb881bfa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632802Reviewed-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@{#663943}
-
Luum Habtemariam authored
Added delegate provides the service with necessary Chrome printing stack dependencies, i.e. hooks to the CupsPrintersManager/PrinterConfigurer. Also adds a helpful fake for unit testing. Bug: chromium:945409 Test: none Change-Id: I6bb02592993fd6bb22b33240b2ae8d6e332304cb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1621326 Commit-Queue: Luum Habtemariam <luum@chromium.org> Reviewed-by:
Sean Kau <skau@chromium.org> Cr-Commit-Position: refs/heads/master@{#663942}
-
Will Harris authored
BUG=961831 Change-Id: I87ad2a4cf333ddfac7170f8309b34fcd7f71c338 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628006Reviewed-by:
Nasko Oskov <nasko@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Commit-Queue: Will Harris <wfh@chromium.org> Cr-Commit-Position: refs/heads/master@{#663941}
-
Caroline Rising authored
Tab renderer data's visible url will show the domain of the page the user is navigating to before there is a title. So at times the title would be for the page the user is navigating from while the url was for the page the user was navigating to. Using the last committed url will prevent this title and domain from being out of sync. Bug: 910739 Change-Id: I19f88d3a96ec950d37476f3287381ec2409ec17b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632593 Commit-Queue: Caroline Rising <corising@chromium.org> Reviewed-by:
Peter Boström <pbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#663940}
-
David Bokan authored
In https://crrev.com/53f9afcdecf35a8, we changed the Force Enable Zoom setting to also force reset the initial scale factor so that pages that specify an initial-scale in the viewport meta tag load fully zoomed out. Unfortunately, this caused the bug in 960518 since we always reset the initial scale factor to -1 when calling SetIgnoreViewportTagLimits. On AndroidTV devices the initial scale is overridden using SetInitialPageScaleOverride. This override would be clobbered when SetIgnoreViewportTagLimits was called (with false, to ensure the override is off). This CL fixes the issue by storing the user agent constraints when we override them, and resetting them to the original values when turning off the override. Bug: 960518,929709 Change-Id: I9d7236ec0991025067504c867fe0d06c9d12c455 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631710 Commit-Queue: David Bokan <bokan@chromium.org> Auto-Submit: David Bokan <bokan@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Cr-Commit-Position: refs/heads/master@{#663939}
-
Ian Kilpatrick authored
This was consuming an additional 160-bytes of stack. Also makes NGBlockNode::RunLegacyLayout private. Bug: 962034, 964926 Change-Id: I1e9f4b97d85b49d6262c07ae789bb984a66cc673 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631126 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#663938}
-
Mike Wasserman authored
Move wallpaper.mojom to a virtual c++ interface. Update impl and clients, make some methods sync. Combine mojo and non-mojo observer types. Add a static WallpaperController::Get(), cleanup. Bug: 958227 Test: No Chrome OS wallpaper regressions. Change-Id: I23de39efd3721f40ec423eed651f1cb8fed7edd4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626011 Commit-Queue: Michael Wasserman <msw@chromium.org> Reviewed-by:
Michael Wasserman <msw@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#663937}
-
Lan Wei authored
Instead of adding a variable to check if the test is finished, we can create a promise object and finish the test at its last callback. Bug: 606367 Change-Id: Iabf281a1fffca85630683e79436a8b442057b824 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1618002 Commit-Queue: Lan Wei <lanwei@chromium.org> Reviewed-by:
Navid Zolghadr <nzolghadr@chromium.org> Cr-Commit-Position: refs/heads/master@{#663936}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/6c8f0250717b..162eba28f207 git log 6c8f0250717b..162eba28f207 --date=short --no-merges --format='%ad %ae %s' 2019-05-28 chrome-bot@chromium.org Update config settings by config-updater. Created with: gclient setdep -r src/third_party/chromite@162eba28f207 The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel TBR=chrome-os-gardeners@google.com Change-Id: I673d0adf0d6c38beef43b87c1c6430d7c335f61f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632804Reviewed-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@{#663935}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/caa10d3db92b..21362a5cf0dc git log caa10d3db92b..21362a5cf0dc --date=short --no-merges --format='%ad %ae %s' 2019-05-28 treehugger-gerrit@google.com Merge "processor: Support arguments for nestable slices" Created with: gclient setdep -r src/third_party/perfetto@21362a5cf0dc The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=perfetto-bugs@google.com Change-Id: I16e23fcb7d57b722c0d5621042590834683f8d79 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632801Reviewed-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@{#663934}
-
Sebastien Lalancette authored
This reverts commit e61604f9. Reason for revert: Tests started failing again. Original change's description: > Re-enabled system_health.memory_mobile benchmarks > > These should be working again after > https://chromium-review.googlesource.com/c/chromium/src/+/1626991 > > TBR=perezju@chromium.org > > Bug: 964804 > Change-Id: Iddbffc36717e86db4da46cfc733821f169cf6f38 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628317 > Reviewed-by: oysteine <oysteine@chromium.org> > Commit-Queue: oysteine <oysteine@chromium.org> > Cr-Commit-Position: refs/heads/master@{#663183} TBR=oysteine@chromium.org,perezju@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 964804 Change-Id: I23caa9852a521316ec7b61369584daa45e146ff9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1630225Reviewed-by:
Sebastien Lalancette <seblalancette@chromium.org> Commit-Queue: Sebastien Lalancette <seblalancette@chromium.org> Cr-Commit-Position: refs/heads/master@{#663933}
-
yilkal authored
Bug: 948955 Change-Id: I5c98964e81984ff2fca76a0500dd297f5189f5b4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1623535Reviewed-by:
Michael Giuffrida <michaelpg@chromium.org> Commit-Queue: Yilkal Abe <yilkal@chromium.org> Cr-Commit-Position: refs/heads/master@{#663932}
-
Tao Bai authored
Change-Id: I5d5a979cb8360341c910288141394e84ebf4e2b4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1616389Reviewed-by:
Changwan Ryu <changwan@chromium.org> Reviewed-by:
Tao Bai <michaelbai@chromium.org> Commit-Queue: Tao Bai <michaelbai@chromium.org> Cr-Commit-Position: refs/heads/master@{#663931}
-
Dale Curtis authored
These should not start the reporter but are possible. Due to the statefulness of WTR this means we need a new "has valid start time" flag which controls when reporting is running. BUG=965820,967103 TEST=new unittest R=sandersd Change-Id: Ieeb125472609f2a0c3b027c9c43ab4ded7cb669a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632893 Auto-Submit: Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Dan Sanders <sandersd@chromium.org> Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#663930}
-
kdillon authored
Bug: 965236 Change-Id: Ib3451b6a6860648f640a971ba2495816f8096840 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632592 Commit-Queue: Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#663929}
-
Roman Aleksandrov authored
Change the icon of the relaunch notification. Use enterprise default icon instead of SystemMenuUpdate icon. Bug: 963883 Change-Id: I9246156160c9e7ede18298eaa89a2ebb1613e802 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1630468Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
Evan Stade <estade@chromium.org> Commit-Queue: Roman Aleksandrov <raleksandrov@google.com> Cr-Commit-Position: refs/heads/master@{#663928}
-
Xianzhu Wang authored
This further reduces back-and-forth flipping for LayoutNG, and makes it clear that inspector highlight always uses physical coordinates. Change-Id: Iecec0c03c2a1a14d8ad2aeb29f61f3a912d5d670 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1625876 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#663927}
-
Vladislav Kaznacheev authored
Bug: none Change-Id: I5faa2d53ffaf353d6209cfc68b5b0f83d6081f90 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631941 Auto-Submit: Vladislav Kaznacheev <kaznacheev@chromium.org> Reviewed-by:
Yury Khmel <khmel@chromium.org> Commit-Queue: Vladislav Kaznacheev <kaznacheev@chromium.org> Cr-Commit-Position: refs/heads/master@{#663926}
-
Dominik Laskowski authored
This CL kills content protection tasks on display reconfiguration. Clients are notified of failure, and are responsible for renewing content protection requests. Bug: 929449 Test: display_unittests Change-Id: I9eb154becd1c0fd5b8988383592f5ee1d5f135c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1597769 Commit-Queue: Dominik Laskowski <domlaskowski@chromium.org> Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Cr-Commit-Position: refs/heads/master@{#663925}
-
Scott Graham authored
ee1d5124a2bf Fix incorrect range checks in elf image note reader Bug: 967228, 967257, 967223 Change-Id: I3c6be7ab517b6f4a9c32ad2d607a2587b73d187e TBR: jperaza@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1630230 Commit-Queue: Scott Graham <scottmg@chromium.org> Auto-Submit: Scott Graham <scottmg@chromium.org> Reviewed-by:
Scott Graham <scottmg@chromium.org> Cr-Commit-Position: refs/heads/master@{#663924}
-
Tanya Gupta authored
The device picker is the second step of the share experience that allows users to choose which device to send the tab to. This CL only contains the outline for the device picker. Future CLs will add functionality, add polish, and wire it to the share sheet. Bug: 949223 Change-Id: I7ae8e3659c957acd0e33de33c4402562f577e91b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1623601Reviewed-by:
Matthew Jones <mdjones@chromium.org> Reviewed-by:
Jeffrey Cohen <jeffreycohen@chromium.org> Commit-Queue: Tanya Gupta <tgupta@chromium.org> Cr-Commit-Position: refs/heads/master@{#663923}
-
Jacob DeWitt authored
Set the origin offset reference space on initialization. Otherwise, that space will be null on the first call to onXRFrame and getViewerPose will throw an exception, preventing the page from working. Change-Id: Icf71ac3c8136e57906d01c3f8a4fdba8650f3495 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1629693 Commit-Queue: Jacob DeWitt <jacde@chromium.org> Reviewed-by:
Alexander Cooper <alcooper@chromium.org> Reviewed-by:
Klaus Weidner <klausw@chromium.org> Cr-Commit-Position: refs/heads/master@{#663922}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/material-components/material-components-ios/+log/f3f089d8833e..8d01645e5411 git log f3f089d8833e..8d01645e5411 --date=short --no-merges --format='%ad %ae %s' 2019-05-28 yarneo@gmail.com Merge branch 'release-candidate' into stable Created with: gclient setdep -r src/ios/third_party/material_components_ios/src@8d01645e5411 The AutoRoll server is located here: https://autoroll.skia.org/r/material-components-ios-chromium Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chrome.try:ios-internal-mdc TBR=bling-p10-rolls@google.com Change-Id: I21648fa87f2a1a2951b8445ee962486f6460bee8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632798Reviewed-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@{#663921}
-
Victor Vasiliev authored
https://quiche.googlesource.com/quiche.git/+log/034c98c00b23..e01dd7043f7b $ git log 034c98c00..e01dd7043 --date=short --no-merges --format='%ad %ae %s' 2019-05-21 dschinazi Clarify spdy response header log 2019-05-20 renjietang Refactor GetOrCreateStream() and GetOrCreateDynamicStream() and remove StreamHandler. 2019-05-20 fayang gfe-relnote: In QUIC, do not adjust burst token for bad bandwidth samples. Protected by gfe2_reloadable_flag_quic_conservative_bursts. 2019-05-20 renjietang Cloned from CL 231494986 by 'g4 patch'. Original change by bnc@bnc:majom-bnc-chromium-google3-headers-git5:2181:citc on 2019/01/29 16:21:02. 2019-05-20 wub gfe-relnote: (n/a) Remove parameter "reject_is_stateless" from function quic::test::crypto_test_utils::FillInDummyReject. Test only. 2019-05-20 rch Move the QuicEpollServerFactory out of quic_simple_server_bin. 2019-05-20 dschinazi Do not send retry token on non-initial packets 2019-05-20 dschinazi Rename connection_id to server_connection_id Created with: roll-dep src/net/third_party/quiche/src R=rch@chromium.org Change-Id: I8e9a18cc23d7c6559758e4e4620907e30eea081a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631869 Commit-Queue: Victor Vasiliev <vasilvv@chromium.org> Reviewed-by:
Ryan Hamilton <rch@chromium.org> Cr-Commit-Position: refs/heads/master@{#663920}
-
Ken Rockot authored
There is a need to express localizable strings in //services code. This CL introduces all the bits necessary to define translated resources in a new //services/services_strings.grd file and moves a single string (pertaining only to a service defined in //services) from the Chrome GRD to the services GRD. This is a precursor to simplifying expression of out-of-process service registration by allowing service manifests to include a resource ID directly in their definition. Bug: 895615, 915806 Change-Id: I76d420266fb5528f407b624838172c267666654b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1615701Reviewed-by:
Nico Weber <thakis@chromium.org> Commit-Queue: Ken Rockot <rockot@google.com> Cr-Commit-Position: refs/heads/master@{#663919}
-
Vikas Soni authored
As per the spec, the driver is expected to return a valid timestamp from the call eglGetFrameTimestampsANDROID() when its not EGL_TIMESTAMP_PENDING_ANDROID or EGL_TIMESTAMP_INVALID_ANDROID. But currently few buggy drivers returns an invalid timestamp 0. We fix/workaround this in chrome by returning the presentation time as TimeTicks::Now() (snapped to the next vsync) instead of 0. Bug: 966638 Change-Id: I5075dda0739f02029922ebbc20c09656fb0e87ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631354Reviewed-by:
Antoine Labour <piman@chromium.org> Commit-Queue: vikas soni <vikassoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#663918}
-
Alex Cooper authored
When an input_source is marked as removed, its gamepad needs to also be marked as disconnected. To facilitate writing tests for this, the blink web_test mocks were also updated to allow for connecting/disconnecting a gamepad object. Also includes very minor cleanup to the test that was used as a pattern when creating the newly added web_test. Bug: 963013 Change-Id: Ia985b548dbc6b1e7052a6189a484b6a93298e2b7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626885Reviewed-by:
Bill Orr <billorr@chromium.org> Commit-Queue: Alexander Cooper <alcooper@chromium.org> Cr-Commit-Position: refs/heads/master@{#663917}
-
Vladislav Kaznacheev authored
Bug: none Change-Id: I05f25bc8f472d44660a8f98fb3b92b32ceebf3c8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631940 Commit-Queue: Vladislav Kaznacheev <kaznacheev@chromium.org> Commit-Queue: Xiyuan Xia <xiyuan@chromium.org> Auto-Submit: Vladislav Kaznacheev <kaznacheev@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#663916}
-
Tommy C. Li authored
This "Turn off" button just resets the content setting to the default setting, which is now BLOCK. Bug: 965760 Change-Id: I32002bfdcad61ee36041d1ecb733b4cdc52981ce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1629041 Commit-Queue: Tommy Li <tommycli@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#663915}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/7eadbd640fc4..12d7da217249 git log 7eadbd640fc4..12d7da217249 --date=short --no-merges --format='%ad %ae %s' 2019-05-28 thestig@chromium.org Remove CPDF_Array::GetFloatAt(). 2019-05-28 thestig@chromium.org Roll buildtools/ c79f3482c..0218c0f9a (18 commits; 5 trivial rolls) 2019-05-28 thestig@chromium.org Roll build/ 578c66146..4cebfa34c (159 commits) 2019-05-28 thestig@chromium.org Roll tools/code_coverage/ 90f3a1ede..b53d904eb (1 commit) 2019-05-28 thestig@chromium.org Roll tools/clang/ 2db48c749..9d46446d5 (6 commits) 2019-05-28 thestig@chromium.org Roll tools/clang/ 4e32649d7..2db48c749 (24 commits) 2019-05-28 thestig@chromium.org Roll third_party/catapult/ cca9447f6..a7b331246 (73 commits) 2019-05-28 thestig@chromium.org Roll third_party/depot_tools/ ccd2b4da9..26af0d34d (112 commits; 68 trivial rolls) 2019-05-28 thestig@chromium.org Roll third_party/icu/ ae4b77dc8..64e5d7d43 (4 commits) 2019-05-28 thestig@chromium.org Roll third_party/binutils/ 2be73f7fb..92bfa0a5d (1 commit) 2019-05-28 thestig@chromium.org Roll third_party/googletest/src/ 9997a830e..f71fb4f9a (8 commits) 2019-05-28 thestig@chromium.org Roll v8/ ed14aba38..c4c480a41 (655 commits) Created with: gclient setdep -r src/third_party/pdfium@12d7da217249 The AutoRoll server is located here: https://autoroll.skia.org/r/pdfium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=pdfium-deps-rolls@chromium.org Change-Id: Ia7c442f48a6df03779ea7b8254a8659a40e4a07d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632797Reviewed-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@{#663914}
-
Mohamed Amir Yosef authored
Recent UMA metrics suggest that AddLoginSync() unexpectedly fails to add remote passwords the password manager when processing remote passwords from the server. This CL is introducing a UMA metric to record the exact reason of failure. Bug: 902349 Change-Id: I71eaf22c35211f363123f21ef2d8dd78085206bc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1630478Reviewed-by:
Brian White <bcwhite@chromium.org> Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org> Cr-Commit-Position: refs/heads/master@{#663913}
-
Aaron Gable authored
This CL does a few things to unify the usage of minimal_symbols throughout mb_config.pyl: 1) It turns it on for all Goma mac builds, to match Win and other platforms 2) It removes it from configs which also specify release_trybot, where it is redundant 3) It renames a couple configs to better reflect their unique pieces Bug: 966342 Change-Id: I6e12efbbe981e8eccbaa831430f8d833bd90e715 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628815 Commit-Queue: Aaron Gable <agable@chromium.org> Reviewed-by:
John Budorick <jbudorick@chromium.org> Cr-Commit-Position: refs/heads/master@{#663912}
-
Vladimir Levin authored
With display locking, the subtree we have might not be laid out, and is not visible. Hence, we should not generate subtree intersection observations. This patch implements this by skipping computation for locked subtree elements. R=chrishtr@chromium.org, rakina@chromium.org, szager@chromium.org Bug: 945531 Change-Id: Iab4b91eb0c964a369901bc4ec322f4a421a8103f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614029Reviewed-by:
Stefan Zager <szager@chromium.org> Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#663911}
-
Christopher Cameron authored
These filed belonged "with the remote cocoa stuff", but at the time there was no such place, or that place was tied to views, which didn't seem right. Now there is a "remote cocoa stuff for the browser process" place (well, created by this patch). Move the things that belong in that place to that place. R=ellyjones TBR=avi (content/) Bug: 958255 Change-Id: I168a259403756cb429f772618161946373470db3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1629042 Commit-Queue: ccameron <ccameron@chromium.org> Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#663910}
-
Daniel Rubery authored
This reverts commit 1ffb9166. Since we are coming up on the M76 branch point, restore the ZIP extraction size limit. I'll roll this out when M75 is released, fixing the bug. Bug: 959628 Change-Id: Iba156644101a1297cf03a129eea756020efe7fbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631895Reviewed-by:
Nathan Parker <nparker@chromium.org> Commit-Queue: Daniel Rubery <drubery@chromium.org> Cr-Commit-Position: refs/heads/master@{#663909}
-
Xianzhu Wang authored
With it we can know the associated blink-side identity of the cc layer, e.g. the GraphicsLayer, DOM node, etc. It also gives ForeignLayerDisplayItems meaningful debug names. TBR=kylechar@chromium.org (for ui/compositor because of added 'const in a cc::LayerClient method) Change-Id: I52f1839b406439fa2cf5b0a203a4e1f88929c345 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1629292 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
kylechar <kylechar@chromium.org> Reviewed-by:
Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#663908}
-