- 08 Nov, 2018 40 commits
-
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/993edbb4..511e861d 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=master.tryserver.blink:linux_trusty_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: I6200203ffc2b808e91daa255e006f7db41df119e Reviewed-on: https://chromium-review.googlesource.com/c/1327547Reviewed-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@{#606625}
-
Sebastien Marchand authored
Bug: 839878 Change-Id: I045921f965486b19efc67a0a2628e2907936f501 Reviewed-on: https://chromium-review.googlesource.com/c/1277273 Commit-Queue: Sébastien Marchand <sebmarchand@chromium.org> Reviewed-by:
Chris Hamilton <chrisha@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Cr-Commit-Position: refs/heads/master@{#606624}
-
David Jacobo authored
IntentPickerAutoDisplayService is a KeyedService (including a factory class) so intent picker UI can locally (i.e. within Chrome) check if such UI has been displayed before without the user taking action. The user ignoring the UI should be remembered, so we stop auto-displaying the UI and instead only show an entry icon in the omnibox, where the UI will be one-click away. Bug: 902657 Test: Build. Change-Id: I2e0333b8c7eba3af78a671a4f119b7c26fcc5283 Reviewed-on: https://chromium-review.googlesource.com/c/1303653 Commit-Queue: David Jacobo <djacobo@chromium.org> Reviewed-by:
Christian Dullweber <dullweber@chromium.org> Reviewed-by:
Raymes Khoury <raymes@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Reviewed-by:
calamity <calamity@chromium.org> Cr-Commit-Position: refs/heads/master@{#606623}
-
Reid Kleckner authored
Previously, alignof(int64_t) was 8 on i686, but now it is 4. This is true in GCC 8+ and the latest version of clang. These types have always only been aligned to 4 bytes in struct layout, so this should not have wide ranging implications for ABI stability. Bug: 900406 Change-Id: Ia2f0d87300679148d7ca653b7cc52fe9cf910bbc Reviewed-on: https://chromium-review.googlesource.com/c/1327606Reviewed-by:
Ken Rockot <rockot@google.com> Commit-Queue: Reid Kleckner <rnk@chromium.org> Cr-Commit-Position: refs/heads/master@{#606622}
-
Victor Miura authored
In Telemetry on Desktop, various toast messages can change the window height dynamically and make layers in the test that should be out of viewport be visible. Double the padding height to ensure they're not visible in these cases. BUG=878951 Change-Id: I19a3990ebd3b577fc19ac73cf72db4e6ecfae3db Reviewed-on: https://chromium-review.googlesource.com/c/1292812Reviewed-by:
Annie Sullivan <sullivan@chromium.org> Commit-Queue: Victor Miura <vmiura@chromium.org> Cr-Commit-Position: refs/heads/master@{#606621}
-
Peter Boström authored
Uses 12% opacity of white / black for the placeholder depending on contrast instead of hard-coding GoogleBlue100. For the bouncing pill, use theme colors previously used for the spinner. Bug: chromium:903457 Change-Id: I6dd46ac516a8fef874ecdf95bcaef3b57d7a5974 Reviewed-on: https://chromium-review.googlesource.com/c/1327422Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Peter Boström <pbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#606620}
-
Leonard Grey authored
This is a really longwinded way for me to fix some NOTIMPLEMENTED spam, though I'm pretty sure the thing that happens right now when you open a certificate prompt and drag a tab into the parent window is bad. This introduces a new method because we're not sure if it matches the Aura semantics, and this is better than the nothing we were doing previously. Bug: 825834 Change-Id: I316ca4fbaa7a27dacb09bce0866203b79567016d Reviewed-on: https://chromium-review.googlesource.com/c/1315956 Commit-Queue: Leonard Grey <lgrey@chromium.org> Reviewed-by:
-
Robert Ogden authored
This basically turns out to a manual revert of https://chromium-review.googlesource.com/c/chromium/src/+/1091499 Bug: 902063 Change-Id: I83a206ef53793f776fa04704f960dc44b4a158f1 Reviewed-on: https://chromium-review.googlesource.com/c/1324931Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Commit-Queue: Robert Ogden <robertogden@chromium.org> Cr-Commit-Position: refs/heads/master@{#606618}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/ca7f9d6defef..aa347dd67ba1 Created with: gclient setdep -r src-internal@aa347dd67ba1 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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=mmoss@chromium.org Change-Id: I5dedca1f27235ff076b508d96a1bea1f15e266cd Reviewed-on: https://chromium-review.googlesource.com/c/1327603Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#606617}
-
BUG=762641 TBR=xiyuan@chromium.org Change-Id: I6477014740f67fb69c6e2684022944b487d484f2 Reviewed-on: https://chromium-review.googlesource.com/c/1327442Reviewed-by:
ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#606616}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/6721478ef112..1e9fc1aac107 git log 6721478ef112..1e9fc1aac107 --date=short --no-merges --format='%ad %ae %s' 2018-11-08 greg@lunarg.com Add base and core bindless validation instrumentation classes (#2014) Created with: gclient setdep -r src/third_party/SPIRV-Tools/src@1e9fc1aac107 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: Ia1d79b6d530b7c562c659703b1b11240dd1a15f5 Reviewed-on: https://chromium-review.googlesource.com/c/1327343Reviewed-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@{#606615}
-
Antoine Labour authored
After switching one-copy to SharedImageInterface, TileResourceFreedIfLostWhileExported lost its meaning as it's only counting staging textures instead of resource textures. This restores the behavior by making sure we ask the SharedImageInterface on the worker context (where they are created now) instead of the GLES2Interface on the compositor context. Bug: 882513 Change-Id: I1257c9e130bfa615d56602b0ce74f2830d5a55f5 Reviewed-on: https://chromium-review.googlesource.com/c/1325087 Commit-Queue: Antoine Labour <piman@chromium.org> Reviewed-by:
Jonathan Backer <backer@chromium.org> Cr-Commit-Position: refs/heads/master@{#606614}
-
Scott Graham authored
Bug: 883496 Change-Id: Ic8973eb46a68ecf09a57572b1d694cb4812c897f Reviewed-on: https://chromium-review.googlesource.com/c/1324209 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by:
Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#606613}
-
Samuel Huang authored
Update includes and comments, and remove some unused code. In particular, remove TODO comments for figuring out whether ARM abs32 references can be 4 bytes long: Turns out ARM absolute references are 8 bytes long. It's rel32 refereneces that can be 4 bytes long. Change-Id: I02dc905885f6cb5ff929efe0fb1f9a6593ee05a8 Reviewed-on: https://chromium-review.googlesource.com/c/1327559Reviewed-by:
Etienne Pierre-Doray <etiennep@chromium.org> Reviewed-by:
Samuel Huang <huangs@chromium.org> Commit-Queue: Samuel Huang <huangs@chromium.org> Cr-Commit-Position: refs/heads/master@{#606612}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/2d061b16ea6c..365e59b9d0c3 git log 2d061b16ea6c..365e59b9d0c3 --date=short --no-merges --format='%ad %ae %s' 2018-11-08 treehugger-gerrit@google.com Merge "trace_processor: Improve parsing of json traces" Created with: gclient setdep -r src/third_party/perfetto@365e59b9d0c3 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: I646e80b134fe28fe928272a8294ce34532aec3e2 Reviewed-on: https://chromium-review.googlesource.com/c/1327345Reviewed-by:
-
Eric Roman authored
It is no longer necessary as ProxyBypassRules now implicitly bypasses loopback addresses. Change-Id: Ia6c480870458e63a70e6ba753137f9169d58ba9e Reviewed-on: https://chromium-review.googlesource.com/c/1327143Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/f04a3a61ad90..5d5091665700 git log f04a3a61ad90..5d5091665700 --date=short --no-merges --format='%ad %ae %s' 2018-11-08 dtu@chromium.org [pinpoint] Let users with tryjob access launch Pinpoint jobs. Created with: gclient setdep -r src/third_party/catapult@5d5091665700 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:895738 TBR=sullivan@chromium.org Change-Id: Ie7de7636281943d07faae602d9e54132a5cce7dc Reviewed-on: https://chromium-review.googlesource.com/c/1327601Reviewed-by:
-
Alex Oldemeier authored
To avoid other people stumbling over potentially unexpected behaviour of Time::FromString, add a visible WARNING about the underlying converter being very permissive. Change-Id: I86c590eaacf6e2f429baaa66113e9c34b44cdd08 Reviewed-on: https://chromium-review.googlesource.com/c/1323093Reviewed-by:
Yuri Wiitala <miu@chromium.org> Commit-Queue: Yuri Wiitala <miu@chromium.org> Cr-Commit-Position: refs/heads/master@{#606608}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/1379508a3a57..06a477c3300d git log 1379508a3a57..06a477c3300d --date=short --no-merges --format='%ad %ae %s' 2018-11-08 mtklein@google.com remove old name for SkCodec::kNoFrame 2018-11-08 reed@google.com Revert[4] "hide nested hinting enum" 2018-11-08 brianosman@google.com Added GrMeshDrawOp::WriteVertexData 2018-11-08 recipe-roller@chromium.org Roll recipe dependencies (trivial). 2018-11-08 mtklein@google.com Reland "simplify disabling effect deserialization" 2018-11-08 mtklein@google.com exclude RAW codec code from Google3 build Created with: gclient setdep -r src/third_party/skia@06a477c3300d 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-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;master.tryserver.blink:linux_trusty_blink_rel TBR=allanmac@chromium.org Change-Id: If4e4beb7d418f607d61f3ca894c2e0010b419c13 Reviewed-on: https://chromium-review.googlesource.com/c/1327241Reviewed-by:
-
Sahel Sharify authored
This cl resolves the regression that is caused by the following cl: https://chromium-review.googlesource.com/c/chromium/src/+/1313270 The previous cl calls UnregisterFlingSchedulerObserver() twice when a fling gets cancelled: once from gesture_event_queue while handling the generated GSE and once from FlingScheduler::DidStopFlingingOnBrowser. When there is only one active fling and the fling is not interrupted by another scroll/fling this works fine since the second Unregister call does nothing. However sometimes when a new fling replaces an active fling (e.g. starting a fling in the opposite direction of the currently active fling) the second Unregister call unregisters the observer that is added for the new fling. Since the observer is unregistered for the new fling no ProgressFling will get called till the user does a third fling. on the first ProgressFling call for the third fling, the controller tries to cancel the second fling and calls unregister which unregisters the observer for the third fling and the same thing happens for the rest of the flings from now on. This cl fixes the issue by not calling UnregisterFlingSchedulerObserver() in FlingScheduler::DidStopFlingingOnBrowser since it will get called once the generated GSE of the fling cancel is processed. Bug: 901831 Change-Id: I4d52f512ea38764fc64c580f6cac5ed4a32c1bee Reviewed-on: https://chromium-review.googlesource.com/c/1327145Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Commit-Queue: Sahel Sharify <sahel@chromium.org> Cr-Commit-Position: refs/heads/master@{#606606}
-
Thoren Paulson authored
The Android implementation of the CMA backend depends on APIs added in Android N. This change uses the default Android AudioManager on earlier versions. Bug: internal b/117838318 Test: audio with GPMusic and Spotify, video with Hulu & GPMovies. Change-Id: Ic59c37e103e098638c861efd8b350c29c028e64d Reviewed-on: https://chromium-review.googlesource.com/c/1327226Reviewed-by:
Luke Halliwell <halliwell@chromium.org> Commit-Queue: Thoren Paulson <thoren@chromium.org> Cr-Commit-Position: refs/heads/master@{#606605}
-
Pedro Amaral authored
This is the bottom toolbar refactor to allow for 5 buttons in browsing mode and moving the tab switcher toolbar to the bottom. This CL breaks the old bottom toolbar MVC component into 2 components: BrowsingModeBottomToolbar and TabSwitcherBottomToolbar. Those components have a common root coordinator called BottomToolbarCoordinator. I've also added two new providers. The first is the TabCountProvider. It notifies its listeners when the tab count changes. This is useful for the tab switcher button and the HTS tab layout icon. The other provider is the IncognitoStateProvider. It notifies its listeners when incognito mode is entered or exited. It also provides the tint and color for that state. Bug: 900759 Change-Id: Idced9f29ff4e5f3b0c6516b761416f32af78efe3 Binary-Size: Overhead from MVC Change-Id: Idced9f29ff4e5f3b0c6516b761416f32af78efe3 Reviewed-on: https://chromium-review.googlesource.com/c/1292405 Commit-Queue: Pedro Amaral <amaralp@chromium.org> Reviewed-by:
Matthew Jones <mdjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#606604}
-
David Jean authored
Bug: 845472 Change-Id: Id8d909eb12468774b52b74e0684b6ab1e72ad1f2 Reviewed-on: https://chromium-review.googlesource.com/c/1318975 Commit-Queue: David Jean <djean@chromium.org> Reviewed-by:
Moe Ahmadi <mahmadi@chromium.org> Cr-Commit-Position: refs/heads/master@{#606603}
-
Juan Antonio Navarro Pérez authored
This reverts commit b1c0b554. Reason for revert: Stories show work now after fix of underlying issue. Original change's description: > [tools/perf] Disable browse:chrome:* stories > > These stories ara failing with an unhandleable error, preventing the > rest of the benchmark to run. > > Disable these as a short term quick fix. > > NOTRY=true > TBR=nednguyen@google.com > > Bug: 900909 > Change-Id: I8e51ced1644853469ff8310de03cb232abba9253 > Reviewed-on: https://chromium-review.googlesource.com/c/1311924 > Reviewed-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@{#604564} TBR=perezju@chromium.org,nednguyen@google.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 900909 Change-Id: Ia698d28b432cc0606e0bb157124c2dd39ca3eff0 Reviewed-on: https://chromium-review.googlesource.com/c/1327561Reviewed-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@{#606602}
-
Siddhartha authored
Change-Id: I354d0cb1ba08877e3ec921faa8439f8219eec8c2 Reviewed-on: https://chromium-review.googlesource.com/c/1325530 Commit-Queue: ssid <ssid@chromium.org> Reviewed-by:
Alexei Filippov <alph@chromium.org> Cr-Commit-Position: refs/heads/master@{#606601}
-
Andrew Luo authored
Bug: 896857 Change-Id: Icfaf7503e60c476e434504971f832a65a3956235 Reviewed-on: https://chromium-review.googlesource.com/c/1321957 Commit-Queue: Andrew Luo <aluo@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#606600}
-
Jerome Jiang authored
https://chromium.googlesource.com/webm/libvpx.git/+log/7808cc796ef1..c66fe1a8930c $ git log 7808cc796..c66fe1a89 --date=short --no-merges --format='%ad %ae %s' 2018-11-07 jianj Add operator<< to hadamard test. 2018-11-07 yaowu Simplify rdmult computation 2018-11-07 marpan vp9-screen-content: Adjust condition for large search area 2018-11-07 jingning Cosmetic clean up in find_arf_order 2018-11-06 jingning Unify GOP structure layout setup 2018-08-28 jianj vp9: postencode drop frame for screen content in CBR. 2018-11-05 marpan vp9 screen-content: Adjustments for screen content. 2018-11-01 sdeng Refactor Hadamard tests and add highbd tests 2018-10-26 paulwilkins Modified key frame detection. 2018-11-05 jianj vp8 dec: only compute ref frame buffer pointer for non intra 2018-11-05 jingning Track maximum layer depth in a GOP 2018-11-05 jingning Fix gf_group->frame_end assignment 2018-11-05 jingning Refactor define_gf_group_structure() 2018-11-05 jingning Remove redundant assignments in define_gf_group_structure() 2018-11-05 jingning Refactor find_arf_order() 2018-11-05 marpan vp8: Increase rate correction threshold for drop-overshoot 2018-10-31 johann.koenig vp8: remove VP8_ENTROPY_STATS code Created with: roll-dep src/third_party/libvpx/source/libvpx R=johannkoenig@google.com BUG=b/118866248,b/112990050 Change-Id: I06b1b60c39fbdd0f2ed16713dae91a02969e918c Reviewed-on: https://chromium-review.googlesource.com/c/1327405Reviewed-by:
Johann Koenig <johannkoenig@google.com> Commit-Queue: Jerome Jiang <jianj@google.com> Cr-Commit-Position: refs/heads/master@{#606599}
-
Tatiana Buldina authored
related CL: https://chromium-review.googlesource.com/c/chromium/deps/webdriver/+/1287025 Change-Id: I7e18664b01de7ed627eecec4f7cedac0eeb39079 Reviewed-on: https://chromium-review.googlesource.com/c/1287186Reviewed-by:
John Chen <johnchen@chromium.org> Commit-Queue: Tatiana Buldina <buldina@chromium.org> Cr-Commit-Position: refs/heads/master@{#606598}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/148454cafef1..ca7f9d6defef Created with: gclient setdep -r src-internal@ca7f9d6defef The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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=mmoss@chromium.org Change-Id: I412f20bbf85a9cecba73ad668b7b15b367c4934e Reviewed-on: https://chromium-review.googlesource.com/c/1327344Reviewed-by:
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/85be49ec0bc2..2d061b16ea6c git log 85be49ec0bc2..2d061b16ea6c --date=short --no-merges --format='%ad %ae %s' 2018-11-08 hjd@google.com Merge "perfetto_cmd: Fix log when streaming to file" Created with: gclient setdep -r src/third_party/perfetto@2d061b16ea6c 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: Ib77e252f062808ba36f3741f41bbb626e67af4a3 Reviewed-on: https://chromium-review.googlesource.com/c/1327341Reviewed-by:
-
Mohamed Amir Yosef authored
Bug: 902349 Change-Id: I565b746737cc1567cf75abf4924c77eb648c3b46 Reviewed-on: https://chromium-review.googlesource.com/c/1322869Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org> Cr-Commit-Position: refs/heads/master@{#606595}
-
Shawn Gallea authored
Remove pointer.h include and replace with wm_helper.h include. pointer.h is not needed, but wm_helper is needed as it was transitively included through pointer.h. Bug: 896710 Test: Built on ChromeOS Change-Id: Ic3dea290b4662cc5d868e7568c4909257dd55122 Reviewed-on: https://chromium-review.googlesource.com/c/1324749Reviewed-by:
Daniele Castagna <dcastagna@chromium.org> Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Commit-Queue: Shawn Gallea <sagallea@google.com> Cr-Commit-Position: refs/heads/master@{#606594}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/e5e0aea5a404..625c7d270c1b git log e5e0aea5a404..625c7d270c1b --date=short --no-merges --format='%ad %ae %s' 2018-11-08 thestig@chromium.org Clean up CPDF_TransferFunc. Created with: gclient setdep -r src/third_party/pdfium@625c7d270c1b 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: I7de81829e0e267160d20bde30c0f665100bd11a3 Reviewed-on: https://chromium-review.googlesource.com/c/1327342Reviewed-by:
-
Dmitry Gozman authored
Bug: 775132 Change-Id: I7f7f58f56e437895afd91002e2316c4ef40c92ce Reviewed-on: https://chromium-review.googlesource.com/c/1324455 Commit-Queue: Dmitry Gozman <dgozman@chromium.org> Reviewed-by:
Andrey Lushnikov <lushnikov@chromium.org> Cr-Commit-Position: refs/heads/master@{#606592}
-
Mitsuru Oshima authored
Because the mask layer may be used by a detached layer, and re-using before the detached layer is deleted can lead to a crash. Bug: b/118822974 Test: manual. See bug for repro step. Change-Id: I82379d6f10f7b00fba8b581e667198f28f82f645 Reviewed-on: https://chromium-review.googlesource.com/c/1325565 Commit-Queue: Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Alex Newcomer <newcomer@chromium.org> Cr-Commit-Position: refs/heads/master@{#606591}
-
Fady Samuel authored
viz::LocalSurfaceIdAllocation bundles a viz::LocalSurfaceId and an allocation time for that viz::LocalSurfaceId. The purpose of this allocation time is to determine how long it takes for a surface to get embedded once an ID has been allocated for it. There was some concern raised about drift between LocalSurfaceIds and allocation times and so a previous CL bundled the two together in a class. This CL plumbs LocalSurfaceIdAllocation to more places to ensure the two quantities remain in sync with one another. This CL plumbs LocalSurfaceIdAllocation through FrameVisualProperties which ensures we plumb valid timestamps from a parent renderer to the browser and ultimately to child renderers. Bug: 655231 Change-Id: I1cb7e3e3acacc4fc5398d65f6f62892a2127346d Reviewed-on: https://chromium-review.googlesource.com/c/1324097Reviewed-by:
Jonathan Ross <jonross@chromium.org> Reviewed-by:
Tom Sepez <tsepez@chromium.org> Reviewed-by:
Antoine Labour <piman@chromium.org> Commit-Queue: Fady Samuel <fsamuel@chromium.org> Cr-Commit-Position: refs/heads/master@{#606590}
-
sczs authored
Before this CL Infobar.cc was informing InfobarContainer of an InfobarView resize. Also, the InfobarView was being set by Infobar.cc it now sets its own height. This CL: - Adds functionality so InfobarContainer resizing is driven by UiKit. - Deletes InfobarViewSizing and InfobarViewSizingDelegate. - Removes the plumbing from InfobarView that informs Infobar.cc of a resize. - Removes InfobarIOS and InfobarController methods that were used to resize the InfobarView. Bug: 892376 Change-Id: Iaae3c0ec36ce226fc89fb405cb3d9c40376d3a79 Reviewed-on: https://chromium-review.googlesource.com/c/1321849 Commit-Queue: Sergio Collazos <sczs@chromium.org> Reviewed-by:
Mark Cogan <marq@chromium.org> Cr-Commit-Position: refs/heads/master@{#606589}
-
Tomas Popela authored
Previously we were using va_list for variadic arguments. The downside for this was that only the first value from the variadic argument was passed to the original function. To make it work properly we have to use the __VA_ARGS__ variadic macro that was introduces in C99 and is available in all major C/C++ compilers. Change-Id: I50652f7348a16214811aaab8af116d78cdb70444 Reviewed-on: https://chromium-review.googlesource.com/c/1323089Reviewed-by:
Patrik Höglund <phoglund@chromium.org> Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Commit-Queue: Tomáš Popela <tomas.popela@gmail.com> Cr-Commit-Position: refs/heads/master@{#606588}
-
Ivan Šandrk authored
This was a mistake on my part when writing the original file, and it was just too bothering to see the wrong year on the file and get confused by it, so I had to update it :-) Change-Id: Ia59fd264f11bda490448a386528b9b2fc0606473 Reviewed-on: https://chromium-review.googlesource.com/c/1326641Reviewed-by:
James Cook <jamescook@chromium.org> Commit-Queue: Ivan Šandrk <isandrk@chromium.org> Cr-Commit-Position: refs/heads/master@{#606587}
-
Dirk Pranke authored
The //chrome:chrome group was missing a data_deps declaration on //chrome:reorder_imports, which meant that chrome would build fine but if you ran `mb zip //out/Release //chrome` you'd only get the copy in //out/Release/initialexe/chrome.exe and not the final version in //out/Release. Bug: 902010 Change-Id: I0f3b662ced4c34eef974e8bede01fb9c89410dc1 Reviewed-on: https://chromium-review.googlesource.com/c/1325554Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Dirk Pranke <dpranke@chromium.org> Cr-Commit-Position: refs/heads/master@{#606586}
-
