- 21 Sep, 2018 40 commits
-
-
Charles Zhao authored
This will enable HourAppLaunchPredictor to forget old records so that: (1) Recent actions are more considered. (2) App launching records that have not been used for several months will be deleted from the saved model file. Bug: 871674 Change-Id: Iab08dfedc3b10cb9985030f1141a179529e30798 Reviewed-on: https://chromium-review.googlesource.com/1236614 Commit-Queue: Charles . <charleszhao@chromium.org> Reviewed-by:Xiyuan Xia <xiyuan@chromium.org> Reviewed-by:
Jia Meng <jiameng@chromium.org> Cr-Commit-Position: refs/heads/master@{#593339}
-
Robert Ogden authored
Removes the random query param hack and prevents the timeout logic from running in all tests. Bug: 887962, 885252 Change-Id: Icc001d2e6d584228027ae56a12813c02dcaf0b42 Reviewed-on: https://chromium-review.googlesource.com/1239393Reviewed-by:
Ryan Sturm <ryansturm@chromium.org> Commit-Queue: Robert Ogden <robertogden@chromium.org> Cr-Commit-Position: refs/heads/master@{#593338}
-
Francois Doray authored
This CL updates the ProactiveTabFreezeAndDiscard testing config to match variation params that will be used to experiment on stable. Note that we will also experiment with other variation params to assess their impact. The CL also updates the study name to "TooManyTabs", which is the study name used in the server-side config file. Bug: 844426 Change-Id: I3ab5d0d0005843f00c8bb0382ecb66a97670c0fb Reviewed-on: https://chromium-review.googlesource.com/1238996Reviewed-by:
Robert Kaplow (sloooow) <rkaplow@chromium.org> Commit-Queue: François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#593337}
-
Evan Stade authored
1. Remove AshFrameSizeButton dependency on PhantomWindowController via a new interface. For Mash Chrome browser frames, this will be implemented via Mojo (for now, that's a TODO). 2. Add ash::TabletMode utility to //ash/public/cpp, which allows code in //ash/public/cpp to get the status of tablet mode from any process (each process has to provide a callback). 3. Move the files from private Ash to the new directory. Bug: 887051 Change-Id: Ib790a89fae89f02b92b36e1b165d59c9e28b59f7 Reviewed-on: https://chromium-review.googlesource.com/1228978 Commit-Queue: Evan Stade <estade@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#593336}
-
Eric Karl authored
CompositorImplAndroid had sizing logic for gpu::SharedMemoryLimits which was not propogated to Viz. Adding this in. Bug: 886816 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: I15b0c75a3a5778bcd912cebd37fa8273736d97d8 Reviewed-on: https://chromium-review.googlesource.com/1237405Reviewed-by:
Tom Sepez <tsepez@chromium.org> Reviewed-by:
ccameron <ccameron@chromium.org> Commit-Queue: Eric Karl <ericrk@chromium.org> Cr-Commit-Position: refs/heads/master@{#593335}
-
Lukasz Anforowicz authored
This CL also fixes a missing lock that was found by the compile-time analysis in ChildProcessSecurityPolicyImpl::HasPermissionsForFileSystemFile. Bug: 887645 Change-Id: I940ade66bb2d754669c2b5bd408b63c91a1a8d5a Reviewed-on: https://chromium-review.googlesource.com/1237145 Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Reviewed-by:
Charlie Reis <creis@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#593334}
-
Michael Giuffrida authored
ArcRobotAuthCodeFetcher will crash if there is no CloudPolicyClient, which can happen when the device hasn't been online since boot. Bug: 875504 Test: ArcRobotAuthCodeFetcherOfflineBrowserTest Change-Id: Ia5412be9a85cfe5028aa30caf74a7b4562d342e7 Reviewed-on: https://chromium-review.googlesource.com/1237255 Commit-Queue: Michael Giuffrida <michaelpg@chromium.org> Reviewed-by:
Yury Khmel <khmel@chromium.org> Cr-Commit-Position: refs/heads/master@{#593333}
-
Kenneth Russell authored
The bots have been upgraded to 10.13.6 and the graphs had to be updated as well. Bug: 885337 Tbr: zmo@chromium.org No-Try: True Change-Id: I676817f3595fee7667c521437bdb907299c08bab Reviewed-on: https://chromium-review.googlesource.com/1239413 Commit-Queue: Kenneth Russell <kbr@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#593332}
-
Tarun Bansal authored
This reverts commit d4d1506d. Reason for revert: Hitting the DCHECK on Chromium startup. crbug.com/888087 Original change's description: > [X11] Don't clear WM state bits when a window is unmapped > > _NET_WM_STATE holds the window state which may be eg: maximized, fullscreen, > minimized, etc. In shutdown, Chrome queries this state so that it can restore > browser windows to the correct state on the next launch. The problem is that > Chrome queries this state (hundreds of times, in fact) after the window has > already gone away. The EWMH spec requires window managers to delete the > _NET_WM_STATE property when a window is unmapped [1], so the state that Chrome > was getting was invalid. > > This CL saves the state when a window becomes unmapped, and includes some small > cleanups. > > [1] https://standards.freedesktop.org/wm-spec/wm-spec-1.3.html#idm140130317598336 > > BUG=882258 > R=sky > > Change-Id: Iacc43563cd54ade77ac83a580ed24434b6802c91 > Reviewed-on: https://chromium-review.googlesource.com/1226645 > Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> > Reviewed-by: Scott Violet <sky@chromium.org> > Cr-Commit-Position: refs/heads/master@{#592570} TBR=sky@chromium.org,thomasanderson@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 882258,888087 Change-Id: Iac2776b33ec366235e233878dcdbfd8530e2ea0b Reviewed-on: https://chromium-review.googlesource.com/1239355 Commit-Queue: Tarun Bansal <tbansal@chromium.org> Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Cr-Commit-Position: refs/heads/master@{#593331}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/cd5e40e994a7..f4a7342c6fc4 git log cd5e40e994a7..f4a7342c6fc4 --date=short --no-merges --format='%ad %ae %s' 2018-09-21 hjd@google.com trace_processor: Fix sched_tracker_unittest.cc Created with: gclient setdep -r src/third_party/perfetto@f4a7342c6fc4 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: I64c2d4c5b6c154815bdb93d1d2875e03b0d7291c Reviewed-on: https://chromium-review.googlesource.com/1238847Reviewed-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@{#593330}
-
Clark DuVall authored
Note: Many (all?) of the android_webview multiprocess_mode tests fail when running NS OOP. Bug: 881572 Change-Id: Icca5d99cbaa655153d7ae19eb9283dcb3e4c1946 Reviewed-on: https://chromium-review.googlesource.com/1238820 Commit-Queue: Clark DuVall <cduvall@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Cr-Commit-Position: refs/heads/master@{#593329}
-
Shakti Sahu authored
Bug: 885322 Change-Id: Ie8b8c31ca6b8aa1a365c69b30d045b9a6eb02ee8 Reviewed-on: https://chromium-review.googlesource.com/1233115 Commit-Queue: Shakti Sahu <shaktisahu@chromium.org> Reviewed-by:
Min Qin <qinmin@chromium.org> Reviewed-by:
Varun Khaneja <vakh@chromium.org> Cr-Commit-Position: refs/heads/master@{#593328}
-
Dan Sanders authored
This API allows mojom::VideoDecoder clients to get a list of rules that can be used to reject unsupported Initialize() calls without additional IPC. On the GPU side, this information is gathered from the existing VDA SupportedProfiles factory. On the renderer side, GpuVideoAcceleratorFactories is now responsible for this query, which it does upon construction. If a MojoVideoDecoder is initialized before the query has completed, MojoVideoDecoder will call the remote Intitialize() method as normal. Bug: 839951, 522298 Change-Id: I62b1e2f6ad79f096d273d7591da1e98094b9cbfe Reviewed-on: https://chromium-review.googlesource.com/1066620Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Dan Sanders <sandersd@chromium.org> Cr-Commit-Position: refs/heads/master@{#593327}
-
Pedro Amaral authored
The experimentation with different Clear Tab icons is done so removing the logic that allowed for different icons. Bug: 880758 Change-Id: Iff65898d404cbefa3a3b8c0a65af5d396f68578c Reviewed-on: https://chromium-review.googlesource.com/1228511Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Pedro Amaral <amaralp@chromium.org> Cr-Commit-Position: refs/heads/master@{#593326}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/980ce54f..31b2347a 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: If792d9b80550ea70250a1d80f2d4805526973ec9 Reviewed-on: https://chromium-review.googlesource.com/1238830Reviewed-by:
V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#593325}
-
John Rummell authored
Add the encryption scheme used for both the audio and video tracks to the data saved for each media playback. BUG=858855 TEST=new unittests pass Change-Id: I477e3475f6211980d199ab7c873447d70192f719 Reviewed-on: https://chromium-review.googlesource.com/1195924Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Commit-Queue: John Rummell <jrummell@chromium.org> Cr-Commit-Position: refs/heads/master@{#593324}
-
Siddhartha authored
Before this CL lot of proto databases used default write buffer size which is 4MB. Some databases explicitly set write buffer sizes because of telemetry regressions observed. The rest of them were not hit by telemetry stories when they were added. After this CL the default buffer size will be set to 512KB for high end and 128KB for low end devices. Most databases don't store a lot of data, but do a lot of transactions. So, this will cause compaction more often. BUG=851034 Change-Id: Ia0fb28035a8e6e3221ee7dc843924086d062a52b Reviewed-on: https://chromium-review.googlesource.com/1236286 Commit-Queue: Siddhartha S <ssid@chromium.org> Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Reviewed-by:
Min Qin <qinmin@chromium.org> Cr-Commit-Position: refs/heads/master@{#593323}
-
Vladislav Kaznacheev authored
Avoid resizing the badge icon, request it at the required size instead. Bug: 887646 Test: search for "New", see badged "New alarm" action Change-Id: I658356b863dd1334fc9da6187fc7cd86cac7a0d4 Reviewed-on: https://chromium-review.googlesource.com/1239236 Commit-Queue: Vladislav Kaznacheev <kaznacheev@chromium.org> Reviewed-by:
Yury Khmel <khmel@chromium.org> Cr-Commit-Position: refs/heads/master@{#593322}
-
Xiaohan Wang authored
- Fixes ToCdmVideoCodecProfile() to handle VP9 profiles. - Add ToCdmVideoDecoderConfig() helper function. Bug: 592074 Change-Id: I7142fbf8d21e6710f84326235ba1e3b8c52036ee Reviewed-on: https://chromium-review.googlesource.com/1236503Reviewed-by:
John Rummell <jrummell@chromium.org> Commit-Queue: Xiaohan Wang <xhwang@chromium.org> Cr-Commit-Position: refs/heads/master@{#593321}
-
John Budorick authored
Bug: 878777 Change-Id: I7d6727fd36523f37db5f670a46e0957b93cb575d Reviewed-on: https://chromium-review.googlesource.com/1239166 Commit-Queue: John Budorick <jbudorick@chromium.org> Commit-Queue: Ben Pastene <bpastene@chromium.org> Reviewed-by:
Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#593320}
-
Tibor Goldschwendt authored
Bug: 884875 Cq-Include-Trybots: luci.chromium.try:win_optional_gpu_tests_rel Change-Id: I402201609f98425169c56983aafb108bb76cb406 Reviewed-on: https://chromium-review.googlesource.com/1238817Reviewed-by:
agrieve <agrieve@chromium.org> Reviewed-by:
Bill Orr <billorr@chromium.org> Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Cr-Commit-Position: refs/heads/master@{#593319}
-
Khushal authored
Skia doesn't support LCD text for all cases of nested pictures in filters, shaders or picture backed image generators. Make sure we match this for the text analysis canvas in oop raster. R=enne@chromium.org Bug: 878874 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I15c4f2527a9d03dba7f9dcc4e3c999b9a4daebda Reviewed-on: https://chromium-review.googlesource.com/1235151 Commit-Queue: Khushal <khushalsagar@chromium.org> Reviewed-by:
enne <enne@chromium.org> Cr-Commit-Position: refs/heads/master@{#593318}
-
Bruce Dawson authored
While investigating crbug.com/882670 I noticed that the CRT __purecall function was calling the InvalidParameter function instead of the PureCall function. That is happening because the two functions have identical implementations and generate identical code and therefore the linker folds the two functions together. This happens despite compiler optimizations being disabled. This is harmless but causes mild confusion. This CL changes the return code of one of the functions so that the two functions are no longer identical. This change was tested by defining these classes, creating a variable of type Derived, and then checking what call stack appears for the crash in a release build: struct Base { Base() { Middle(); } void Middle() { DerivedFunc(); } virtual void DerivedFunc() = 0; }; struct Derived : public Base { void DerivedFunc() override {} }; I manually confirmed that this fix has the desired effect. Change-Id: I37446600e00a3ee95b009190c471e938ec85e5c0 Reviewed-on: https://chromium-review.googlesource.com/1237539 Commit-Queue: Bruce Dawson <brucedawson@chromium.org> Reviewed-by:Robert Liao <robliao@chromium.org> Cr-Commit-Position: refs/heads/master@{#593317}
-
Lukasz Anforowicz authored
This CL cleans-up URLLoaderFactoryBundle[Info] in preparation for adding initiator-origin-keyed factories in the future (for supporting URLLoaderFactories with extension-specific permissions for requests initiated by content scripts). Changes in the CL: - s/factories/scheme_specific_factories/ - s/factories_info/scheme_specific_factory_infos/ Rationale for the changes above: - Making it more explicit that these factories are keyed by a scheme - Differentiating the name from |initiator_specific_factories| that is planned to be introduced in a follow-up CL (https://crrev.com/c/1228478). - Introducing URLLoaderFactoryBundle::SchemeMap - Introducing URLLoaderFactoryBundleInfo::SchemeMap - Fixes for some of issues reported by: git cl lint - Removing URLLoaderFactoryBundle::RegisterFactory that had no callers. - Making URLLoaderFactoryBundle::GetFactoryForURL protected (it used to be unnecessarily public) - Having ChildURLLoaderFactoryBundle delegate to its base class (URLLoaderFactoryBundle) in its implementation of GetFactoryForURL and CreateLoaderAndStart methods. There are no intended behavior changes in this CL (well except skipping a DCHECK in GetFactoryForURL method so that the method can be reused by subclasses with more relaxed invariants). Bug: 846346 Change-Id: Ibbd07debaf518e2b71cf09a2fd92c8b8104b7411 Reviewed-on: https://chromium-review.googlesource.com/1227135Reviewed-by:Nasko Oskov <nasko@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Cr-Commit-Position: refs/heads/master@{#593316}
-
Xiyuan Xia authored
Bug: 794724 Change-Id: Iba80e83e191f616af9331144a372e281dba49fa2 Reviewed-on: https://chromium-review.googlesource.com/1238441 Commit-Queue: Xiyuan Xia <xiyuan@chromium.org> Reviewed-by:
Yury Khmel <khmel@chromium.org> Cr-Commit-Position: refs/heads/master@{#593315}
-
Vladislav Kaznacheev authored
Previous solution (crrev.com/c/1208692) has to be reverted as it removed badges from a few other search result types where they are actually needed. Bug: 872404 Test: manual Change-Id: I20d3af35a493a52b5a45645e85e5b17f0cbbfeb2 Reviewed-on: https://chromium-review.googlesource.com/1238997Reviewed-by:
Jenny Zhang <jennyz@chromium.org> Commit-Queue: Vladislav Kaznacheev <kaznacheev@chromium.org> Cr-Commit-Position: refs/heads/master@{#593314}
-
Bailey Berro authored
- Switches Network file shares settings page to using sentence casing. Bug: chromium:887677 Change-Id: If7bffe4d4b9ffdf464e1d81d782c0a4033b3fb1a Reviewed-on: https://chromium-review.googlesource.com/1237393Reviewed-by:
Zentaro Kavanagh <zentaro@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Commit-Queue: Bailey Berro <baileyberro@chromium.org> Cr-Commit-Position: refs/heads/master@{#593313}
-
Eric Karl authored
DualBrowserStorySet uses non-standard set-up to create its webview, missing the previous option customization added to PerfBenchmark's CustomizeBrowserOptions. While this should probably be unified, copying the relevant options over for now to un-break the dual browser case. Also disables VizDisplayCompositor, as this is a related unsupported feature, and although things happen to work now, we don't want to rely on that. Bug: 881469 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: I1070210c2a92768795689d4488369c0b589ca9bb Reviewed-on: https://chromium-review.googlesource.com/1236468 Commit-Queue: Eric Karl <ericrk@chromium.org> Reviewed-by:
Ned Nguyen <nednguyen@google.com> Cr-Commit-Position: refs/heads/master@{#593312}
-
Christian Biesinger authored
See also https://chromium.googlesource.com/chromium/src/+/0e94f26e8/third_party/WebKit/Source/wtf/Allocator.md#PartitionAlloc R=rego@igalia.com Change-Id: Icd128c3a970c6b9860ef14aef1f23de218b8f865 Reviewed-on: https://chromium-review.googlesource.com/1238783Reviewed-by:
Javier Fernandez <jfernandez@igalia.com> Commit-Queue: Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#593311}
-
Clark DuVall authored
Looks like the timing info is no longer being used. Bug: 721403 Change-Id: Id99af7695e93026211b97567296daccfd84ed176 Reviewed-on: https://chromium-review.googlesource.com/1238620Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Commit-Queue: Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#593310}
-
Jenny Zhang authored
Since the recommendation app can be shown in both suggestion chip and zero state UI with different dimension, I added a chip_icon in SearchResultMeataData, so that we can load the icons in different dimension without resizing loss. TBR=jianli@chromium.org Bug: 880979 Change-Id: Ibbea1d22eae7c15268bafb1fcca6c9211385b6ed Reviewed-on: https://chromium-review.googlesource.com/1220813 Commit-Queue: Jenny Zhang <jennyz@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#593309}
-
BUG=762641 TBR=stevenjb@google.com, tbarzic@google.com Change-Id: I6699cead1fbbfefdb38c306b941526cf988bb552 Reviewed-on: https://chromium-review.googlesource.com/1237864Reviewed-by:
ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Commit-Queue: Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#593308}
-
Maks Orlovich authored
Bug: 875032 Cq-Include-Trybots: luci.chromium.try:linux_mojo Change-Id: I087bd6a9b62f05ccb853db4e5b04639fab0e4e83 Reviewed-on: https://chromium-review.googlesource.com/1238795Reviewed-by:
Tom Sepez <tsepez@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Reviewed-by:
Nicolas Zea <zea@chromium.org> Commit-Queue: Maks Orlovich <morlovich@chromium.org> Cr-Commit-Position: refs/heads/master@{#593307}
-
Fredrik Söderquist authored
AbsoluteBoundingBoxRectForScrollIntoView and associated helpers did not compute the correct bounding box for SVG shapes (or anything but the SVG root.) Compute the bounding rect using the stroke bounding box. Bug: 803440 Change-Id: If25ca98b686f17a0db699e569460cb4c276f06a0 Reviewed-on: https://chromium-review.googlesource.com/1238458Reviewed-by:
David Bokan <bokan@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#593306}
-
Weiliang Chen authored
There is no need to call SetNeedsPushProperties on each individual setter on LayerImpl, so remove them. LayerImpl's needs to push property status is only useful when they are on pending tree and waiting to push its properties during activation. With PropertyTrees, the change to trigger a LayerImpl's need to push properties on pending trees come from only the main thread's commit. Since Layer pushing properties to LayerImpl SetNeedsPushProperties on LayerImpl, there is no need for each individual setter on LayerImpl to set that status again. R=enne Bug: 854256 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I3cfc0e3898deb6ae08a88c1f715d035dea624c9b Reviewed-on: https://chromium-review.googlesource.com/1234999Reviewed-by:
enne <enne@chromium.org> Commit-Queue: weiliangc <weiliangc@chromium.org> Cr-Commit-Position: refs/heads/master@{#593305}
-
Josh Karlin authored
What: Expand the WebCore.Framebust metric to also measure if the frame initiating the navigation is an ad frame. Why: It might be a good idea to prevent framebusting from same-origin ad iframes without user gesture. This measurement will tell us how common it is. Bug: 885146 Change-Id: I6366094b119b6f220ac1a01ea43662423dc961ee Reviewed-on: https://chromium-review.googlesource.com/1238778 Commit-Queue: Josh Karlin <jkarlin@chromium.org> Reviewed-by:
Nate Chapin <japhet@chromium.org> Cr-Commit-Position: refs/heads/master@{#593304}
-
Chris Lu authored
- Require minimum height equal the height of the favicon for the vertical stackview in TableViewUrlCell - If title and host aren't available, use full url spec. Screenshot: https://drive.google.com/file/d/1C19zooJG80phfS6gDiCnMZQa2NZJd9zA/view?usp=sharing Bug: 878833 Change-Id: I11e91f583f014f88a208478bef767cb70972ce7b Reviewed-on: https://chromium-review.googlesource.com/1235319 Commit-Queue: Chris Lu <thegreenfrog@chromium.org> Reviewed-by:
Sergio Collazos <sczs@chromium.org> Cr-Commit-Position: refs/heads/master@{#593303}
-
Ben Kelly authored
We've seen some anecdotal evidence in local testing that mojo::DataPipe creation can sometimes take milliseconds to complete. Currently there is a pipe created on the ServiceWorker thread for certain FetchEvent respondWith() code paths. This histogram will help us determine if this is introducing jank on the service worker thread. Bug: 888045 Change-Id: I5f36da2dfbde4bd561c605336949e475f45ecb43 Reviewed-on: https://chromium-review.googlesource.com/1239274Reviewed-by:
Mark Pearson <mpearson@chromium.org> Reviewed-by:
Marijn Kruisselbrink <mek@chromium.org> Commit-Queue: Ben Kelly <wanderview@chromium.org> Cr-Commit-Position: refs/heads/master@{#593302}
-
Denis Kuznetsov authored
Postpone Login WebUI initialization if Oobe is not completed until OOBE configuration check is complete. Bug: 854101 Change-Id: If9f7bba80d048d28b8cf17ef57b1558742e7a765 Reviewed-on: https://chromium-review.googlesource.com/1203977 Commit-Queue: Denis Kuznetsov <antrim@chromium.org> Reviewed-by:
Alexander Alekseev <alemate@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#593301}
-
Andrew Grieve authored
This rule was causing @MainDex methods to be obfuscated, even when they were marked as -keep by a previous rule. Turns out that this rule is entirely unnecessary for maintaining @MainDex annotations anyways. Bug: 887954 Change-Id: I3f371d4c24f91e217494f02b45e9401a8628688a Reviewed-on: https://chromium-review.googlesource.com/1238784Reviewed-by:
Sam Maier <smaier@chromium.org> Commit-Queue: agrieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#593300}
-