- 30 Jun, 2018 40 commits
-
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/cf863fb9b446..75e69028956d git log cf863fb9b446..75e69028956d --date=short --no-merges --format='%ad %ae %s' 2018-06-30 angle-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/angle2 6ef24d7824d2..a72f400c5ff3 (3 commits) Created with: gclient setdep -r src/third_party/skia@75e69028956d 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;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=jcgregorio@chromium.org Change-Id: I439cba13a697fbb9a8127cfdd4f20f342299f313 Reviewed-on: https://chromium-review.googlesource.com/1121600Reviewed-by:
skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#571771}
-
Kunihiko Sakamoto authored
- Add a browser test case that uses real (not mocked) CertVerifier. - Re-generate test certificates removing the critical flag of CanSignHttpExchangesDraft extension, since the extension is not known to the OS cert verifiers. Bug: 851778 Change-Id: Ic43319229feddcbaa0349a4f81c995011e63bc7b Reviewed-on: https://chromium-review.googlesource.com/1116406Reviewed-by:
Ryan Sleevi <rsleevi@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#571770}
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/b7b9d02ac020..cf863fb9b446 git log b7b9d02ac020..cf863fb9b446 --date=short --no-merges --format='%ad %ae %s' 2018-06-30 skia-bookmaker@skia-swarming-bots.iam.gserviceaccount.com Update markdown files Created with: gclient setdep -r src/third_party/skia@cf863fb9b446 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;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=jcgregorio@chromium.org Change-Id: Icff1261f808d6498fa02c9d8bc986bbb16391349 Reviewed-on: https://chromium-review.googlesource.com/1121599Reviewed-by:
skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#571769}
-
Aleks Totic authored
This test's baseline was incorrect. Child's writing mode is influencing its offset inside parent. IE matches NG rendering. Bug: 740993 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Change-Id: I779db404ca3e4c8960a95e09beaa854294260dca Reviewed-on: https://chromium-review.googlesource.com/1121247 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#571768}
-
Chromite Chromium Autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/de3a6f421ec7..3f6e3cd26961 git log de3a6f421ec7..3f6e3cd26961 --date=short --no-merges --format='%ad %ae %s' 2018-06-30 vapier@chromium.org cros_portage_upgrade: restore functionality Created with: gclient setdep -r src/third_party/chromite@3f6e3cd26961 The AutoRoll server is located here: https://chromite-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. BUG=chromium:858925 TBR=chrome-os-gardeners@chromium.org Change-Id: I845a9b78083e625400501c859431e2d32032f74e Reviewed-on: https://chromium-review.googlesource.com/1121598Reviewed-by:
Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#571767}
-
fuchsia-sdk-chromium-autoroll authored
The AutoRoll server is located here: https://fuchsia-sdk-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=luci.chromium.try:fuchsia_arm64_cast_audio;luci.chromium.try:fuchsia_x64_cast_audio TBR=cr-fuchsia+bot@chromium.org Change-Id: I6c29dc6a3051500d6e68616c22c300e8b3689a4e Reviewed-on: https://chromium-review.googlesource.com/1121686Reviewed-by:
Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#571766}
-
Olga Sharonova authored
Bug: 832666 Change-Id: I4dfafd0d6d9d4867dc4c7460644a7166ad5e6e8c Reviewed-on: https://chromium-review.googlesource.com/1120502Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Commit-Queue: Olga Sharonova <olka@chromium.org> Cr-Commit-Position: refs/heads/master@{#571765}
-
afdo-chromium-autoroll authored
This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 The AutoRoll server is located here: https://afdo-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. TBR=gbiv@chromium.org Change-Id: I284246df11c4d73f1a3a6ad70442366373a63f6c Reviewed-on: https://chromium-review.googlesource.com/1121683Reviewed-by:
afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#571764}
-
Gabriel Charette authored
These metric help evaluate whether scheduled sleeps (especially long ones) tend to be the cause of the next wakeup or not. This will influence the upcoming redesign of delayed tasks management. The time histogram was extended to 14 days since that's the maximum possible cap we will enforce @ crbug.com/850450#c3. With 50 buckets that still yields 7 buckets under 16ms so we get proper resolution in the fast range too. This will also, as a side-effect of not doing delayed tasks logic when ShouldQuitWhenIdle(), result in disabling hi-resolution timers when the loop is QuitWhenIdle(). Not that this will matter much for power per this mostly being a test-only operation but always nice to reduce time spent under hi-res timers. Bug: 850450, 786597, 854237 Change-Id: Ic552a512f534fc04162a3d6b53c6043621bb3fcf Reviewed-on: https://chromium-review.googlesource.com/1094301 Commit-Queue: Gabriel Charette <gab@chromium.org> Reviewed-by:
François Doray <fdoray@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Cr-Commit-Position: refs/heads/master@{#571763}
-
webrtc-chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/20b4b0dcf066..5a482847e95b git log 20b4b0dcf066..5a482847e95b --date=short --no-merges --format='%ad %ae %s' 2018-06-30 buildbot@webrtc.org Roll chromium_revision 810d8218..f06b8215 (571617:571725) Created with: gclient setdep -r src/third_party/webrtc@5a482847e95b 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=luci.chromium.try:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng BUG=chromium:None TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I00245850bdb65ca49628e8c219d61d7dcca7baf2 Reviewed-on: https://chromium-review.googlesource.com/1121597Reviewed-by:
webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#571762}
-
Yi Gu authored
TBR=klausw@chromium.org NOTRY=True Bug: 859270 Change-Id: I084037c5686e6ab7ac047556b64ff9dc49b41245 Reviewed-on: https://chromium-review.googlesource.com/1121676Reviewed-by:
Yi Gu <yigu@chromium.org> Commit-Queue: Yi Gu <yigu@chromium.org> Cr-Commit-Position: refs/heads/master@{#571761}
-
dpapad authored
Instead "dom-module id=" should be used everywhere. This change makes CrSettingsFocusRowBehavior.FocusTest pass in Polymer 2. Bug: 739532 Change-Id: I9ae09e78e5239bc7432845d4ced9632811d4a7cc Reviewed-on: https://chromium-review.googlesource.com/1121582Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#571760}
-
Aleks Totic authored
We were painting text in all paint phases, causing some tests to crash. Similar routine: LineBoxListPainter::Paint only paint during the foreground/selection phases. This fixes 8 crashes, and removes some no longer necessary baselines. Bug: 714962 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng;luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: Ib4819b3dfee58256f398ef6f123553eb34107ec5 Reviewed-on: https://chromium-review.googlesource.com/1121545 Commit-Queue: Aleks Totic <atotic@chromium.org> Reviewed-by:
Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#571759}
-
Kenneth Russell authored
The underlying bug should be fixed. Tbr: ynovikov@chromium.org Bug: 857112 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 Change-Id: Ie0f277447d01644f0c76134d6d7d570f5f03d8fc Reviewed-on: https://chromium-review.googlesource.com/1121595Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#571758}
-
Yi Gu authored
Mark virtual/threaded/external/wpt/feature-policy/experimental-features/vertical-scroll-touch-block-manual.tentative.html. timeout on Win7 TBR=ekaramad@chromium.org NOTRY=True Bug: 850964 Change-Id: I9ae6e227f3ab158c7aa93217358cbae11ba2ede4 Reviewed-on: https://chromium-review.googlesource.com/1121633Reviewed-by:
Yi Gu <yigu@chromium.org> Commit-Queue: Yi Gu <yigu@chromium.org> Cr-Commit-Position: refs/heads/master@{#571757}
-
Bill Orr authored
These tests were flakily broken by a recent change to introduce a mojo interface where a C++ interface once was. During destruction, there was a race between an async mojo binding error vs. GvrDevice destruction. If GvrDevice is destroyed too early, we don't get the disconnect message and the GvrDelegate is never told that we have exited presentation. The fix is to check whether we are presenting in GvrDevice's destructor, and treat destruction as another signal to stop presentation. TBR=mthiesse,bsheedy Bug: 859217 Change-Id: I0c47da28d4c61ad44839d0b3c1dff1240d2e034d Reviewed-on: https://chromium-review.googlesource.com/1121624Reviewed-by:
Bill Orr <billorr@chromium.org> Commit-Queue: Bill Orr <billorr@chromium.org> Cr-Commit-Position: refs/heads/master@{#571756}
-
Yi Gu authored
TBR=wez@chromium.org NOTRY=True Bug: 859151 Change-Id: Id45c6e679ea50523e99a72cf9ae52a7bd1254286 Reviewed-on: https://chromium-review.googlesource.com/1121631Reviewed-by:
Yi Gu <yigu@chromium.org> Commit-Queue: Yi Gu <yigu@chromium.org> Cr-Commit-Position: refs/heads/master@{#571755}
-
rajendrant authored
Network traffic annotations provides an unique hash for each component that creates the URLRequest. This CL records data use against the hashes, so that no client change is needed when new services are added. New service names could be independently added in enums.xml. Different conditions upstream/downstream, app state in background/foreground are added as suffixes to the histogram. Notably, network connection type (cellular/non-cellular) is not added as suffix. This CL also deprecates the histograms DataUse.AllServices.BackgroundKB and DataUse.MessageSize.AllServices.* histograms. Bug: 843715 Change-Id: Iecffb840afa1880bd383972c30e82925b519c18b Reviewed-on: https://chromium-review.googlesource.com/1114061Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Reviewed-by:
Ramin Halavati <rhalavati@chromium.org> Reviewed-by:
Eric Roman <eroman@chromium.org> Reviewed-by:
Ryan Sturm <ryansturm@chromium.org> Commit-Queue: rajendrant <rajendrant@chromium.org> Cr-Commit-Position: refs/heads/master@{#571754}
-
Yi Gu authored
TBR=luoe@chromium.org NOTRY=True Bug: 859064 Change-Id: Ib465b82c39f3d594f95b73df29fe5684020e5bd6 Reviewed-on: https://chromium-review.googlesource.com/1121628Reviewed-by:
Yi Gu <yigu@chromium.org> Commit-Queue: Yi Gu <yigu@chromium.org> Cr-Commit-Position: refs/heads/master@{#571753}
-
Ryan Hamilton authored
Merge internal change: 202544067 Change-Id: Ibf16eef2c6f61fe1e34920494a03a7ae5c93e433 Reviewed-on: https://chromium-review.googlesource.com/1119259Reviewed-by:
Zhongyi Shi <zhongyi@chromium.org> Commit-Queue: Ryan Hamilton <rch@chromium.org> Cr-Commit-Position: refs/heads/master@{#571752}
-
Chris Harrelson authored
TBR=trchen@chromium.org Bug: 855542 Change-Id: I4c06b96829b2e7f18924be69b562ac8ccf5bf3bc Reviewed-on: https://chromium-review.googlesource.com/1121376 Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#571751}
-
Gyuyoung Kim authored
StagingBufferPool has been only supporting the MemoryCoordinator. However, it is not enabled by default. So it would be good if we support the memory pressure handler until the MemoryCoordinator is enabled by default. Especially, it will help low-end devices to reduce memory usage under the out-of-memory situation. Bug: 856527 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I52be2b732199c66ddaac015fb29aae274ff2fb1d Reviewed-on: https://chromium-review.googlesource.com/1114559 Commit-Queue: Gyuyoung Kim <gyuyoung.kim@lge.com> Reviewed-by:
Eric Karl <ericrk@chromium.org> Cr-Commit-Position: refs/heads/master@{#571750}
-
Chromite Chromium Autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/1bf75a651fe5..de3a6f421ec7 git log 1bf75a651fe5..de3a6f421ec7 --date=short --no-merges --format='%ad %ae %s' 2018-06-30 vapier@chromium.org deploy_chrome: drop setuid bit on chrome sandbox 2018-06-29 dgarrett@google.com chromeos_config: Move release builders to swarming. Created with: gclient setdep -r src/third_party/chromite@de3a6f421ec7 The AutoRoll server is located here: https://chromite-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. BUG=chromium:312380,chromium:576409,chromium:853969 TBR=chrome-os-gardeners@chromium.org Change-Id: I545b6ab9a3cf2a6b1bb90c714f8e160275521340 Reviewed-on: https://chromium-review.googlesource.com/1121596Reviewed-by:
Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#571749}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=govind@chromium.org Change-Id: I64d43f73ef31320163291c309ad756f93af8e473 Reviewed-on: https://chromium-review.googlesource.com/1121522Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#571748}
-
Nico Weber authored
Run cast_unittests, cc_unittests, chromedriver_unittests, components_browsertests, snapshot_unittests on the cros bots. Also run printing_unittests on the cros dbg bot (it's already running on the rel bot). These tests already run and pass on the cros memory bots, so it's not clear why they shouldn't run on the regular cros bots. Bug: 843511 Change-Id: Ia845a7477fcab01bbb8df257585cbde4463a9e8c Reviewed-on: https://chromium-review.googlesource.com/1120232Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#571747}
-
Nico Weber authored
Follow-up to https://chromium-review.googlesource.com/c/chromium/src/+/1120225, the test doesn't pass on the 32-bit linux dbg bot. TBR=kbr Bug: 859264,843511 Change-Id: I99ddef5bc637444ccb0023df528123f14bee0fed Reviewed-on: https://chromium-review.googlesource.com/1121521Reviewed-by:
Nico Weber <thakis@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#571746}
-
Eric Karl authored
Now that we use this class from the Viz/Gpu process, we need the @MainDex annotation. Bug: 858835 Change-Id: Ia444f26f25d2d0532bfb15b0ef552dc2995d4a2b Reviewed-on: https://chromium-review.googlesource.com/1119332Reviewed-by:
Bo <boliu@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Eric Karl <ericrk@chromium.org> Cr-Commit-Position: refs/heads/master@{#571745}
-
Nico Weber authored
Found by a marginally improved version of https://chromium-review.googlesource.com/c/chromium/src/+/1097616 , see patch set 4 there. Bug: 843511 Change-Id: I591567c66f6afa63853e23112fcf432fa61006a0 Reviewed-on: https://chromium-review.googlesource.com/1120752Reviewed-by:
Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#571744}
-
angle-chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/6ef24d7824d2..a72f400c5ff3 git log 6ef24d7824d2..a72f400c5ff3 --date=short --no-merges --format='%ad %ae %s' 2018-06-29 jmadill@chromium.org run_code_generation: Compare hashes instead of mtime. 2018-06-29 oysteine@google.com Removed an assert about addTraceEvent not returning empty handles. 2018-06-29 jmadill@chromium.org Vulkan: Add Features class. Created with: gclient setdep -r src/third_party/angle@a72f400c5ff3 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=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:844421 TBR=ynovikov@chromium.org Change-Id: I652601668a8cba23e34ecd78158fb1b70628e6c6 Reviewed-on: https://chromium-review.googlesource.com/1121260Reviewed-by:
angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#571743}
-
pdfium-chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/0894dc84013c..09646f2d0497 git log 0894dc84013c..09646f2d0497 --date=short --no-merges --format='%ad %ae %s' 2018-06-29 tsepez@chromium.org Use UnownedPtr<CXFA_Node> or comment raw pointers as tree nodes. Created with: gclient setdep -r src/third_party/pdfium@09646f2d0497 The AutoRoll server is located here: https://pdfium-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. TBR=dsinclair@chromium.org Change-Id: I4afa3e3d0411134d55fe4a40b5e18295df3f6445 Reviewed-on: https://chromium-review.googlesource.com/1121498Reviewed-by:
pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#571742}
-
Aleks Totic authored
Bug: 635619 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Change-Id: I99071670521a938d87a90bb2d1a7e481f7e74bdb Reviewed-on: https://chromium-review.googlesource.com/1121578Reviewed-by:
Emil A Eklund <eae@chromium.org> Commit-Queue: Aleks Totic <atotic@chromium.org> Cr-Commit-Position: refs/heads/master@{#571741}
-
Bill Orr authored
This reverts commit f0ce7bce. Reason for revert: Found the issue with tests, will rebase with fix. Original change's description: > Revert "Create mojo interfaces to replace VRDevice, XrSessionController" > > This reverts commit f793e166. > > Reason for revert: Some tests are broken - I'll revert to investigate then reland. > > Original change's description: > > Create mojo interfaces to replace VRDevice, XrSessionController > > > > Devices are converted over to XrRuntime. > > > > Bug: 795510 > > Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:linux_vr;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel > > Change-Id: Ibd50a6eb6b5e971ceba260dc46852157222b3228 > > Reviewed-on: https://chromium-review.googlesource.com/1093386 > > Commit-Queue: Bill Orr <billorr@chromium.org> > > Reviewed-by: Daniel Cheng <dcheng@chromium.org> > > Reviewed-by: Michael Thiessen <mthiesse@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#571595} > > TBR=dcheng@chromium.org,mthiesse@chromium.org,billorr@chromium.org,offenwanger@chromium.org > > Change-Id: I496be5fe20f9dc67999aa0cac86c41f79206e841 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: 795510 > Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:linux_vr;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel > Reviewed-on: https://chromium-review.googlesource.com/1121497 > Commit-Queue: Bill Orr <billorr@chromium.org> > Reviewed-by: Bill Orr <billorr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#571710} TBR=dcheng@chromium.org,mthiesse@chromium.org,billorr@chromium.org,offenwanger@chromium.org Change-Id: Ibe4d12804afc6482dc53623436ed1126d1885fc5 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 795510 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:linux_vr;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Reviewed-on: https://chromium-review.googlesource.com/1121636Reviewed-by:
Bill Orr <billorr@chromium.org> Commit-Queue: Bill Orr <billorr@chromium.org> Cr-Commit-Position: refs/heads/master@{#571740}
-
Peter Kasting authored
I'm not opposed to leaving this under Finch control for future experimentation, but I don't really know how to use FEATURE_WITH_PARAMS_VALUE. Bug: 857610, 857282, 855729 Change-Id: Ibe1b9c13003f2da78b241e775f37b2e9ab7e71f7 Reviewed-on: https://chromium-review.googlesource.com/1119362 Commit-Queue: Peter Kasting <pkasting@chromium.org> Reviewed-by:
Bret Sepulveda <bsep@chromium.org> Cr-Commit-Position: refs/heads/master@{#571739}
-
Mrunal Kapade authored
ScriptPromiseProperties.h -> script_promise_properties.h BUG= Change-Id: I0df4d9d80662c67dc895be36b80db1fa698dc896 Reviewed-on: https://chromium-review.googlesource.com/1121242Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Mrunal Kapade <mrunal.kapade@intel.com> Cr-Commit-Position: refs/heads/master@{#571738}
-
Klaus Weidner authored
The "Don't submit exclusive WebXR frames without valid frame ID" patch from https://crrev.com/1117770 was incomplete, it results in closing Mojo connections due to a sanity check that treats the received frame_id==-1 as invalid. Just ignore these on the Renderer side instead of attempting to submit as missing frames. BUG=855722,858838 Change-Id: I5a5c70979be2bb9a2c9429b6efa78fdd6029d4db Reviewed-on: https://chromium-review.googlesource.com/1121344Reviewed-by:
Bill Orr <billorr@chromium.org> Reviewed-by:
Brian Sheedy <bsheedy@chromium.org> Commit-Queue: Klaus Weidner <klausw@chromium.org> Cr-Commit-Position: refs/heads/master@{#571737}
-
Victor Costan authored
This CL changes the signatures of cookieStore.{get,getAll,set,delete} and introduces the CookieStoreDeleteOptions and CookieStoreSetExtraOptions dictionary. The CL also updates the CookieListItem dictionary. TBR=haraken Bug: 729800 Change-Id: Iaa62b5a51cc79b19cb567be30a2f0dda54e326d8 Reviewed-on: https://chromium-review.googlesource.com/1117868 Commit-Queue: Victor Costan <pwnall@chromium.org> Reviewed-by:Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/master@{#571736}
-
Ned Nguyen authored
NOTRY=true # test by CQ TBR=eyaich@chromium.org Bug: 855063,859251 Change-Id: I2df70bc2b258debe1fa723fb8cda4f189db1745d Reviewed-on: https://chromium-review.googlesource.com/1121520Reviewed-by:
Ned Nguyen <nednguyen@google.com> Commit-Queue: Ned Nguyen <nednguyen@google.com> Cr-Commit-Position: refs/heads/master@{#571735}
-
Scott Chen authored
Bug: 857424 Cq-Include-Trybots: luci.chromium.try:closure_compilation Change-Id: I205f279363b21324cc89d7c0ab44bd042beab588 Reviewed-on: https://chromium-review.googlesource.com/1121107Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Scott Chen <scottchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#571734}
-
Orin Jaworski authored
When the steady omnibox is hovered, the location bar smoothly animates to a slightly different shade of gray instead of switching instantly. Bug: 853241 Change-Id: I5c51607a602f7e7245dddd46060d6dc25f4f4581 Reviewed-on: https://chromium-review.googlesource.com/1119494 Commit-Queue: Orin Jaworski <orinj@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#571733}
-
James Cook authored
When an accessibility extension requests an action the request comes into the browser process AutomationManagerAura. We send the action data over mojo to the remote app and dispatch it there using the existing views toolkit accessibility code. TBR=slan@chromium.org Bug: 851578 Test: added unit tests Change-Id: I37fde88af43de4cee45ca563d4b279a3ddeb02d6 Reviewed-on: https://chromium-review.googlesource.com/1118828Reviewed-by:
James Cook <jamescook@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Tom Sepez <tsepez@chromium.org> Commit-Queue: James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#571732}
-