- 07 Feb, 2018 40 commits
-
-
Mike Wittman authored
This is a reland of aa63fc1d. Original change's description: > Encapsulate Chrome thread profiling setup into a single class > > Creates a simple abstraction around the fairly complex profiling setup. > This CL switches over the GPU and renderer process usage to this class. > The browser process usage will be converted to use this class after it > is extended to support periodic profiling (in a follow-on CL). > > Bug: 808588 > Change-Id: I6195571bf3ddd08291f288f475569bd9a88795ef > Reviewed-on: https://chromium-review.googlesource.com/905451 > Reviewed-by: Scott Violet <sky@chromium.org> > Reviewed-by: Alexei Svitkine <asvitkine@chromium.org> > Commit-Queue: Mike Wittman <wittman@chromium.org> > Cr-Commit-Position: refs/heads/master@{#535125} TBR=sky Bug: 808588 Change-Id: I34f1910116c4e7a500e353c27b85bf7534be43c7 Reviewed-on: https://chromium-review.googlesource.com/907508Reviewed-by:
Mike Wittman <wittman@chromium.org> Commit-Queue: Mike Wittman <wittman@chromium.org> Cr-Commit-Position: refs/heads/master@{#535170}
-
Thomas Anderson authored
This reverts commit e41fd2de. Reason for revert: Tests are still failing with the revert Original change's description: > Revert "DevTools: emit requestWillBeSent & responseReceived for nav requests from browser" > > This reverts commit 37608a0e. > > Reason for revert: Suspected cause of the timeout failures on Linux Tests (dbg)(1). Will reland if the timeouts are not fixed. > https://ci.chromium.org/buildbot/chromium.linux/Linux%20Tests%20%28dbg%29%281%29/70144 > > Original change's description: > > DevTools: emit requestWillBeSent & responseReceived for nav requests from browser > > > > This moves the instrumentation for Network.{requestWillBeSent,responseReceived,loadingFailed} > > to browser and prevents renderer from reporting these. The dataReceived and loadingFinished > > events are still reported from the renderer. > > > > TBR=alexclarke > > > > Bug: 791838 > > Change-Id: I6f7ce1f0c243342ad15cb1bd6290c0f68a0da647 > > Reviewed-on: https://chromium-review.googlesource.com/861952 > > Reviewed-by: Andrey Kosyakov <caseq@chromium.org> > > Reviewed-by: Daniel Cheng <dcheng@chromium.org> > > Reviewed-by: Dmitry Gozman <dgozman@chromium.org> > > Commit-Queue: Andrey Kosyakov <caseq@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#534878} > > TBR=dgozman@chromium.org,dcheng@chromium.org,caseq@chromium.org,pfeldman@chromium.org,alexclarke@chromium.org > > Change-Id: I1a9d199033f5b74b351b788ab6e5eee14869c760 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: 791838 > Reviewed-on: https://chromium-review.googlesource.com/907339 > Reviewed-by: Thomas Anderson <thomasanderson@chromium.org> > Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> > Cr-Commit-Position: refs/heads/master@{#535129} TBR=dgozman@chromium.org,dcheng@chromium.org,caseq@chromium.org,pfeldman@chromium.org,alexclarke@chromium.org,thomasanderson@chromium.org Change-Id: I3688bc4230c71eb1c0ddff896ccdf34255c788bf No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 791838 Reviewed-on: https://chromium-review.googlesource.com/906846Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/master@{#535169}
-
François Degros authored
See the discussion in r894962. It was agreed that the removed code is not necessary anymore. Change-Id: I6e79b0729efe2ed0f28842041383d2c3f35895d4 Reviewed-on: https://chromium-review.googlesource.com/905722Reviewed-by:
Bernhard Bauer <bauerb@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Commit-Queue: François Degros <fdegros@chromium.org> Cr-Commit-Position: refs/heads/master@{#535168}
-
Andrey Kosyakov authored
It's a flaky timeout on most platforms. TBR: clamy NOTRY: true Bug: 809488 Change-Id: Idfa6896f55622c5b79b7ffc81fe008241991daa3 Reviewed-on: https://chromium-review.googlesource.com/907646Reviewed-by:
Andrey Kosyakov <caseq@chromium.org> Commit-Queue: Andrey Kosyakov <caseq@chromium.org> Cr-Commit-Position: refs/heads/master@{#535167}
-
rbpotter authored
Split from https://crrev.com/c/902668 Bug: 809738 Change-Id: I6f462c82370238a79baee437eb7020990334e8fd Reviewed-on: https://chromium-review.googlesource.com/905984 Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#535166}
-
Chromium WPT Sync authored
Using wpt-import in Chromium 88a9ae6d. Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/12031 Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md Directory owners for changes in this CL: foolip@chromium.org: external/wpt/compat TBR=jsbell No-Export: true Change-Id: I0846390465de01ed986185559a64c5aa0d6667b2 Reviewed-on: https://chromium-review.googlesource.com/906678 Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Reviewed-by:
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Cr-Commit-Position: refs/heads/master@{#535165}
-
Klaus Weidner authored
The "WebVR FPS" metric was also counting non-WebVR submitted frames such as the "WebVR isn't working" warning, this is unhelpful for automated tests which erroneously reported broken presentation as a FPS improvement. Fix the metric to only count actual WebVR frames, and export a separate "VR UI FPS" which counts all frames submitted to GVR, including non-WebVR UI. Change-Id: I6efe93b55635596e547efb246ac9c6aefabc36a5 Reviewed-on: https://chromium-review.googlesource.com/907185Reviewed-by:
Michael Thiessen <mthiesse@chromium.org> Commit-Queue: Klaus Weidner <klausw@chromium.org> Cr-Commit-Position: refs/heads/master@{#535164}
-
Ria Jiang authored
RenderWidgetHostInputEventRouter operates in DIP but HitTestQuery uses pixels. Convert event location to be in pixels before asking HitTestQuery for targeting and convert the transformed location back to DIP after receiving that from HTQ. Bug: 750755 Test: will add along with other browsertests (crbug/810121) Change-Id: I0561dd9a4ed73bb1c2ede019e9ee09aa33e1e08c Reviewed-on: https://chromium-review.googlesource.com/907340 Commit-Queue: Ria Jiang <riajiang@chromium.org> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Cr-Commit-Position: refs/heads/master@{#535163}
-
Sahel Sharify authored
The fling progress must get called on begin frame in rwhv_child_frame. rwhv_android and rwhv_aura are already calling ProgressFling on begin frame, I missed to do the same thing in rwhv_child_frame and it was breaking the fling on a oopif. Bug: 809069 Test: SitePerProcessBrowserTest.GestureFlingStart Change-Id: I4319f5cc9fe5863331f8babf4cde3a08d773f106 Reviewed-on: https://chromium-review.googlesource.com/901959 Commit-Queue: Sahel Sharifymoghaddam <sahel@chromium.org> Reviewed-by:
Timothy Dresser <tdresser@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#535162}
-
Sergey Ulanov authored
After crrev.com/535118 DIR_MODULE fails on Fuchsia (before that change it wasn't working correctly, but GetPath() was returning true). Updating the test accordingly. TBR=danakj@chromium.org Change-Id: I9ddcc9e55a35472d38eb563fb72cf9e956928ded Reviewed-on: https://chromium-review.googlesource.com/907536Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
Scott Graham <scottmg@chromium.org> Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> Cr-Commit-Position: refs/heads/master@{#535161}
-
Krishna Govind authored
R=abdulsyed@chromium.org Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs Change-Id: Ifac91eaa04f12abf99b7b4af5f501fec547fc595 Reviewed-on: https://chromium-review.googlesource.com/907547Reviewed-by:
Krishna Govind <govind@chromium.org> Cr-Commit-Position: refs/heads/master@{#535160}
-
Chris Blume authored
memset(0) is a common way to value initialze in C because in C it is very common for 0 bits to represet a value-initialized state. In C++ this is still common, but less so. But C++ also provides a way to explicitly value initialize. Rely on value initialization instead of memset(0) when the intent isn't "set these bits to zero". BUG=810088 Change-Id: I5736f072b101df846de9c2db15b29230a0efb3fb Reviewed-on: https://chromium-review.googlesource.com/907290Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Chris Blume <cblume@chromium.org> Cr-Commit-Position: refs/heads/master@{#535159}
-
Scott Violet authored
This is necessary for unit32_t usage in file. BUG=none TEST=none Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel Change-Id: I20ea2e493c5f9158a381e7e72f225b3aab675add Reviewed-on: https://chromium-review.googlesource.com/907172Reviewed-by:
Fady Samuel <fsamuel@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#535158}
-
Scott Graham authored
Most recently https://build.chromium.org/p/chromium.fyi/builders/Fuchsia%20%28dbg%29/builds/15991 TBR: wez@chromium.org Bug: 768436, 792310 Change-Id: I836a3e918bf67a0780d781bea1b64fa750f75ef3 Reviewed-on: https://chromium-review.googlesource.com/907531 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by:
-
Daniel Murphy authored
Session storage has two different namespace ids. One for storage on disk, and another for the runtime representation. This removes the int ids used for the runtime representation of a session storage namespace in favor of the string GUID persisted on disk. This refactor simplifies the mojo migration of session storage. Change-Id: I09fe1081a9b40e28f3bdd22b5b0fd43e0495df2a Reviewed-on: https://chromium-review.googlesource.com/885087Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Marijn Kruisselbrink <mek@chromium.org> Commit-Queue: Daniel Murphy <dmurph@chromium.org> Cr-Commit-Position: refs/heads/master@{#535156}
-
https://chromium.googlesource.com/catapult.git/+log/c03d5fb17adb..df24d5192b8b $ git log c03d5fb17..df24d5192 --date=short --no-merges --format='%ad %ae %s' 2018-02-07 nednguyen Revert "Revert "[Telemetry] Preserve shared diagnostics added in JavaScript"" 2018-02-07 sullivan Revert "[Telemetry] Preserve shared diagnostics added in JavaScript" 2018-02-07 eakuefner [Telemetry] Add PageTestResults.Skip hook 2018-02-07 eakuefner [Telemetry] Add PageTestResults.Fail hook 2018-02-07 eakuefner [Telemetry] Remove PageTestResults.histograms getter Created with: roll-dep src/third_party/catapult The AutoRoll server is located here: https://catapult-roll.skia.org 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=master.tryserver.chromium.android:android_optional_gpu_tests_rel TBR=sullivan@chromium.org Change-Id: I70c927c10cc8bd3f21fdcdfa1308f82fe89c44a1 Reviewed-on: https://chromium-review.googlesource.com/907338Reviewed-by:
catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#535155}
-
Andrey Kosyakov authored
This reverts commit e3b18767. Reason for revert: this likely broke telemetry_perf_unittests on Linux debug bots: https://ci.chromium.org/buildbot/chromium.linux/Linux%20Tests%20%28dbg%29%281%29/70144 To reproduce, run ./tools/perf/run_tests --browser=debug benchmarks.system_health_smoke_test.SystemHealthBenchmarkSmokeTest.system_health.memory_desktop.browse_accessibility:tech:codesearch Original change's description: > Add hooks for AXTreeDelegate when a relation target changes > > > Problem > Suppose a node a has an active descendant b. A page author might change |b| to aria-selected="true" immediately after setting |b| to be the active descendant. > As a result, we have the events and actions: > active descendant changed on |a| > client gets event on |a| and emits output > attribute changed on |b| > client gets attribute changed on |b| but focus remains over |a| > > Solution > > Let the client know about changes in its related nodes. > For example, changes to |b| would cause an event on |a|. > > Bug: 808061 > Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation > Change-Id: I58a3d99d3187db348320223f0bde588015ab6f55 > Reviewed-on: https://chromium-review.googlesource.com/899862 > Commit-Queue: David Tseng <dtseng@chromium.org> > Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org> > Cr-Commit-Position: refs/heads/master@{#534885} TBR=dmazzoni@chromium.org,dtseng@chromium.org,nektar@chromium.org,aleventhal@chromium.org Change-Id: Icc230ef0afa0f8b0828c573ec18c5a2eb13eeed9 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 808061 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Reviewed-on: https://chromium-review.googlesource.com/906844Reviewed-by:
-
https://skia.googlesource.com/skia.git/+log/4043702b9ac2..eac2090b46a1 $ git log 4043702b9..eac2090b4 --date=short --no-merges --format='%ad %ae %s' 2018-02-07 angle-skia-autoroll Roll skia/third_party/externals/angle2/ b9d1daa06..00155d58e (1 commit) 2018-02-07 skcms-skia-autoroll Roll skia/third_party/externals/skcms/ aa884af96..14aee793f (1 commit) 2018-02-07 skcms-skia-autoroll Roll skia/third_party/externals/skcms/ fdf53e5d5..aa884af96 (2 commits) 2018-02-07 robertphillips Remove GrStencilAndCoverTextContext 2018-02-07 angle-skia-autoroll Roll skia/third_party/externals/angle2/ fd66b81e2..b9d1daa06 (1 commit) 2018-02-07 mtklein Reland "remove SkCanvas::kIsOpaque_SaveLayerFlag" Created with: roll-dep src/third_party/skia The AutoRoll server is located here: https://autoroll.skia.org 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=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel TBR=bsalomon@chromium.org Change-Id: I429b455311e655db41947c4bf592644a5f989aab Reviewed-on: https://chromium-review.googlesource.com/907211 Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#535153}
-
John Chen authored
On the ChromeDriver Android build bot on the waterfall, automatically update the Chrome app when necessary. Change-Id: I1af1bb8835c1fea63493b5f76a98923067744f13 Reviewed-on: https://chromium-review.googlesource.com/907334 Commit-Queue: John Chen <johnchen@chromium.org> Reviewed-by:
Jonathon Kereliuk <kereliuk@chromium.org> Cr-Commit-Position: refs/heads/master@{#535152}
-
Aidan Wolter authored
This will allow Android APK targets to provide a list of shared libraries to not link into Java. This can occur when a native dependency includes a .so file as a runtime dep but does not actually depend on it at link time. BUG=b:73008622 TEST=Build and run release target with specific exclude Change-Id: I5bd7e5a061420fafcafed7001767499d4326a269 Reviewed-on: https://chromium-review.googlesource.com/905695Reviewed-by:
agrieve <agrieve@chromium.org> Commit-Queue: Aidan Wolter <awolter@chromium.org> Cr-Commit-Position: refs/heads/master@{#535151}
-
Mike Baxley authored
The utility it calls returns bool, but this method had been ignoring the results. This results in tests failing later than they should. Also make add WARN_UNUSED_RESULT annotation to this method. Bug: 807789 Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs Change-Id: I832f025028f555911bcad46b6d229a0be580ca81 Reviewed-on: https://chromium-review.googlesource.com/896832Reviewed-by:
Eugene But <eugenebut@chromium.org> Commit-Queue: Mike Baxley <baxley@chromium.org> Cr-Commit-Position: refs/heads/master@{#535150}
-
Dominick Ng authored
This CL: * renames methods on WebappTestPage to be more consistent * removes duplicated code in AppBannerManageTest * removes all mention of manifest_test_page.html from files other than WebappTestPage.java BUG=806923 Change-Id: I9a7e21fae6c0b3a856dbf57433cc849cabe24834 Reviewed-on: https://chromium-review.googlesource.com/905246 Commit-Queue: Dominick Ng <dominickn@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Cr-Commit-Position: refs/heads/master@{#535149}
-
Victor Costan authored
We currently use the system-supplied SQLite library on iOS. This is not the end of the world, because we require iOS 10.0+, which means SQLite 3.14+, which has the features that Chrome uses. iOS is also special in that we don't ship Blink, so we don't expose SQLite via WebSQL -- we control all the other SQL queries we send to SQLite, so SQLite security bugs aren't easily exploitable. At the same time, USE_SYSTEM_SQLITE means Chrome for iOS uses an entirely different SQLite build that most developers don't run. This makes it more likely that we'll introduce bugs or crashes, and makes it more difficult to investigate existing bugs/crashes. In theory, USE_SYSTEM_SQLITE seems appealing on Android and Linux. In practice, the idea isn't workable on either platform. * On Android, not shipping our own SQLite would cut down APK size by a few hundred KB. However, Android doesn't have a great upgrade story before Lollipop (5.0), and we still support KitKat (4.4). SQLite is exposed via WebSQL on Android, so we must be in control of SQLite upgrades. * Linux distributions would like to ship Chromium builds linked against their SQLite copies. However, https://crbug.com/807487 suggests that USE_SYSTEM_SQLITE on Linux would result in unacceptable stability. The root cause of the bug was that NSS can load SQLite on Linux, resulting in SQLite getting initialized outside our control. Even if we could fix that bug (via a dependency from //crypto to //sql), we'd still have to chase all the libraries that might potentially initialize SQLite. Today we believe that NSS is the only library in that set, but we simply don't have the bandwidth to justify investigating the bug reports that will come if we miss something. In conclusion, there is no platform where USE_SYSTEM_SQLITE is desirable and viable. So, this CL removes USE_SYSTEM_SQLITE from the codebase. This will cause the iOS build to increase by a few hundred KB. This price buys us one less difference between iOS and every other platform, and increased OS stability in the long run, as iOS bugs / crashes will be easier to diagnose. Bug: 22208, 299684, 372584, 807093, 807487 Cq-Include-Trybots: master.tryserver.chromium.mac:ios-device Change-Id: I1bd64bd93527624e197bd082c725a952c8b3c430 Reviewed-on: https://chromium-review.googlesource.com/898223 Commit-Queue: Victor Costan <pwnall@chromium.org> Reviewed-by:
Chris Mumford <cmumford@chromium.org> Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Cr-Commit-Position: refs/heads/master@{#535148}
-
Sahel Sharify authored
Android relies on getting the notification when a fling cancels/stops. This cl calls client_->DidStopFlinging() in input_router_impl which used to get called after a DidStopFlinging message from renderer. Bug: 808587 Test: FlingControllerTest.ControllerNotifiesTheClientAfterFlingStart Change-Id: Icfd7966c19b8f4c770163bb4973548ddc50b35dc Reviewed-on: https://chromium-review.googlesource.com/907412Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Commit-Queue: Sahel Sharifymoghaddam <sahel@chromium.org> Cr-Commit-Position: refs/heads/master@{#535147}
-
Greg Thompson authored
BUG=511300 Change-Id: I9f75ac645097a3333027c433db2e02d869d7fd9a Reviewed-on: https://chromium-review.googlesource.com/891820 Commit-Queue: Greg Thompson <grt@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#535146}
-
dpapad authored
TBR=atwilson Bug: 800502 Change-Id: I827b23793d87770228b29f0e7c0ea65e3d455c73 Reviewed-on: https://chromium-review.googlesource.com/857814Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#535145}
-
Matt Wolenetz authored
Removes crash expectation now that the root cause CL itself was reverted. See https://bugs.chromium.org/p/chromium/issues/detail?id=809998#c5. BUG=809998 Change-Id: Ia7ad92ce41c34aba974f5a37f64c7a26f88ffb4d Reviewed-on: https://chromium-review.googlesource.com/907428Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org> Cr-Commit-Position: refs/heads/master@{#535144}
-
Christopher Grant authored
Now, when there is no URL to show, we show a hint instead. This triggered a cleanup of the "no URL" logic in the texture, and in turn, completion of a TODO that was floating in that code. BUG= Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_vr;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Change-Id: I82742251c477147eb9ecb10ee161f67c99c63bd9 Reviewed-on: https://chromium-review.googlesource.com/907179Reviewed-by:
Ian Vollick <vollick@chromium.org> Commit-Queue: Christopher Grant <cjgrant@chromium.org> Cr-Commit-Position: refs/heads/master@{#535143}
-
https://webrtc.googlesource.com/src.git/+log/5684921a16af..1829af6a390c $ git log 5684921a1..1829af6a3 --date=short --no-merges --format='%ad %ae %s' Created with: roll-dep src/third_party/webrtc The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org 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=master.tryserver.chromium.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng;master.tryserver.chromium.win:win-msvc-dbg TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I2cbe39a1b3a8c4a8575db65ff76e6f8f8bf95189 Reviewed-on: https://chromium-review.googlesource.com/907468 Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#535142}
-
Kevin Marshall authored
Chromecast builds include a number of shared libraries, but Fuchsia's shared library support from within a package is still undefined, in addition to the packaging script's handling of libraries. Bug: 810069 Change-Id: I5b6a9f4597d1f760710f907e56ac97ac2c99c9e2 Reviewed-on: https://chromium-review.googlesource.com/907329Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Commit-Queue: Kevin Marshall <kmarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#535141}
-
Sergey Ulanov authored
Previously font render styler logic was mostly platform specific, which made it hard to ensure that font rendering is consistent across supported platforms. This CL moves code previously used on Linux and Android, so it can be shared with Fuchsia. 1. FontRenderStyle class out of linux directory and renames it to WebFontRenderStyle. 2. Removed WebFontRendering class, which allows to remove one layer between content and font config stored in FontRenderStyle. 3. Default font size now is stored in FontCache instead of LayoutThemeFontProvider. Mainly for consistency, since FontCache is responsible for handling all other font-related settings. With these changes font rendering on Fuchsia is consistent with Linux, which will allow to reuse layout test expectations. In future WebFontRenderStyle can be used on Windows as well. Bug: 778467, 808221 Change-Id: I6a7ef7e87f4c51e9d78d077c6cb796f3cbe5c8e1 Reviewed-on: https://chromium-review.googlesource.com/896839 Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:Dominik Röttsches <drott@chromium.org> Reviewed-by:
Pavel Feldman <pfeldman@chromium.org> Cr-Commit-Position: refs/heads/master@{#535140}
-
Pavel Feldman authored
This change also unifies the logic for serving bundled versions of the front-end. Change-Id: I2b1f4e87077332d2c9fc9ef9fd1b1bf85d0d68d1 TBR: updating clients wrt API changes Reviewed-on: https://chromium-review.googlesource.com/905983Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#535139}
-
Peng Huang authored
Bug: None Change-Id: I6a33ead67ef4447228ee05ca30cc2cac83d0119d Reviewed-on: https://chromium-review.googlesource.com/907379 Commit-Queue: Peng Huang <penghuang@chromium.org> Reviewed-by:
Antoine Labour <piman@chromium.org> Cr-Commit-Position: refs/heads/master@{#535138}
-
Peng Huang authored
Update Vulkan headers to 1.0.68, because Skia requests newer vulkan headers. This CL also fixes skia/BUILD.gn, so we can find libvulkan.so in /usr/lib/x86_64-linux-gnu on glinux. Change-Id: I5d3e36093a56e2e2af5eff788830c1f85c32f9f5 Reviewed-on: https://chromium-review.googlesource.com/905323Reviewed-by:
Brian Salomon <bsalomon@chromium.org> Commit-Queue: Peng Huang <penghuang@chromium.org> Cr-Commit-Position: refs/heads/master@{#535137}
-
Nektarios Paisios authored
Bug: 806317 R=dmazzoni@chromium.org, dtrainor@chromium.org Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I3f563f02e201389e2fec63ec4230cad75bc7c265 Reviewed-on: https://chromium-review.googlesource.com/882103Reviewed-by:
Nektarios Paisios <nektar@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Hector Carmona <hcarmona@chromium.org> Commit-Queue: Nektarios Paisios <nektar@chromium.org> Cr-Commit-Position: refs/heads/master@{#535136}
-
Daniel Murphy authored
Bug: 796818 Change-Id: I9955a1bc86404e8c68e373bf572a99192e8f7e4c Reviewed-on: https://chromium-review.googlesource.com/839021Reviewed-by:
Yuzhu Shen <yzshen@chromium.org> Commit-Queue: Daniel Murphy <dmurph@chromium.org> Cr-Commit-Position: refs/heads/master@{#535135}
-
Francois Doray authored
We are making a change that will cause RunAllTasksUntilIdle() to wait for all tasks running on MessageLoops. This means that a call to RunAllTasksUntilIdle() from a task running on a MessageLoop will deadlock. This CL removes calls to RunAllTasksUntilIdle() from MessageLoop tasks in printers sync intergration tests. Change-Id: I61aa695adf297beb14ec4e96fbb08a30516afd7b Reviewed-on: https://chromium-review.googlesource.com/890000Reviewed-by:
Robert Liao <robliao@chromium.org> Reviewed-by:
Nicolas Zea <zea@chromium.org> Commit-Queue: François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#535134}
-
https://chromium.googlesource.com/angle/angle.git/+log/fd66b81e2e90..00155d58e8b0 $ git log fd66b81e2..00155d58e --date=short --no-merges --format='%ad %ae %s' 2018-02-06 lucferron Vulkan: Implement scissor test and add a simple test for it 2018-01-04 tobine Add Vulkan mock_icd to the build Created with: roll-dep src/third_party/angle The AutoRoll server is located here: https://angle-chromium-roll.skia.org 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=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel TBR=cwallez@chromium.org Change-Id: I2b676bcde43dd3af6aa6faba9b4d258bc25447d8 Reviewed-on: https://chromium-review.googlesource.com/906926 Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#535133}
-
Candice Sy authored
Fix for bug regarding Strict Mode violation during call to update notification. Bug: 809864 Change-Id: Ibbb0b20adf449d2bfa435de882242f0ed0b2f56a Reviewed-on: https://chromium-review.googlesource.com/907209Reviewed-by:
Joy Ming <jming@chromium.org> Commit-Queue: Candice Sy <cmsy@google.com> Cr-Commit-Position: refs/heads/master@{#535132}
-
Andrew Grieve authored
API wasn't introduced until JB MR2. Bug: 808419 Change-Id: I9c4298cbe5ba41d8c92c37b684d064b7e0f0d14a Reviewed-on: https://chromium-review.googlesource.com/905563Reviewed-by:
Richard Coles <torne@chromium.org> Commit-Queue: agrieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#535131}
-
