- 17 Oct, 2018 40 commits
-
-
Tommy Nyquist authored
This reverts commit 5423fd8a. Reason for revert: Breaks Chrome Custom Tabs. Original change's description: > Update UI for unsupported Android OS and make Jelly Bean unsupported. > > This CL updates the UI to show a badge icon in the app menu icon > whenever the user is running Chrome on a currently unsupported Android > version. This badge in the app menu is only displayed once, until the > user taps the app menu icon. If the user does in fact get a new version, > the badge state is reset, and will be shown again. The current behavior > for out of date users stays the same as before (once per cold start). > > In addition, a new menu item is displayed at the top of the menu that > explains that Chrome is unable to update. Nothing happens when you tap > the menu item in the case of an unsupported OS version. > > The new menu item and the new warning message in About Chrome will > always be displayed when the user is in this state, regardless of > whether the app menu has already been tapped (which removes the badge). > > This CL also updates the UI in Settings - About Chrome to show a new > message and a warning icon when the user is running Chrome on an > unsupported version of the Android OS. > > By default, Jelly Bean is considered unsupported after this CL, but this > can be overridden from the variations framework. > > It is possible to use command line flags or chrome://flags for > testing the different states, though that does not impact the > About Chrome screen. > > Binary-Size: This CL adds new assets and the minimal code required. > Bug: 847940 > Change-Id: If128e1692b66c5804928183718000aaf1e2ffaa6 > Reviewed-on: https://chromium-review.googlesource.com/c/1243167 > Commit-Queue: Tommy Nyquist <nyquist@chromium.org> > Reviewed-by: Theresa <twellington@chromium.org> > Cr-Commit-Position: refs/heads/master@{#599369} TBR=nyquist@chromium.org,dtrainor@chromium.org,twellington@chromium.org,mdjones@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 847940 Change-Id: Ifde69d6fe007bf0ace6f1f2517db9c1b07526798 Reviewed-on: https://chromium-review.googlesource.com/c/1286973 Commit-Queue: Tommy Nyquist <nyquist@chromium.org> Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Cr-Commit-Position: refs/heads/master@{#600507}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/a358d622339d..785a26dc649a git log a358d622339d..785a26dc649a --date=short --no-merges --format='%ad %ae %s' 2018-10-17 tikuta@google.com Do not do null pointer arithmetic 2018-10-17 thestig@chromium.org Fix typo in coverage_report.py. 2018-10-17 thestig@chromium.org Fix the static initialization order problem for PartitionAlloc. Created with: gclient setdep -r src/third_party/pdfium@785a26dc649a 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. BUG=chromium:766891,chromium:896117 TBR=dsinclair@chromium.org Change-Id: Idbbb57b832cfcdef43607893a607abbce9f23ee6 Reviewed-on: https://chromium-review.googlesource.com/c/1286750Reviewed-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@{#600506}
-
John Budorick authored
This reverts commit afe32c4a. Reason for revert: possible recipe issue in the required CL. Original change's description: > Build chrome_apk on the chromium.perf android builders. > > Requires crrev.com/c/1283629 > > Bug: 817842 > Change-Id: I9bda31e2b98d58cb514e1ba79c0d4a5457a566a2 > Reviewed-on: https://chromium-review.googlesource.com/c/1284752 > Reviewed-by: Juan Antonio Navarro Pérez <perezju@chromium.org> > Reviewed-by: Ned Nguyen <nednguyen@google.com> > Commit-Queue: John Budorick <jbudorick@chromium.org> > Cr-Commit-Position: refs/heads/master@{#600499} TBR=perezju@chromium.org,nednguyen@google.com,jbudorick@chromium.org Change-Id: Icc7f3e46f51c7446690dfcf6940c8bf6a12d2083 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 817842 Reviewed-on: https://chromium-review.googlesource.com/c/1287038Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: John Budorick <jbudorick@chromium.org> Cr-Commit-Position: refs/heads/master@{#600505}
-
Patrick Noland authored
Bug: 891419 Change-Id: I14bff26807974fe6367ef4873d82563f2ffe3dc4 Reviewed-on: https://chromium-review.googlesource.com/c/1274902 Commit-Queue: Patrick Noland <pnoland@chromium.org> Reviewed-by:
Sky Malice <skym@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Cr-Commit-Position: refs/heads/master@{#600504}
-
Vaclav Brozek authored
The fuzzer was able to exercise the codepath causing the crash from the associated bug report (causing an out-of-range error in std::basic_string due to length computed incorrectly because of an error in Unicode handling). Bug: 895578 Change-Id: Icbef8120c18c89227ba7a94c410ec58948d13ae6 Reviewed-on: https://chromium-review.googlesource.com/c/1286453 Commit-Queue: Vaclav Brozek <vabr@chromium.org> Reviewed-by:
Max Moroz <mmoroz@chromium.org> Reviewed-by:
Fabio Tirelo <ftirelo@chromium.org> Cr-Commit-Position: refs/heads/master@{#600503}
-
Saman Sami authored
Make EvictSurfaces take the primary surface instead of the last active surface. Any surface that activates in Viz that is older than the primary will get evicted. Bug: 893731 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel Change-Id: Ibfaed7f4ddfaf73f502c79e4cdf753ec237ea588 Reviewed-on: https://chromium-review.googlesource.com/c/1277826 Commit-Queue: Saman Sami <samans@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Reviewed-by:
Khushal <khushalsagar@chromium.org> Reviewed-by:
Fady Samuel <fsamuel@chromium.org> Reviewed-by:
Antoine Labour <piman@chromium.org> Cr-Commit-Position: refs/heads/master@{#600502}
-
Jochen Eisinger authored
This reverts commit 44256192. Reason for revert: still need to handle the case where an existing profile is locked BUG=896136 Original change's description: > Add a CHECK to non-DICE signin that it's only used for force-signin > > All other use cases are meanwhile migrated or disabled > > R=msarda@chromium.org > > Change-Id: Ieff03c3a46a9ef8fec5c9de8a1aa041a97d9afbf > Reviewed-on: https://chromium-review.googlesource.com/1148211 > Reviewed-by: Mihai Sardarescu <msarda@chromium.org> > Commit-Queue: Jochen Eisinger <jochen@chromium.org> > Cr-Commit-Position: refs/heads/master@{#577827} TBR=msarda@chromium.org,jochen@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Change-Id: I3b7c538682784f57f5142c43ff4bd6c78c14685b Reviewed-on: https://chromium-review.googlesource.com/c/1286278 Commit-Queue: Jochen Eisinger <jochen@chromium.org> Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Cr-Commit-Position: refs/heads/master@{#600501}
-
Toni Barzic authored
These are not used anymore (the verification is separately implemented in Chrome). BUG=846971 Change-Id: Id96f59850f2e56aeb766c34433b5c8a86a72cf4a Reviewed-on: https://chromium-review.googlesource.com/c/1283484Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Commit-Queue: Toni Baržić <tbarzic@chromium.org> Cr-Commit-Position: refs/heads/master@{#600500}
-
John Budorick authored
Requires crrev.com/c/1283629 Bug: 817842 Change-Id: I9bda31e2b98d58cb514e1ba79c0d4a5457a566a2 Reviewed-on: https://chromium-review.googlesource.com/c/1284752Reviewed-by:
Juan Antonio Navarro Pérez <perezju@chromium.org> Reviewed-by:
Ned Nguyen <nednguyen@google.com> Commit-Queue: John Budorick <jbudorick@chromium.org> Cr-Commit-Position: refs/heads/master@{#600499}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/f20c3493eb57..e92aae6b3612 git log f20c3493eb57..e92aae6b3612 --date=short --no-merges --format='%ad %ae %s' 2018-10-17 reed@google.com make legacy shadercontext optional 2018-10-17 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/angle2 1d8a783c9db2..c20ead32ad6d (2 commits) 2018-10-17 khushalsagar@chromium.org fonts: Cache serialized typeface wire data for remote fonts. 2018-10-17 herb@google.com Fix logic error for GrTextBlob mustRegen 2018-10-17 skia-autoroll@skia-public.iam.gserviceaccount.com Roll skia/third_party/skcms fa2161cf791f..c851ac96663d (4 commits) 2018-10-17 skia-recreate-skps@skia-swarming-bots.iam.gserviceaccount.com Update go_deps asset Created with: gclient setdep -r src/third_party/skia@e92aae6b3612 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 BUG=chromium:894200 TBR=egdaniel@chromium.org Change-Id: I03baf792befb769de37ac16efc3537325c358819 Reviewed-on: https://chromium-review.googlesource.com/c/1286112Reviewed-by:
-
Scott Graham authored
Now supporting defining and passing structs from JS -> C++. Bug: 883496 Change-Id: Ib1baf5d435f9e936393e31871f12e71f6ed79f33 Reviewed-on: https://chromium-review.googlesource.com/c/1244891 Commit-Queue: Scott Graham <scottmg@chromium.org> Reviewed-by:
Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#600497}
-
Katie Dillon authored
Added perf tests for worker that measures encoding data with TextEncoder and sending it to a worker as a transferable. Change-Id: I8cf825fda79d596dee0a3a1ce6bdc692b4529552 Reviewed-on: https://chromium-review.googlesource.com/c/1282106Reviewed-by:
Shubhie Panicker <panicker@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Katie Dillon <kdillon@chromium.org> Cr-Commit-Position: refs/heads/master@{#600496}
-
Fady Samuel authored
This metric wasn't really providing a useful signal for anything. Bug: 672962 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel Change-Id: Ia4c5086f1d9705277455c149e1c8138b3a3085b3 Reviewed-on: https://chromium-review.googlesource.com/c/1286899Reviewed-by:
Saman Sami <samans@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Commit-Queue: Fady Samuel <fsamuel@chromium.org> Cr-Commit-Position: refs/heads/master@{#600495}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/383ad4fa29d6..51b2312390d4 git log 383ad4fa29d6..51b2312390d4 --date=short --no-merges --format='%ad %ae %s' 2018-10-17 lalitm@google.com Merge "trace_processor: fix failing diff test and start running on travis" 2018-10-17 hjd@google.com Merge "perfetto-ui: Fix adding tracks" 2018-10-17 fmayer@google.com Merge "profiling: Do not crash client for server problems." Created with: gclient setdep -r src/third_party/perfetto@51b2312390d4 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: Id34e070448b8d6fa3b9d1f3fbbbb60406f5a185d Reviewed-on: https://chromium-review.googlesource.com/c/1286111Reviewed-by:
-
Tarun Bansal authored
Resource Scheduler: Add UMA to record request queuing time broken down by request loading priority Cq-Include-Trybots: luci.chromium.try:linux_mojo Change-Id: I120b9f0b549c76d1f36920c051014afe71462db2 Bug: 895486 Reviewed-on: https://chromium-review.googlesource.com/c/1280145Reviewed-by:
Jesse Doherty <jwd@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Commit-Queue: Tarun Bansal <tbansal@chromium.org> Cr-Commit-Position: refs/heads/master@{#600493}
-
Daniel Bratell authored
In February a number of obsolete header files were deleted but some of them were still listed in sources lists. That might have caused isolate step errors in trybots. Bug: 778580 Change-Id: Ica026a5d157c64f07465f520a15ed2ffab92c234 Reviewed-on: https://chromium-review.googlesource.com/c/1286428Reviewed-by:
-
Ken Rockot authored
The CL https://chromium-review.googlesource.com/c/chromium/src/+/1145692 changes Mojo dispatch behavior and ends up breaking this test. The test is making invalid assumptions about when an InterfacePtr can expect encountered_error() to return true. This CL fixes the test be ensuring that it explicitly waits for an error to be raised on the clipboard interface before continuing. Bug: 895693 Change-Id: I17ea7f994ea9c7d672d0f200aeeaa2c404e04f3f Reviewed-on: https://chromium-review.googlesource.com/c/1286203Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Ken Rockot <rockot@chromium.org> Cr-Commit-Position: refs/heads/master@{#600491}
-
Jared Saul authored
(When a card accrues 3 strikes, future offers to save for that card should show the omnibox save icon, but NOT pop up the bubble. On Android, no offer to save is shown at all.) Bug: 884817 Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs Change-Id: I0d6ad27a4e03d0128970af6e22d2a40a62d0601b Reviewed-on: https://chromium-review.googlesource.com/c/1269524 Commit-Queue: Jared Saul <jsaul@google.com> Reviewed-by:
Sebastien Seguin-Gagnon <sebsg@chromium.org> Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Reviewed-by:
Moe Ahmadi <mahmadi@chromium.org> Cr-Commit-Position: refs/heads/master@{#600490}
-
Jamie Madill authored
GpuCrash_GPUProcessCrashesExactlyOncePerVisitToAboutGpuCrash This test was so flaky it was failing on the ANGLE CQ. Also affects Intel and possibly AMD. Tbr: kbr@chromium.org Bug: 878258 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: I74685596e4162d1d8244ac48f60fcbd12319159d Reviewed-on: https://chromium-review.googlesource.com/c/1286892Reviewed-by:
Jamie Madill <jmadill@chromium.org> Commit-Queue: Jamie Madill <jmadill@chromium.org> Cr-Commit-Position: refs/heads/master@{#600489}
-
Becca Hughes authored
If the "MediaSessionAccelerators" feature is enabled then media keys should behave as system keys. This means they will be handled in ash unless a Chrome app is overridding the behaviour. BUG=894255 Change-Id: I00d8c5a0d8e2c9f73531408f30ddeb56424ad03e Reviewed-on: https://chromium-review.googlesource.com/c/1274885 Commit-Queue: Becca Hughes <beccahughes@chromium.org> Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#600488}
-
David Trainor authored
In order to properly test download home V2 from a Coordinator standpoint, we need to support building/passing in the following parameters: - Whether or not to use the legacy download path (which queries DownloadManagerService/native code that we don't want). - Whether or not to use the legacy download thumbnail path (which queries disk/native code that we don't want). - Letting tests mock out the OfflineContentProvider for a Profile. Getting rid of the legacy code path for these tests is okay because production code will soon do the same once the old code path is fully deprecated. Change-Id: I59784bc53c76b22a81fe6c4f7d43ec43ff7da298 Reviewed-on: https://chromium-review.googlesource.com/c/1277915Reviewed-by:
Xing Liu <xingliu@chromium.org> Commit-Queue: David Trainor <dtrainor@chromium.org> Cr-Commit-Position: refs/heads/master@{#600487}
-
Philip Rogers authored
This patch makes the renderer's compositor use blink runtime feature flags to initialize the layer list setting. With this change we no longer need to separately plumb both a blink feature (i.e., BGPT or SPV2) and a layer list setting. This prevents the confusion situation of having the blink feature flags not match the compositor's layer list setting. This also simplifies the release of Blink Generated Property Trees because we can use the existing processes for transitioning a blink feature from test to experimental to stable. The primary code change is to remove the --enable-layer-lists flag and instead have render_widget.cc initialize the use_layer_lists setting from blink feature flags. This patch also cleans up some plumbing for the --enable-slimming-paint-v2 flag and adds TODOs to remove both --enable-slimming-paint-v2 and --enable-blink-gen-property-trees. Bug: 836884 Cq-Include-Trybots: luci.chromium.try:linux-blink-gen-property-trees;luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: Iffdefc896abb00e6692a0d77b4fde5f628cb8ff5 Reviewed-on: https://chromium-review.googlesource.com/c/1278988Reviewed-by:
enne <enne@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#600486}
-
Clark DuVall authored
This is in preparation for running Network Service out of process. The Network Service process will initially run as a privileged process, so we need to make sure there are enough services to handle the extra process. Bug: 872343 Change-Id: I208c9385a9d48471b2b4ae0b0b23764c18388abc Merge-With: eureka-internal/210477 Reviewed-on: https://chromium-review.googlesource.com/c/1282122Reviewed-by:
Robert Sesek <rsesek@chromium.org> Reviewed-by:
Simeon Anfinrud <sanfin@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Commit-Queue: Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#600485}
-
Hans Wennborg authored
And update references to FileIOClient::Status, because it's now an enum class. Bug: 895475 Change-Id: I1e0e9646416a969e87a9d34dd24b31dc0017889e Reviewed-on: https://chromium-review.googlesource.com/c/1283370Reviewed-by:
Xiaohan Wang <xhwang@chromium.org> Commit-Queue: Hans Wennborg <hans@chromium.org> Cr-Commit-Position: refs/heads/master@{#600484}
-
Jonathan Backer authored
This will make it easy to create a viz::RasterContextProvider from a viz::ContextProvider. TBR=sadrul@chromium.org 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;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I98255264d2a8f5d81d2fae78e7202914fd0428a3 Reviewed-on: https://chromium-review.googlesource.com/c/1286769 Commit-Queue: Jonathan Backer <backer@chromium.org> Reviewed-by:
danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#600483}
-
Sébastien Séguin-Gagnon authored
Has been disabled by default since M67. This was intended as this was a temporary fix to mitigate a bug. Bug: 851295 Change-Id: I7d7200deed7a54fdb61c4d62a683d5f4a98b2164 Reviewed-on: https://chromium-review.googlesource.com/c/1285752Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Reviewed-by:
-
Clark DuVall authored
These were causing the bot to fail: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mojo%20Android/9538 TBR=jam@chromium.org Bug: 893570 Cq-Include-Trybots: luci.chromium.try:linux_mojo Change-Id: I342e931d51a2cc3b81224055f4b1eaafd7141f8c Reviewed-on: https://chromium-review.googlesource.com/c/1286938Reviewed-by:
Clark DuVall <cduvall@chromium.org> Commit-Queue: Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#600481}
-
Johannes Henkel authored
This adds support for protocol::Binary to the headless client API generator, so that the headless shell may take advantage of fields in the protocol that are marked binary. My overall WIP change is in here, and happy to explain more: https://chromium-review.googlesource.com/c/chromium/src/+/1244719 Bug: chromium:891377 Change-Id: I4e46d4b94ad019be62a9a31867d956b00d718adf Reviewed-on: https://chromium-review.googlesource.com/c/1285356Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Johannes Henkel <johannes@chromium.org> Cr-Commit-Position: refs/heads/master@{#600480}
-
Fredrik Söderquist authored
We can only ever hit the same Node in this loop, so even if the query is penetrating/list-based we won't add more to the result if we would happen to hit multiple fragments. It's also easier to read and maybe slightly faster in some cases. Change-Id: I3ce41ce58ef4a188d948690b1840d66e20ac0631 Reviewed-on: https://chromium-review.googlesource.com/c/1277792Reviewed-by:
Philip Rogers <pdr@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#600479}
-
Shakti Sahu authored
This CL adds a max width for image and videos to handle screens that are too wide such as phone in landscape and tablets. Bug: 890526 Change-Id: Icd8acbe0177761c2fd684d2ab2421419857e7be9 Reviewed-on: https://chromium-review.googlesource.com/c/1282203Reviewed-by:
David Trainor <dtrainor@chromium.org> Commit-Queue: Shakti Sahu <shaktisahu@chromium.org> Cr-Commit-Position: refs/heads/master@{#600478}
-
Josh Karlin authored
The test was supposed to verify that, when AdTagging is disabled, frames with ad urls aren't tagged as ads. This wasn't working as intended. It passed regardless of whether or not ad tagging was disabled. What the test wanted to do isn't really possible when an AdTracker isn't present, and it's not when AdTagging is disabled. Changed the test to verify that the AdTracker is not present when AdTagging is disabled. Bug: 856273 Change-Id: I6e31444774ed5c1d1a9156a2a16e92896909d8fa Reviewed-on: https://chromium-review.googlesource.com/c/1273816Reviewed-by:
Nate Chapin <japhet@chromium.org> Commit-Queue: Josh Karlin <jkarlin@chromium.org> Cr-Commit-Position: refs/heads/master@{#600477}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/1d8a783c9db2..78bcd2bec371 git log 1d8a783c9db2..78bcd2bec371 --date=short --no-merges --format='%ad %ae %s' 2018-10-17 jmadill@chromium.org Vulkan: Fix deleting in-use descriptor sets. Created with: gclient setdep -r src/third_party/angle@78bcd2bec371 The AutoRoll server is located here: https://autoroll.skia.org/r/angle-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=geofflang@chromium.org Change-Id: I4aefff962f4a6083f576903d4b22b873a842e643 Reviewed-on: https://chromium-review.googlesource.com/c/1286693Reviewed-by:
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/db22e96f..23e331fe 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: I3e6035923788c550e8f69f30cfcab62a81e8ed26 Reviewed-on: https://chromium-review.googlesource.com/c/1286882Reviewed-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@{#600475}
-
Asa Karlsson authored
Added for code cleanup purposes Change-Id: I55463c1c8cadc1eeac810ad25fc3892813d63d19 Reviewed-on: https://chromium-review.googlesource.com/c/1286461Reviewed-by:
-
Alexander Alekseev authored
This disables Discover App. Bug: 894095 Change-Id: I34dda9c73210f1e56aca9a9ab2ad30e5878a89bd Reviewed-on: https://chromium-review.googlesource.com/c/1286462Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Alexander Alekseev <alemate@chromium.org> Cr-Commit-Position: refs/heads/master@{#600473}
-
Christian Biesinger authored
clear() also frees the backing store of the vector. This patch replaces it with resize(0), which doesn't do that, in cases where that seems unnecessary/undesirable. R=eae@chromium.org Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Change-Id: I2e4360756d2c1a4b0adca18e3f490c46165e73cb Reviewed-on: https://chromium-review.googlesource.com/c/1286884 Commit-Queue: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by:
Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#600472}
-
Elly Fong-Jones authored
This change: 1) Adds an inner WidgetObserver subclass to Button to allow Button to observe its Widget's activation state changing; 2) Introduces a notion of "visual state" to buttons, as distinct from their existing state; the visual state governs how a button is drawn. 3) Has LabelButton use the visual state to decide which image to use instead of the raw state. The end result is that when a LabelButton's Widget deactivates, that LabelButton will take on a disabled appearance. Bug: 848593 Change-Id: If5bd135c254fd36669e76fd39338dc24387602aa Reviewed-on: https://chromium-review.googlesource.com/c/1251330 Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#600471}
-
Qiyu Hu authored
LEListen is not called by Android anymore BUG=b:111367421 TEST=build Change-Id: Id1fecf57810dbb75b34862ac240b8cca8a38c570 Reviewed-on: https://chromium-review.googlesource.com/c/1281684 Commit-Queue: Qiyu Hu <qiyuh@google.com> Reviewed-by:
Greg Kerr <kerrnel@chromium.org> Reviewed-by:
Hidehiko Abe <hidehiko@chromium.org> Cr-Commit-Position: refs/heads/master@{#600470}
-
Lukasz Anforowicz authored
Setting a new window's opener to null and navigating it cross-site used to be a hint to Chrome that it was safe to open the link in a new process. Now that Site Isolation is enabled by default on desktop, cross-site links will always open in a new process, making this unnecessary there. For cases where Site Isolation is not enabled, it is better to use target=_blank rel=noreferrer (or rel=noopener) than this old, non-standard heuristic. See: https://blog.chromium.org/2009/12/links-that-open-in-new-processes.html Bug: 892212, 892375, 884383 Change-Id: I50422cb6bd97f8e0f1d4ef082551ecb355ae104b Reviewed-on: https://chromium-review.googlesource.com/c/1262089Reviewed-by:
James MacLean <wjmaclean@chromium.org> Reviewed-by:
Charlie Reis <creis@chromium.org> Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Cr-Commit-Position: refs/heads/master@{#600469}
-
Adrienne Walker authored
This is according to the gpu spec, and should fix a crash during context lost. Bug: 878258 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: Icabb95055de11c7a743144288898428ecd36bc90 Reviewed-on: https://chromium-review.googlesource.com/c/1285317Reviewed-by:
-
