- 01 Feb, 2019 40 commits
-
-
Paul Meyer authored
This patch adds a "Frobulate" feature policy to test being controlled via the Frobulate sample origin trial. Bug: 925097 Change-Id: I8f85926546dc0eafd3f882273af87bbc79a321b2 Reviewed-on: https://chromium-review.googlesource.com/c/1435534 Commit-Queue: Paul Meyer <paulmeyer@chromium.org> Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Reviewed-by:
Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#628441}
-
Harley Li authored
In Application's Clear Storage panel, when the current site is invalid, e.g. localhost:5000 (no server running there), the 'clear site data' button should be deactivated, and the subtitle for this panel should not display the security origin address. Component 'ParsedURL' has the ability to tell whether the url is valid. Bug: 915703, 919857 Change-Id: I41f6079bbef299d284b36815d3888e3cec1e0050 Reviewed-on: https://chromium-review.googlesource.com/c/1447317Reviewed-by:
Joel Einbinder <einbinder@chromium.org> Commit-Queue: Haihong Li (Harley) <hhli@chromium.org> Cr-Commit-Position: refs/heads/master@{#628440}
-
David 'Digit' Turner authored
This is only used to get rid of an annoying issue where third_party/android_tools/sdk/platform-tools/package.xml appears as an untracked file, because it was not properly listed in its .gitgnore file. See https://chromium-review.googlesource.com/c/1449574 R=agrieve@chromium.org, jbudorick@chromium.org BUG=NONE Change-Id: I93e830a4e75e4ed28d597e7a79fd306f1bf192af Reviewed-on: https://chromium-review.googlesource.com/c/1449667Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: David Turner <digit@chromium.org> Cr-Commit-Position: refs/heads/master@{#628439}
-
Aaron Leventhal authored
Bug: 903588 Change-Id: Ie33670e71e91ec992ea51fc8e1fa2a0416698a91 Reviewed-on: https://chromium-review.googlesource.com/c/1450233 Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Commit-Queue: Nektarios Paisios <nektar@chromium.org> Reviewed-by:
Nektarios Paisios <nektar@chromium.org> Cr-Commit-Position: refs/heads/master@{#628438}
-
Chris Lu authored
Add delegate for FindInPageManager. CreateFindInpageManagerTest to test it's behavior. Add property inFindInPageManagerImpl to keep track of total matches in a find. Bug: 896867 Change-Id: I0c4b951c898eb8f3f91562a564db369b66afa78e Reviewed-on: https://chromium-review.googlesource.com/c/1436946 Commit-Queue: Chris Lu <thegreenfrog@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Reviewed-by:
Mike Dougherty <michaeldo@chromium.org> Cr-Commit-Position: refs/heads/master@{#628437}
-
Christian Fremerey authored
Flakiness was caused by it not being deterministic whether or not adding and removing virtual devices to/from the video capture service would actually take effect before the Renderer requesting to enumerate devices. The fix is to wait for the service to send a confirmation before proceeding to enumerate in the Renderer. Test: content_browsertests --gtest_filter=WebRtcVideoCaptureServiceEnumerationBrowserTest* Bug: 885256, 927714 Change-Id: If942900c419244454378fe6d53f5bb524207ff03 Reviewed-on: https://chromium-review.googlesource.com/c/1450392Reviewed-by:
Weiyong Yao <braveyao@chromium.org> Commit-Queue: Christian Fremerey <chfremer@chromium.org> Cr-Commit-Position: refs/heads/master@{#628436}
-
Azeem Arshad authored
This CL adds some logic to AndroidSmsAppSetupController so that when removing the PWA, a cookie will be set on the old domain to indicate the status of the migration. This will allow the client to redirect users to new url. We also attempt to remove this cookie when installing the PWA so that the client won't redirect inside the PWA in a rollback case. Bug: 927472 Change-Id: Ia11ce407b2140242c6746d2b28e39d229dff58d4 Reviewed-on: https://chromium-review.googlesource.com/c/1448984 Commit-Queue: Azeem Arshad <azeemarshad@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Reviewed-by:
Jeremy Klein <jlklein@chromium.org> Cr-Commit-Position: refs/heads/master@{#628435}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/0e08d5911290..7da523216533 git log 0e08d5911290..7da523216533 --date=short --no-merges --format='%ad %ae %s' 2019-02-01 thestig@chromium.org Add CFX_Font::kUntitledFontName. Created with: gclient setdep -r src/third_party/pdfium@7da523216533 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=dsinclair@chromium.org Change-Id: Iaf2a22a6d616faf5e34021f13dd99da2e3086c40 Reviewed-on: https://chromium-review.googlesource.com/c/1450314Reviewed-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@{#628434}
-
kylechar authored
This software output device implementation created a child window to draw into from the GPU process. This was to prevent some flashes in the blank areas of the window on resize. While investigating https://crbug.com/924975 it seems like drawing directly into the browser HWND no longer causes any issues on Windows 7 or 10. Drawing directly in the browser HWND also fixes the bug where we aren't redrawing exposed regions on Windows 7 with DWM disabled and software compositing. This was caused by the WM_PAINT update region being empty for the browser window because it has the WS_CLIPCHILDREN style. The child window wasn't handling the WM_PAINT message and with DWM disabled Windows doesn't keep it's own copy of the pixels. As a result, nothing was telling the display compositor to paint those pixels again. Bug: 924975, 835906 Change-Id: I70eef78223ea6f18f4898ebb4d973811fa85c1d2 Reviewed-on: https://chromium-review.googlesource.com/c/1450399 Commit-Queue: kylechar <kylechar@chromium.org> Reviewed-by:
Sunny Sachanandani <sunnyps@chromium.org> Cr-Commit-Position: refs/heads/master@{#628433}
-
Mike Reed authored
Motivated/found by https://skia-review.googlesource.com/c/skia/+/188630 TBR= Change-Id: Iac8fdfe741a51eace1c7ab5ca6116a82e9172ece Reviewed-on: https://chromium-review.googlesource.com/c/1450437 Commit-Queue: Mike Reed <reed@google.com> Reviewed-by:
Florin Malita <fmalita@chromium.org> Cr-Commit-Position: refs/heads/master@{#628432}
-
Jeremy Klein authored
The existing message makes it sound like the wrong device responded with a ConnectTetheringResponse, but really this log happens every time a non-success response code is received. Bug: None Change-Id: I6c34857a30e86751febff93b13d84b3db6ddc883 Reviewed-on: https://chromium-review.googlesource.com/c/1450404 Commit-Queue: Jeremy Klein <jlklein@chromium.org> Commit-Queue: Kyle Horimoto <khorimoto@chromium.org> Auto-Submit: Jeremy Klein <jlklein@chromium.org> Reviewed-by:
-
Asanka Herath authored
This change stops attaching the origin and referrer URL metadata to downloaded files on Linux. This information was previously set via the user.xdg.origin.url and user.xdg.referrer.url xattrs. Attaching this metadata doesn't provide any security guarantees on Linux, and is a privacy risk. Originally landed as: https://crrev.com/10156ea4faa45bc0a61817c07659dc4c Reverted as : https://crrev.com/c1f63eb16417863e361a5de3265bd0fa Relanding after removing change to enable a PPAPI browser test on macOS. Bug: 917842 Bug: 927074 TBR: wfh@chromium.org Change-Id: I911776ec2c6d30f0ed24761f4f1257a62b3b62d6 Reviewed-on: https://chromium-review.googlesource.com/c/1447122Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Min Qin <qinmin@chromium.org> Commit-Queue: Avi Drissman <avi@chromium.org> Auto-Submit: Asanka Herath <asanka@chromium.org> Cr-Commit-Position: refs/heads/master@{#628430}
-
Hao Zhang authored
Design Doc: https://docs.google.com/document/d/1Sm3Yh3xxIcvo3qF2HQpQzJYR3v7K15B516vidtLNYvY/edit?usp=sharing Change-Id: If9d866d84cda3bf9b31c4db4792cfe6033e459cf Bug: 899057 Reviewed-on: https://chromium-review.googlesource.com/c/1443629Reviewed-by:
Jared Saul <jsaul@google.com> Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Reviewed-by:
Fabio Tirelo <ftirelo@chromium.org> Commit-Queue: Hao Zhang <hozhng@google.com> Cr-Commit-Position: refs/heads/master@{#628429}
-
Min Qin authored
This CL moves DownloadPathReservationTracker from chrome/ to components/. This will make it easier to move DownloadTargetDeterminer to components/, which is crucial for making download a standalone component. Bug: 927083 Change-Id: Idff5737a9ef79988de6eb9d3f7669e8636f86688 Reviewed-on: https://chromium-review.googlesource.com/c/1447118Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Reviewed-by:
Xing Liu <xingliu@chromium.org> Commit-Queue: Min Qin <qinmin@chromium.org> Cr-Commit-Position: refs/heads/master@{#628428}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/da18f31f960f..3e7bf99febab git log da18f31f960f..3e7bf99febab --date=short --no-merges --format='%ad %ae %s' 2019-02-01 dgarrett@google.com workspace_stages: Add UpdateSDKStage. 2019-02-01 dgarrett@google.com workspace_stages: Use chroot_args and extra_env. 2019-02-01 dgarrett@google.com workspace_stages: Add tests for InitSDK, SetupBoard. Created with: gclient setdep -r src/third_party/chromite@3e7bf99febab 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. TBR=chrome-os-gardeners@chromium.org Change-Id: I237d4a44d2d8e7924ec6d52531620dd83d83ea1d Reviewed-on: https://chromium-review.googlesource.com/c/1450164Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/da7318dd0eeb..8af4b4b64443 git log da7318dd0eeb..8af4b4b64443 --date=short --no-merges --format='%ad %ae %s' 2019-02-01 rmhasan@google.com Fixing issue with tests skipped via the 'Skip' tag Created with: gclient setdep -r src/third_party/catapult@8af4b4b64443 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-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 BUG=chromium:923494 TBR=sullivan@chromium.org Change-Id: I94398bb9ae913c15cf53e7e58fb519d85cb03574 Reviewed-on: https://chromium-review.googlesource.com/c/1450163Reviewed-by:
-
Varun Khaneja authored
Also, add a comment in the proto. See http://b/123719599 for details. R=drubery Bug: 907280,927831 Change-Id: Idc690f25bfc3b909eead54c0184184bcf0df8a32 Reviewed-on: https://chromium-review.googlesource.com/c/1450415Reviewed-by:
Daniel Rubery <drubery@chromium.org> Commit-Queue: Varun Khaneja <vakh@chromium.org> Cr-Commit-Position: refs/heads/master@{#628425}
-
Vladislav Kaznacheev authored
The current height is 90dp, while the spec requires 92dp. Bug: 925204 Test: manual Change-Id: I484d604028c9bb1c9b82ceae115f871fc1640566 Reviewed-on: https://chromium-review.googlesource.com/c/1450413Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Vladislav Kaznacheev <kaznacheev@chromium.org> Cr-Commit-Position: refs/heads/master@{#628424}
-
Leonard Grey authored
Follow up to https://chromium-review.googlesource.com/c/chromium/src/+/1436948 Change-Id: I553d0a1d50aa764a79b163a8a3a26ab774e4e162 Reviewed-on: https://chromium-review.googlesource.com/c/1440525 Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Auto-Submit: Leonard Grey <lgrey@chromium.org> Cr-Commit-Position: refs/heads/master@{#628423}
-
Ryan Hansberry authored
This restores previous Smart Lock behavior (regressed in M71), improving latency. Before (average of 10 local runs): * StartScanToReceiveUnlockableRemoteStatus: 9007.0 ms * StartScanToAuthentication: 8827.2 ms * AuthenticationToReceiveUnlockableRemoteStatus: 179.3 ms After (average of 10 local runs): * StartScanToReceiveUnlockableRemoteStatus: 3685.6 ms * StartScanToAuthentication: 3576.6 ms * AuthenticationToReceiveUnlockableRemoteStatus: 108.6 ms ((9007.0 - 3685.6) / 9007.0) = 59% reduction in overall latency. Bug: 905724 Change-Id: Ic9dd8e3d11bd3f4140d68bc920a96f2822fc3519 Reviewed-on: https://chromium-review.googlesource.com/c/1448987Reviewed-by:
-
Dana Fried authored
Currently, Chrome offers to update plugins that are blocked because they are outdated. In Dec 2020, there will be no way to update, as plugins will be end-of-life. When the user tries to load an outdated plugin now, they get a status message that offers to run the outdated version or upgrade the plugin. This patch changes the message seen when a plugin is blocked and cannot be updated - it only offers to run the plugin as-is (no upgrade option). Bug: 918427 Change-Id: If6019fc9492575d7c2e9efbec7c3d665f1db47ac Reviewed-on: https://chromium-review.googlesource.com/c/1448794 Commit-Queue: Dana Fried <dfried@chromium.org> Reviewed-by:
Tommy Li <tommycli@chromium.org> Cr-Commit-Position: refs/heads/master@{#628421}
-
Nicolas authored
This will let the Internet Explorer BHO use the same prefs as Chrome. Caveat: since cache.dat is only updated at startup, it won't update correctly if BrowserSwitcher is enabled by Cloud policy, or if BrowserSwitcher *becomes* enabled while Chrome is open. Bug: 909878 Change-Id: I1f5fe1d436d752eeb327d0bf9c0c4096ab62fce7 Reviewed-on: https://chromium-review.googlesource.com/c/1432478Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Commit-Queue: Nicolas Ouellet-Payeur <nicolaso@chromium.org> Cr-Commit-Position: refs/heads/master@{#628420}
-
dpapad authored
Replace i18n-values with $i18n{} mechanism. Also remove unnecessary tabs.css and widgets.css dependencies. Bug: 677338 Change-Id: I99b9b570e00bbc2b0bd0ff1179b086bd6bd8e270 Reviewed-on: https://chromium-review.googlesource.com/c/1450307Reviewed-by:Joshua Bell <jsbell@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#628419}
-
Ahmed Fakhry authored
BUG=906698 TEST=Manually, on nocturne, make sure going into docked mode causes the video to stop playing. Change-Id: I9381c9688a4529db9684e6de5f88e2a935b8dce6 Reviewed-on: https://chromium-review.googlesource.com/c/1407504Reviewed-by:Mitsuru Oshima <oshima@chromium.org> Commit-Queue: Ahmed Fakhry <afakhry@chromium.org> Cr-Commit-Position: refs/heads/master@{#628418}
-
Philip Rogers authored
This patch removes a CaptureScreenshotTest.CaptureScreenshotArea subtest that was testing screenshots extending beyond the frame. This does not affect the devtools screenshot feature which resizes the frame to be large enough. There could be non-chrome users of the devtools api that depend on this behavior but I think there are not. For example, on a page such as https://pr.gg/fixedtall.html, capturing pixels outside the frame would mean the blue fixed div would be in the middle of the screenshot. Bug: 922706 Change-Id: I8ed1e143bffd08de6e0f2b6ec6d76da93ab1e797 Reviewed-on: https://chromium-review.googlesource.com/c/1435836Reviewed-by:
Eric Seckler <eseckler@chromium.org> Reviewed-by:
Andrey Kosyakov <caseq@chromium.org> Auto-Submit: Philip Rogers <pdr@chromium.org> Commit-Queue: Andrey Kosyakov <caseq@chromium.org> Cr-Commit-Position: refs/heads/master@{#628417}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/ab56670af981..a34d7766c56a git log ab56670af981..a34d7766c56a --date=short --no-merges --format='%ad %ae %s' 2019-02-01 nisse@webrtc.org Move RtpSenderAudioTest to its own file 2019-02-01 mbonadei@webrtc.org [clang-tidy] Apply performance-move-const-arg fixes. 2019-02-01 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision ecc3b419..6893a4aa (628213:628317) 2019-02-01 nisse@webrtc.org Delete sequence number save and restore in ChannelSend. 2019-02-01 mbonadei@webrtc.org Fix RTCStatsReport::ConstIterator move constructor. 2019-02-01 eladalon@webrtc.org Improve CPU utilization when encoding VP8 with a single temporal layer Created with: gclient setdep -r src/third_party/webrtc@a34d7766c56a 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 TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: Ia708a6669e2a247e7ea9c2382d28f62268b8ba25 Reviewed-on: https://chromium-review.googlesource.com/c/1449787Reviewed-by:
-
David Bertoni authored
We are currently collecting stats for the old and new analysis functions. Keeping the percentage of visible pixels required will allow us to keep comparing these numbers. Bug: 805600 Change-Id: I5d7e9c800c2e6f7bab5f92b081624b796b18b4f3 Reviewed-on: https://chromium-review.googlesource.com/c/1448791Reviewed-by:
Karan Bhatia <karandeepb@chromium.org> Commit-Queue: David Bertoni <dbertoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#628415}
-
François Beaufort authored
This CL makes sure a play/pause button is always displayed in a Picture-in-Picture window if a Media Session action such as play or pause has been set by the website. Clicking this button will also trigger the action handler if set. Change-Id: Ic06f2dfc18318593b0d7b85deaef7e8ff24626d4 Bug: 926163 Reviewed-on: https://chromium-review.googlesource.com/c/1437074 Auto-Submit: François Beaufort <beaufort.francois@gmail.com> Commit-Queue: François Beaufort <beaufort.francois@gmail.com> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Reviewed-by:
Becca Hughes <beccahughes@chromium.org> Cr-Commit-Position: refs/heads/master@{#628414}
-
Raul Tambre authored
IntToString has been deprecated in favour of NumberToString. Using NumberToString also fixes a few 64-bit truncation warnings. Bug: 879657 Change-Id: Icd305fbc7ee005df63271a74412eb6dffad19712 Reviewed-on: https://chromium-review.googlesource.com/c/1448463 Auto-Submit: Raul Tambre <raul@tambre.ee> Commit-Queue: Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/master@{#628413}
-
Matt Menke authored
This parameter was recently added to the SSL socket pools, which are going away. This CL adds it to the TransportClientSocketPool, which is replacing them. This is part of an effort to flatten the socket pools. https://docs.google.com/document/d/1g0EA4iDqaDhNXA_mq-YK3SlSX-xRkoKvZetAQqdRrxM/edit Bug: 472729 Change-Id: I804bf4558e4e9f57dbb014a7f0e5ff102e1f677d Reviewed-on: https://chromium-review.googlesource.com/c/1446248Reviewed-by:
David Benjamin <davidben@chromium.org> Commit-Queue: Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#628412}
-
David Tseng authored
Bug: b:123382801 Change-Id: Ic4527aff9042c32606de942b09c5e5bb1d663f93 Reviewed-on: https://chromium-review.googlesource.com/c/1443935Reviewed-by:
Jorge Lucangeli Obes <jorgelo@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#628411}
-
Vadym Doroshenko authored
Manual fallbacks are needed for forms that have <input type=password> but for some reasons not considered as valid password forms (for example because there is autocomplete attributes for credit card fields). The manual fallback flow is the following: 1.A form with <input type=password> is found 2.Filling information is sent to the renderer, if this form is not considered as valid password form, automatic filling shouldn't happen, only fallbacks on password field are available. 3.When the user is typing in any password element, the manual manual fallback for saving is shown. 4.If the user submits form that is not considered as valid password form, not automatic prompt is shown. This CL contains: 1.FormParser is updated to ensure that all <input type=password> are taken for manual fallbacks (before that credit card fields or readonly fields might be missing). 2.Implemented not to fill, if parsing result is only for fallback 3.PasswordManager::ProvisionallySaveForm is updated to ensure that no save fallback is shown, if parsing was unsuccessful (because nothing to save) 4.Renaming PasswordForm::only_for_fallback_saving to only_for_fallback (because it's also used for filling now). Bug: 831123, 925191 Change-Id: If6d4f8d2f139b1530eaffc7c6eb74efdc9842d49 Reviewed-on: https://chromium-review.googlesource.com/c/1446153Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Commit-Queue: Vadym Doroshenko <dvadym@chromium.org> Cr-Commit-Position: refs/heads/master@{#628410}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/cf9383ed325c..91d469aae063 git log cf9383ed325c..91d469aae063 --date=short --no-merges --format='%ad %ae %s' 2019-02-01 syoussefi@chromium.org Initial support for compiler AST validation 2019-02-01 jmadill@chromium.org Roll glslang. 2019-02-01 ckulakowski@opera.com Fix for linking of non-component angle_unittests 2019-02-01 jmadill@chromium.org Inline ValidateBindTexture. Created with: gclient setdep -r src/third_party/angle@91d469aae063 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 BUG=chromium:926235,chromium:927650 TBR=cwallez@chromium.org Change-Id: I07f7ddfada83e3ab1a0a3e8478ef07d7e8b26089 Reviewed-on: https://chromium-review.googlesource.com/c/1450157Reviewed-by:
-
Joshua Pawlicki authored
Bug: 833687 Change-Id: I7581877bfda2a5f8ffeb1134814ec0b784c9def0 Reviewed-on: https://chromium-review.googlesource.com/c/1450305 Commit-Queue: Joshua Pawlicki <waffles@chromium.org> Commit-Queue: Sorin Jianu <sorin@chromium.org> Auto-Submit: Joshua Pawlicki <waffles@chromium.org> Reviewed-by:
Sorin Jianu <sorin@chromium.org> Cr-Commit-Position: refs/heads/master@{#628408}
-
Joey Arhar authored
Bug: 607240 Change-Id: I2595c44cdb80a9abc9098bd66fb38145b697a6d0 Reviewed-on: https://chromium-review.googlesource.com/c/1447231 Commit-Queue: Joey Arhar <jarhar@chromium.org> Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#628407}
-
Stephen McGruer authored
Previously the content-side support for reduced motion for a frame was static and would not react to changes in the system settings until you created a new frame. This CL listens for notifications and recomputes the webkit preferences when that happens (which then causes the new prefers-reduced-motion value to be calculated). This CL also introduces a caching mechanism for the system setting, to avoid potentially expensive recomputation. Test: Tested manually on MacOS and Windows devices. Bug: 722548 Change-Id: I6be0822cc40a697a4373fbf53888d2219e5890f2 Reviewed-on: https://chromium-review.googlesource.com/c/1418498 Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Reviewed-by:
Stephen McGruer <smcgruer@chromium.org> Reviewed-by:
Robert Flack <flackr@chromium.org> Reviewed-by:
-
Brian Osman authored
When skcms was spun out from Skia, we ended up with two structs for transfer function. They're both POD, and memory-layout is identical, but field naming is different. We've migrated most APIs to use the skcms types - this finishes that work in Chrome. Change-Id: I148c60518776cac950bae5edab34be58d25b3555 Reviewed-on: https://chromium-review.googlesource.com/c/1434175Reviewed-by:
ccameron <ccameron@chromium.org> Reviewed-by:
Robert Kroeger <rjkroege@chromium.org> Reviewed-by:
Daniele Castagna <dcastagna@chromium.org> Commit-Queue: Brian Osman <brianosman@google.com> Cr-Commit-Position: refs/heads/master@{#628405}
-
Kevin Ellis authored
Change-Id: If273cdaee2a84cbe961962c1b5ab47e595dbec4b Reviewed-on: https://chromium-review.googlesource.com/c/1450038Reviewed-by:
Xida Chen <xidachen@chromium.org> Commit-Queue: Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#628404}
-
Kenneth Russell authored
conformance2/vertex_arrays/vertex-array-object.html is currently flaky on all GPUs with ANGLE's OpenGL backend. Bug: 920265 Change-Id: Iedded0bf7b36a0046edc19ccfc6dbd216f47a82a Tbr: ynovikov@chromium.org No-Try: True Reviewed-on: https://chromium-review.googlesource.com/c/1450258Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#628403}
-
Vlad Tsyrklevich authored
Now that https://crrev.com/627865 has landed, increase the amount of memory GWP-ASan uses to get back to consuming approximately ~40k per process. Bug: 896019 Change-Id: Iac888c38f32078e21cf4295bdd756b67f48d68c0 Reviewed-on: https://chromium-review.googlesource.com/c/1448793 Auto-Submit: Vlad Tsyrklevich <vtsyrklevich@chromium.org> Reviewed-by:
Vitaly Buka <vitalybuka@chromium.org> Commit-Queue: Vlad Tsyrklevich <vtsyrklevich@chromium.org> Cr-Commit-Position: refs/heads/master@{#628402}
-
