- 03 Jan, 2019 40 commits
-
-
Marcin Wiacek authored
This is part of changes which put as goal removing redundant ChromeAnimation API by moving everything into CompositorAnimator. Public doc with proposal: https://docs.google.com/document/d/1VL5ntE7vn267IFjE4Zke0GkhVVTHz1bEP672Apj_E2k/edit This concrete patch is migrating StackLayoutBase. BUG=890643 Change-Id: I66668b9373c54fc9573de8d797990b6e291f2b54 Reviewed-on: https://chromium-review.googlesource.com/c/1376851Reviewed-by:
Changwan Ryu <changwan@chromium.org> Commit-Queue: Marcin Wiącek <marcin@mwiacek.com> Cr-Commit-Position: refs/heads/master@{#619739}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/c63ddb2a3f9a..3f2b9aad4a05 git log c63ddb2a3f9a..3f2b9aad4a05 --date=short --no-merges --format='%ad %ae %s' 2019-01-03 srte@webrtc.org Moves logged event structs to separate header. 2019-01-03 yinwa@webrtc.org Bugfix: Activate pushback on every sent packet. 2019-01-03 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 86bff8b8..adf0af4d (619523:619625) 2019-01-03 hta@webrtc.org Add an observer API for DTLSTransport events. 2019-01-03 minyue@webrtc.org Use ordered data structure for supported frame lengths in ANA. 2019-01-03 nisse@webrtc.org Convert peerconnection_client to use VcmCapturer 2019-01-03 nisse@webrtc.org Update unityplugin to use VcmCapturer. 2019-01-02 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision d189a954..86bff8b8 (619409:619523) Created with: gclient setdep -r src/third_party/webrtc@3f2b9aad4a05 The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-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:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng BUG=chromium:None,chromium:None,chromium:907849,chromium:None TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I9eb6c6869d7c551064e241d794ecd60715e660b0 Reviewed-on: https://chromium-review.googlesource.com/c/1394686Reviewed-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@{#619738}
-
Becca Hughes authored
Notifies the mojo observer from content::MediaSessionImpl when the supported actions change. BUG=892771 Change-Id: Iea1edf130b415d44ab9f32f7b6506d53f4558280 Reviewed-on: https://chromium-review.googlesource.com/c/1379917Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Commit-Queue: Becca Hughes <beccahughes@chromium.org> Cr-Commit-Position: refs/heads/master@{#619737}
-
Peter Kasting authored
Bug: 331924, 603562, 626761, 837219 Change-Id: If2695993d98dc00168c367c3c171b99a96eb7bc5 Reviewed-on: https://chromium-review.googlesource.com/c/1351809 Commit-Queue: Peter Kasting <pkasting@chromium.org> Reviewed-by:
Allen Bauer <kylixrd@chromium.org> Cr-Commit-Position: refs/heads/master@{#619736}
-
Danyao Wang authored
Change-Id: I8f2cfb66099a3bf8bd03f3407ed763067a465f01 Reviewed-on: https://chromium-review.googlesource.com/c/1394883 Commit-Queue: Danyao Wang <danyao@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#619735}
-
chromium-autoroll authored
The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-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:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast TBR=cr-fuchsia+bot@chromium.org Change-Id: Idb57ebf1ea2981b717cb9712ad86dda8c7ed0c3b Reviewed-on: https://chromium-review.googlesource.com/c/1394797Reviewed-by:
-
Xianzhu Wang authored
This is a reland of crrev.com/618316 which was reverted in crrev.com/619326 because of performance regression. This patch changed the condition in PrePaintTreeWalk::WalkTree() from if (root_frame_view.GetLayoutView()->Layer()->NeedsRepaint()) to if (needs_invalidate_chrome_client_). needs_invalidate_chrome_client_ is set by PaintInvalidator. The problem of previous code was that NeedsRepaint() is always true if the document doesn't update lifecycle to paint which is the case for the subdocument of SVGImage, causing infinite invalidation of the chrome client. Original change's description: > Revert "[CompositeAfterPaint] Invalidate chrome client when needed" > > This reverts commit 29021ede. > > Reason for revert: Suspect performance regression > > Bug: 918276 > > Original change's description: > > [CompositeAfterPaint] Invalidate chrome client when needed > > > > For pre-CompositeAfterPaint, we call InvalidateChromeClient() > > when an object is invalidated in a view referenced from a plugin or > > an svg-image. > > > > Now let the path also work for CompositeAfterPaint. > > > > This fixes several web plugin tests for CompositeAfterPaint. > > > > Bug: 524134 > > Change-Id: Ia4c3ccba4632ddcdfdfdfec299fb7a68440a1419 > > Reviewed-on: https://chromium-review.googlesource.com/c/1385112 > > Reviewed-by: Philip Rogers <pdr@chromium.org> > > Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#618316} > > TBR=wangxianzhu@chromium.org,pdr@chromium.org > > # Not skipping CQ checks because original CL landed > 1 day ago. > > Bug: 524134 > Change-Id: I9b4f67a74732919ba23acc00fd501d45baa498e6 > Reviewed-on: https://chromium-review.googlesource.com/c/1392439 > Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> > Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> > Cr-Commit-Position: refs/heads/master@{#619326} Bug: 918276, 524134 Change-Id: Ifad1c2eb8bdddcceea26a286c3309665f6d94c1a Reviewed-on: https://chromium-review.googlesource.com/c/1393558Reviewed-by:
Philip Rogers <pdr@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#619733}
-
Lindsay Pasricha authored
Creating 2 prototype tests using EG2 with the smoke_egtest suite. The plan for migrating to EG2 is outlined at go/chrome-eg2-migration. - Added the earl_grey2:all_tests as a build target - Added the ios/chrome/test/earl_grey2 directory with BUILD and gni files - Added the prototype smoke_test suite with 2 test cases - Added the chrome_earl_grey_edo .h/mm files for the EDO helpers - Tweaked and reorganized ios/third_party/earl_grey2/ BUILD and gni files. Bug: 906201 Change-Id: I6521af6403ac9e4b320cba25f390be88522a0678 Reviewed-on: https://chromium-review.googlesource.com/c/1352532 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Reviewed-by:
Justin Cohen <justincohen@chromium.org> Cr-Commit-Position: refs/heads/master@{#619732}
-
Raul Tambre authored
Bug: 766891 Change-Id: Ib8cf38fb63d9494f21462ab55ce361775b107322 Reviewed-on: https://chromium-review.googlesource.com/c/1390003Reviewed-by:
Antoine Labour <piman@chromium.org> Reviewed-by:
Bill Budge <bbudge@chromium.org> Reviewed-by:
Lambros Lambrou <lambroslambrou@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/eb333167..b4e2270d Please follow these instructions for assigning/CC'ing issues: https://github.com/v8/v8/wiki/Triaging%20issues 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;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I218b75e19cb3322712e550ee9a9f13d96b545637 Reviewed-on: https://chromium-review.googlesource.com/c/1394789Reviewed-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@{#619730}
-
liberato@chromium.org authored
This CL adds SupportedVideoDecoderConfig to match the mojom struct. It also adds a struct traits for them, and converts the existing mojo code to use the media:: rather than the mojom:: version. This will make it easier for {D3D11, MediaCodec}VideoDecoder to return their media::SupportedVideoDecoderConfigs, since they cannot use mojo directly. Bug: 918029 Change-Id: Id0403ccadaa1b3fbbb310f01fd9b3a7bebc92ba7 Reviewed-on: https://chromium-review.googlesource.com/c/1392350 Commit-Queue: Frank Liberato <liberato@chromium.org> Reviewed-by:Dan Sanders <sandersd@chromium.org> Reviewed-by:
Xiaohan Wang <xhwang@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#619729}
-
Tim Zheng authored
To set a Crostini app scaled is to set the property in the Crostini app registry so that when the app launches it'll use low display density. BUG=chromium:839242 TEST=unit test included in this CL Change-Id: I1428a49cce918930f8b5d4083fbc9ba208e8b101 Reviewed-on: https://chromium-review.googlesource.com/c/1393547 Commit-Queue: Tim Zheng <timzheng@chromium.org> Reviewed-by:
Ben Wells <benwells@chromium.org> Reviewed-by:
Dan Erat <derat@chromium.org> Cr-Commit-Position: refs/heads/master@{#619728}
-
Manu Cornet authored
Shelf items used to be aligned directly after the launcher button, so it made sense to include everything within bounds where tooltips should not hide to avoid hiccups. However, now that we show centered shelf items, this means that a tooltip can be shown all over a possibly quite large amount of white space between the launcher button and the first shelf item. 1) It is very strange to show a tooltip over such a potentially large piece of shelf. 2) On the other hand, when it does happen that the first shelf item is close to the launcher button, not showing a tooltip in the space between them does mean a slight stutter when hovering from one to the next. The drawbacks of 1) clearly outweigh the ones of 2), so this change hides tooltips between the launcher button and the first shelf item. Bug: 896524 Change-Id: I06e666ba0296881f87c2cf3ce5972b38d638c3f7 Reviewed-on: https://chromium-review.googlesource.com/c/1393889 Commit-Queue: Manu Cornet <manucornet@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#619727}
-
Tomasz Wiszkowski authored
Overlooked in crrev/c/1393888 Bug: 918877, 918335 Change-Id: I4c4f0274eefd0b23d449390699f673e061653b48 Reviewed-on: https://chromium-review.googlesource.com/c/1394784 Commit-Queue: Tomasz Wiszkowski <ender@google.com> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Cr-Commit-Position: refs/heads/master@{#619726}
-
Tommy Steimel authored
Example failure: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac10.13%20Tests%20%28dbg%29/7897 Bug: 918905 Change-Id: I3ab6874fb5380d8f369e03f3d0837edff8eacbeb Reviewed-on: https://chromium-review.googlesource.com/c/1394799Reviewed-by:
Becca Hughes <beccahughes@chromium.org> Commit-Queue: Tommy Steimel <steimel@chromium.org> Cr-Commit-Position: refs/heads/master@{#619725}
-
Elly Fong-Jones authored
The existing code used FocusedBorderColor, which happened to be equal to ProminentButtonColor on non-Mac and close enough on Mac that nobody noticed the disparity. Mojave changed the color that underlies FocusedBorderColor, which made checkboxes start drawing very faintly. Bug: 918673 Change-Id: If73a4607bb5857e4b61d67cfd7e9f58ebd341021 Reviewed-on: https://chromium-review.googlesource.com/c/1394434Reviewed-by:
Michael Wasserman <msw@chromium.org> Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#619724}
-
Tarun Bansal authored
Metrics review doc: http://shortn/_GsufFKsadl Change-Id: Iffd9002ed43586608d4c224602d8405911956a64 Bug: 893923 Reviewed-on: https://chromium-review.googlesource.com/c/1387554Reviewed-by:
Bryan McQuade <bmcquade@chromium.org> Commit-Queue: Tarun Bansal <tbansal@chromium.org> Cr-Commit-Position: refs/heads/master@{#619723}
-
Esmael El-Moslimany authored
Bug: 862839 Change-Id: I3499e9c6abe18c0ffb23a4ed3598320edf757570 Reviewed-on: https://chromium-review.googlesource.com/c/1392063 Commit-Queue: Esmael El-Moslimany <aee@chromium.org> Reviewed-by:
Dan Beam <dbeam@chromium.org> Reviewed-by:
Hector Carmona <hcarmona@chromium.org> Cr-Commit-Position: refs/heads/master@{#619722}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/9f36c8bb721d..241644a5a398 git log 9f36c8bb721d..241644a5a398 --date=short --no-merges --format='%ad %ae %s' 2019-01-03 stevenperron@google.com Have replace load size handle extact with no index. (#2261) Created with: gclient setdep -r src/third_party/SPIRV-Tools/src@241644a5a398 The AutoRoll server is located here: https://autoroll.skia.org/r/spirv-tools-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=dsinclair@chromium.org Change-Id: I5c00330ca5e6233f070b39959cc0e748a5f927c7 Reviewed-on: https://chromium-review.googlesource.com/c/1394689Reviewed-by:
-
Justin Cohen authored
Nobody appears to use this and it will be removed in the future. Change-Id: I3caadee3e4f4cec2a2f0d9e4d8717f9b1a16afe6 Reviewed-on: https://chromium-review.googlesource.com/c/1394704 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#619720}
-
Charlie Andrews authored
TBR=nyquist@chromium.org Bug: 918874 Change-Id: I45eaab1c4f4ba92d6a90f2826b92fa3c3eb37774 Reviewed-on: https://chromium-review.googlesource.com/c/1394823Reviewed-by:
Charlie Andrews <charliea@chromium.org> Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Commit-Queue: Charlie Andrews <charliea@chromium.org> Cr-Commit-Position: refs/heads/master@{#619719}
-
Steven Bennetts authored
For header file moves in src/chrome: TBR=sky@chromium.org Bug: 918682 Change-Id: I2cc795ada277560503aa4183075a94825d876c54 Reviewed-on: https://chromium-review.googlesource.com/c/1394003Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
-
John Chen authored
This is a reland of 70ffd447 Original change was reverted due to test flakiness on Mac, caused by: * Pause time often goes above the upper limit of 300 ms, sometime more than double the limit. * Occasionally the first event is missing. The following changes are made to improve test reliability: * Remove the check of an upper limit for the pause time. With the wide range of actual pause time, there appears to be no feasible upper limit to use. * The first significant event is now pointer down instead of key down, to ensure that the target element receives focus. The previous dependence on autofocus attribute appears to be unreliable. * Change mouse button from 1 (middle) to 0 (left), as the middle mouse button triggers paste on some platforms. (It was a typo.) Original change's description: > [ChromeDriver] Handle pauses in Perform Actions > > W3C spec allows the app to specify pauses within Perform Actions command > (https://w3c.github.io/webdriver/#dfn-dispatch-actions). Updating > ChromeDriver to handle these pauses. > > Bug: chromedriver:1897 > Change-Id: I533179f4a9f2216bfacf0f4fdb539c8f898bed07 > Reviewed-on: https://chromium-review.googlesource.com/c/1392281 > Commit-Queue: John Chen <johnchen@chromium.org> > Reviewed-by: Caleb Rouleau <crouleau@chromium.org> > Cr-Commit-Position: refs/heads/master@{#619506} Bug: chromedriver:1897 Change-Id: I38122bdc01965345421429b1d2f45374395b0cc7 Reviewed-on: https://chromium-review.googlesource.com/c/1394786Reviewed-by:
Caleb Rouleau <crouleau@chromium.org> Commit-Queue: John Chen <johnchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#619717}
-
Paul Irish authored
Change-Id: I8005904bdc042ad4ac709edcc371256a075cde1b Reviewed-on: https://chromium-review.googlesource.com/c/1393427Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Paul Irish <paulirish@chromium.org> Cr-Commit-Position: refs/heads/master@{#619716}
-
Sergey Ulanov authored
zircon.ethernet was renamed to fuchsia.hardware.ethernet last week, but zircon/ethernet/cpp/fidl.h was still included in network_interfaces_fuchsia.cc. TBR=wez@chromium.org Bug: 918797 Change-Id: I83409d7b5aeb06599a5b89f6400a09704b498fd6 Reviewed-on: https://chromium-review.googlesource.com/c/1394169Reviewed-by:
Wez <wez@chromium.org> Reviewed-by:
Fabrice de Gans-Riberi <fdegans@chromium.org> Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Commit-Queue: Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#619715}
-
Max Moroz authored
TEST=tools/code_coverage/coverage_test.py Bug: 869451 Change-Id: I29423a45d6542e358e7157bc6af7f9208969a436 Reviewed-on: https://chromium-review.googlesource.com/c/1394594 Commit-Queue: Max Moroz <mmoroz@chromium.org> Reviewed-by:
Yuke Liao <liaoyuke@chromium.org> Cr-Commit-Position: refs/heads/master@{#619714}
-
Rayan Kanso authored
Use consistent annotation style in content/browser/background_fetch/... Style guide: https://google.github.io/styleguide/cppguide.html#Function_Argument_Comments Style used: /* param_name= */ $prvalue Done using the following regex swap + some manual fixes for outliers: - ([^\s{\(]+)\s/\*\s([\w\_]+)\s\*/ - /* $2= */ $1 Change-Id: Id68329cad6ae520f84e9f3ecb6c31f4a39480e36 Reviewed-on: https://chromium-review.googlesource.com/c/1388149 Commit-Queue: Rayan Kanso <rayankans@chromium.org> Reviewed-by:
Mugdha Lakhani <nator@chromium.org> Cr-Commit-Position: refs/heads/master@{#619713}
-
Matt Simmons authored
R=asvitkine@chromium.org, yusufo@chromium.org Bug: 916818 Change-Id: Ie703332daf193dec69b3bff5c0686f84886422dc Reviewed-on: https://chromium-review.googlesource.com/c/1393453 Commit-Queue: Matt Simmons <mattsimmons@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Cr-Commit-Position: refs/heads/master@{#619712}
-
Joshua Peraza authored
Overview: This CL disables Breakpad for Chrome, Content Shell, WebView, and Chromecast on Android and replaces it with Crashpad. When a crash signal is received, the browser forks+execs a Crashpad handler process either for itself or on behalf of a crashing child to create a crash dump. components/crash/ - Remove CrashDumpManager. Minidump creation is handled entirely by Crashpad. - Remove OnChildStart from ChildExitObserver as it is no longer necessary. - ChildExitObserver observers CrashHandlerHost to be notified when child processes receive crash signals. - De-duplicate calls to ChildExitObserver::Client::OnChildExit when NOTIFICATION_RENDER_PROCESS_{CLOSED, TERMINATED} are both sent. components/minidump_uploader/ - Uploaders expect crash reports to already be MIME encoded since Breakpad was doing that in a signal handler call-back. CrashFileManager now automatically calls into native code to do the encoding and write to a directory of crash reports whenever it checks for reports without logcats. chrome/app/*.{cc,h} chrome/browser/*.cc content/shell/app/*.{cc,h} content/shell/browser/*.cc - Initialize Crashpad instead of Breakpad, with minor cleanup and adjustment for changes to CrashDumpObserver. chrome/browser/metrics/oom/out_of_memory_reporter_unittest.cc - Simulate crashes/exits with NOTIFICATION_RENDER_PROCESS_{CREATED, CLOSED} and signals sent to ChildExitObserver instead of a crash dump. android_webview/ - AwBrowserTerminator now observes child process crashes via ChildExitObserver rather than its own pipe. - Crashpad always produces minidumps, and not microdumps. - Disabling Crashpad is not yet supported. chromecast/ - There are now two directories that crash report uploaders should be aware of: "Crashpad" contains a database of raw minidumps produced by Crashpad, and "Crash Reports" contains MIME encoded minidumps. MIME encoding is performed by a CrashReportMimeWriter in CastCrashUploader.java:checkForCrashDumps(). TBR=yfriedman@chromium.org,peter@chromium.org,isherman@chromium.org,jam@chromium.org,wnwen@chromium.org,torne@chromium.org,halliwell@chromium.org,tobiasjs@chromium.org,rsesek@chromium.org,sanfin@chromium.org,jperaza@chromium.org,mark@chromium.org Bug: crashpad:30 Change-Id: Ib1b0fe085272a7e1e4a91462add50e41eecad746 Cq-Include-Trybots: master.tryserver.chromium.android:android_compile_x64_dbg;master.tryserver.chromium.android:android_compile_x86_dbg Reviewed-on: https://chromium-review.googlesource.com/c/1388654 Commit-Queue: Joshua Peraza <jperaza@chromium.org> Reviewed-by:Mark Mentovai <mark@chromium.org> Reviewed-by:
Luke Halliwell <halliwell@chromium.org> Cr-Commit-Position: refs/heads/master@{#619711}
-
Steven Valdez authored
https://boringssl.googlesource.com/boringssl/+log/4cce955d1487b5bd2b3c03ead986558649cdaadf..8e8f250422663106d478f6927beefba289a95b37 Bug: none Change-Id: Ifa87db808efd939abfb388c32f544e7510b70a63 Reviewed-on: https://chromium-review.googlesource.com/c/1393016Reviewed-by:
David Benjamin <davidben@chromium.org> Commit-Queue: Steven Valdez <svaldez@chromium.org> Cr-Commit-Position: refs/heads/master@{#619710}
-
Tom Anderson authored
These should no longer be necessary now that Desktop Linux uses ChromeOS-styled frame buttons. BUG=911770 R=sky Change-Id: I79ae8a5173e7be7e050ba84220700c47ea6515cc Reviewed-on: https://chromium-review.googlesource.com/c/1394303Reviewed-by:
-
Juan Antonio Navarro Perez authored
TBR=sullivan@chromium.org Bug: 914390 Change-Id: I2cfe83fef58ea0f6c7a123c662ccfd5dd875aa5e Reviewed-on: https://chromium-review.googlesource.com/c/1394393Reviewed-by:
Juan Antonio Navarro Pérez <perezju@chromium.org> Commit-Queue: Juan Antonio Navarro Pérez <perezju@chromium.org> Cr-Commit-Position: refs/heads/master@{#619708}
-
Cathy Li authored
Bug: 918436 Change-Id: I5311199b6dff15400d36308c35dbf7aa9469be98 Reviewed-on: https://chromium-review.googlesource.com/c/1392501 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@{#619707}
-
Tom McKee authored
The 'newtab' and 'omnibox' stories aren't run against Android_Webview because they don't make sense in that context. Since those stories don't run against Android_Webview we don't need entries in expectations.config to disable those stories on that platform. Bug: 867568 Change-Id: Ifcd38f0bc5ace5fddc0d883e24b89b06d1f84ef6 Reviewed-on: https://chromium-review.googlesource.com/c/1392734 Commit-Queue: Tom McKee <tommckee@chromium.org> Reviewed-by:
-
Alexei Svitkine authored
This is triggered by the cloned install detector here: https://cs.chromium.org/chromium/src/components/metrics/cloned_install_detector.cc?rcl=4c806b8b802c5bcd93831229bedd8164d8a68a26&l=82 Bug: 866722 Change-Id: Ic0c99bdceee10413949f71f965d1b4edb9006466 Reviewed-on: https://chromium-review.googlesource.com/c/1392348Reviewed-by:
Paul Miller <paulmiller@chromium.org> Commit-Queue: Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#619705}
-
Hector Carmona authored
Having URLs in GRD files can be error-prone. Bug: NONE Change-Id: I5d9bb6cb768fdad2bcea3cb1998ad636b83a072a Reviewed-on: https://chromium-review.googlesource.com/c/1391426Reviewed-by:
-
Troy Hildebrandt authored
The metadata database is primarily for storing corruption information at the moment. Adds the creation/loading of entries from the metadata DB on shared database init, and causes the database load to fail if metadata can't be loaded, since that would be potentially dangerous. Adds an async check for corruption information during SharedProtoDatabaseClient init, and sets the corruption flag accordingly so IsCorrupt() is correct. Bug: 870813 Change-Id: Id24cd2c5c2aeed21d0e8bb108cc4126c3acb3049 Reviewed-on: https://chromium-review.googlesource.com/c/1356224 Commit-Queue: Troy Hildebrandt <thildebr@chromium.org> Reviewed-by:
-
Sam Maier authored
This is a reland of 09f15bdb Original change's description: > Android: Turning on R8 instead of Proguard for public targets > > We are in the process of migrating to R8 to replace Proguard. This is > the first step - move all usages of Proguard in public targets to R8. > > Some refactorings were natural with the few forced changes this caused. > > TBR=smaier > > Bug: 908988, 913554 > Change-Id: I2139919598fba1643d7560dc5557d5efb9a5887c > Reviewed-on: https://chromium-review.googlesource.com/c/1357306 > Reviewed-by: Sam Maier <smaier@chromium.org> > Reviewed-by: agrieve <agrieve@chromium.org> > Commit-Queue: Sam Maier <smaier@chromium.org> > Cr-Commit-Position: refs/heads/master@{#619471} TBR=proguard.flags(smaier) Bug: 908988, 913554 Change-Id: I93690ad2a6838025221b7fab4b0bee1b06c920c9 Reviewed-on: https://chromium-review.googlesource.com/c/1394387 Commit-Queue: Sam Maier <smaier@chromium.org> Reviewed-by:
Peter Wen <wnwen@chromium.org> Reviewed-by:
agrieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#619702}
-
Mitsuru Oshima authored
* Don't use root window as transient parent in test. * Don't create WindowState before adding to parent intest. Instead set the window show type to specify the maximized state. These are preparations to limit WindowState to specific containers. Bug: 912191 Test: no functional change. all tests should pass. Change-Id: Ic4587153395552eb140f06d440c5df7afb5b689a Reviewed-on: https://chromium-review.googlesource.com/c/1387839 Commit-Queue: Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#619701}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/4627b3705d59..9fa54eab2590 git log 4627b3705d59..9fa54eab2590 --date=short --no-merges --format='%ad %ae %s' 2019-01-03 jmadill@chromium.org Optimize and inline more validation. Created with: gclient setdep -r src/third_party/angle@9fa54eab2590 The AutoRoll server is located here: https://autoroll.skia.org/r/angle-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: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_optional_gpu_tests_rel TBR=syoussefi@chromium.org Change-Id: I92262e57f5edc7ff4f7f4dcc296d90fd1ec2c483 Reviewed-on: https://chromium-review.googlesource.com/c/1394685Reviewed-by:
-
