- 29 Jan, 2018 40 commits
-
-
sebsg authored
The case statement was missing a break. Bug: 806934 Change-Id: I7e51f35a1e418439e7577e757fd5daf182d6c6a7 Reviewed-on: https://chromium-review.googlesource.com/891690Reviewed-by:
Roger McFarlane <rogerm@chromium.org> Commit-Queue: Roger McFarlane <rogerm@chromium.org> Cr-Commit-Position: refs/heads/master@{#532574}
-
Peter Wen authored
No longer enforce full deprecation and unchecked warnings by commandline flags to javac. Greatly reduce verbosity of build output. BUG=805906 Change-Id: I20ac2f56d9bfa5ed946789373eae536089e7506e Reviewed-on: https://chromium-review.googlesource.com/887001 Commit-Queue: Peter Wen <wnwen@chromium.org> Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
agrieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#532573}
-
Vladimir Levin authored
This patch updates several places in the code that assume that LayoutInlines can only contain absolute position elements (and not fixed). This is a step towards making filtered elements be able to contain both absolute and fixed positioned elements. R=chrishtr@chromium.org Bug: 795549 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: Idf970e4343646574bd9c53d064f7578a2f09f3a3 Reviewed-on: https://chromium-review.googlesource.com/882187Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Commit-Queue: vmpstr <vmpstr@chromium.org> Cr-Commit-Position: refs/heads/master@{#532572}
-
Hongchan Choi authored
AudioWorklet::IsReady() checks the state of the worklet object and must be accessed from the main thread. OfflineAudioDestinationHandler::DoOfflineRendering() violates the rule and this CL fixes GetRenderingThread() method to check the assigned worklet thread instead. Bug: 804908 Change-Id: I1ff1f779a3bb75d1715f521a2656a7c6c8c51a9f Reviewed-on: https://chromium-review.googlesource.com/882121Reviewed-by:
Raymond Toy <rtoy@chromium.org> Commit-Queue: Hongchan Choi <hongchan@chromium.org> Cr-Commit-Position: refs/heads/master@{#532571}
-
https://skia.googlesource.com/skia.git/+log/11e5bff1594c..58acd74f55f2 $ git log 11e5bff15..58acd74f5 --date=short --no-merges --format='%ad %ae %s' 2018-01-29 reed validate that contours begin with moveTo 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=bungeman@chromium.org Change-Id: I0981a56b442e8722d60b9d88b95c0c9c9e5f02c6 Reviewed-on: https://chromium-review.googlesource.com/891685Reviewed-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@{#532570}
-
James Cook authored
Previously it was only allowed in developer builds and dev channel builds. I think canary was an oversight. Bug: none Test: option appears in about:flags Change-Id: I3611b0d23f43f53628e03bf1245ca056a1456c0f Reviewed-on: https://chromium-review.googlesource.com/891693Reviewed-by:
Michael Wasserman <msw@chromium.org> Commit-Queue: James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#532569}
-
Jialiu Lin authored
Move LogSyncPasswordHashChange call into password store class, such that "PasswordManager.SyncPasswordHashChange" will only be logged if there is actual change. Bug: 657041 Change-Id: I3afbea76ee9a31376f7a6752b3933cf278328378 Reviewed-on: https://chromium-review.googlesource.com/885243 Commit-Queue: Jialiu Lin <jialiul@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Reviewed-by:
Vadym Doroshenko <dvadym@chromium.org> Cr-Commit-Position: refs/heads/master@{#532568}
-
Lambros Lambrou authored
When receiving a bandwidth estimate of 0 from WebRTC, the host should pause the video stream without crashing. This CL is a simple fix which sets the bucket-emptying time to 1 minute if the rate is set to 0. This is similar to what we already do in FrameProcessingTimeEstimator::EstimatedTransitTime(). Bug: 806918 Change-Id: I43bf24cf54250cc3856adeb4c49809733320d46b Reviewed-on: https://chromium-review.googlesource.com/891671Reviewed-by:
Joe Downing <joedow@chromium.org> Commit-Queue: Lambros Lambrou <lambroslambrou@chromium.org> Cr-Commit-Position: refs/heads/master@{#532567}
-
danakj authored
Instead of the ResourcePool making a ResourceId, which the RasterBufferProvider implementation actualizes into a backing via a write lock, we have the ResourcePool give out a metadata object, and the RasterBufferProvider allocates a backing for it directly. Then, TileManager puts a ResourceId by explicitly asking the ResourcePool to do so, in order to allow the backing to be exported to the display compositor. R=vmpstr@chromium.org Bug: 730660 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel Change-Id: Idc3b127f819e7154414cb7de9897e5309a22b7bc Reviewed-on: https://chromium-review.googlesource.com/882101 Commit-Queue: danakj <danakj@chromium.org> Reviewed-by:
vmpstr <vmpstr@chromium.org> Reviewed-by:
danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#532566}
-
Nico Weber authored
Bug: 177475 R=dalecurtis@chromium.org 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 Change-Id: I5536e4854edf66a0838fe0a89f37bdedfc6bfc7e Reviewed-on: https://chromium-review.googlesource.com/889721Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#532565}
-
dpapad authored
Bug: 738611 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I92e07bca0041ed84a9b45339c89b61d05e8158de Reviewed-on: https://chromium-review.googlesource.com/887779 Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Reviewed-by:
Scott Chen <scottchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#532564}
-
Avi Drissman authored
This modernizes the WebContentsObserver interface. BUG=767526 Change-Id: I55b92fabf7a62cc932124822a91da1ffe2230549 Reviewed-on: https://chromium-review.googlesource.com/889939Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Commit-Queue: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#532563}
-
Eric Lawrence authored
Preload for Strict-Transport-Security several .gov domains that were manually requested. TBR=palmer@chromium.org Change-Id: I9b23ab1c5c10cc2f295ebd33ec24cfbc6a5512ca Reviewed-on: https://chromium-review.googlesource.com/889717Reviewed-by:
Eric Lawrence <elawrence@chromium.org> Commit-Queue: Eric Lawrence <elawrence@chromium.org> Cr-Commit-Position: refs/heads/master@{#532562}
-
Raymond Toy authored
There's no reason to have a limit on the number of concurrent AudioContexts. If the user creates too many, we'll just run out of resources and stop. Bug: 777342 Test: audiocontext-max-contexts.html removed Change-Id: I55ac01e42cc1ffc313db5b93e49db1c4a36a585b Reviewed-on: https://chromium-review.googlesource.com/875192Reviewed-by:
Hongchan Choi <hongchan@chromium.org> Commit-Queue: Raymond Toy <rtoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#532561}
-
catapult-deps-roller@chromium.org authored
https://chromium.googlesource.com/catapult.git/+log/e99634797bd6..831d51715a13 $ git log e99634797..831d51715 --date=short --no-merges --format='%ad %ae %s' 2018-01-29 perezju [Devil] Rewrite surface_stats_collector.GetSurfaceFlingerPid 2018-01-29 perezju [Telemetry] Fix up IsApplicationRunning for Android platform 2018-01-29 erikchen Change assert to instead log a warning. 2018-01-29 perezju [Telemetry] Simplify GetDevtoolsRemotePort for WebView 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: Iaa73a0c657b69535d95b09c3d621b5af3201aebf Reviewed-on: https://chromium-review.googlesource.com/890823 Commit-Queue: <catapult-deps-roller@chromium.org> Reviewed-by: <catapult-deps-roller@chromium.org> Cr-Commit-Position: refs/heads/master@{#532560}
-
Bret Sepulveda authored
Versions of the dialog with long titles, like the "re-enable with new permissions" or the "extension installed externally" dialogs, are affected by this change. Instead of wrapping, their titles would all be on one big line, making the dialog extremely wide. This is fixed. This patch also adds interactive browser tests for "withheld" permissions and for the "re-enable" version of the dialog. Bug: 654124 Change-Id: Iaffdede6a9977952f83a4393425a4df58007d05e Reviewed-on: https://chromium-review.googlesource.com/885104Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Commit-Queue: Bret Sepulveda <bsep@chromium.org> Cr-Commit-Position: refs/heads/master@{#532559}
-
Wez authored
Bug: 750756, 806451 Change-Id: I60ab7ca8a99bd1845492d7486e811f68105116f2 Reviewed-on: https://chromium-review.googlesource.com/890109Reviewed-by:
Scott Graham <scottmg@chromium.org> Commit-Queue: Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#532558}
-
Ahmed Fakhry authored
BUG=709824 TEST=unit_tests --gtest_filter=AboutFlagsHistogramTest.*' Change-Id: If17ed24b23f68e5bb3720d25240209f16a707480 Reviewed-on: https://chromium-review.googlesource.com/887562Reviewed-by:
James Cook <jamescook@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Commit-Queue: Ahmed Fakhry <afakhry@chromium.org> Cr-Commit-Position: refs/heads/master@{#532557}
-
Raphael Kubo da Costa authored
We were previously using an std::set<std::string> to filter out mime type duplicates, optionally adding the "application/octet-stream" mime type to the set before joining all items as a single string to pass to the kdialog invocation. This used to work fine with the KDE4-based kdialog, whose underlying KFileDialog ended up creating a custom file type filter with all entries and suggesting the proper file extension. The KDE Frameworks 5-based kdialog that was released a few months ago uses a simple QFileDialog, and the filter's entries are added in the order they are passed to kdialog. In practice, this means that downloading a PDF file (or any file whose mime type ended up coming after "application/octet-stream" when iterating our std::set) causes kdialog to be invoked like this: kdialog [...] --getsavefilename /path/to/Downloads/foo.pdf \ application/octet-stream application/pdf KDE4 kdialog suggests "foo.pdf" as the name and adds "unknown, PDF document", "unknown" and "PDF document" to the filter list. KF5 kdialog suggests "foo.bin" as the name and adds "unknown" and "PDF document" to the filter list. We now make sure that "application/octet-stream" is the last mime type we pass to kdialog so that any other more specific mime type is chosen as the default and we do not always try to add the ".bin" extension to the files we are saving. Bug: 752375 Change-Id: I56a458042823c52beada9c1819c2ee4b8b8e5e30 Reviewed-on: https://chromium-review.googlesource.com/891160 Commit-Queue: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> Reviewed-by:Elliot Glaysher <erg@chromium.org> Cr-Commit-Position: refs/heads/master@{#532556}
-
Daniel Cheng authored
Going forward, this is the preferred naming for modules containing EnumTraits, StructTraits, and UnionTraits. Change-Id: I4e363a9c74cd3f43d071cd4cdc4cb6c0a72be722 Bug: 806965 Reviewed-on: https://chromium-review.googlesource.com/891673 Commit-Queue: Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Ken Rockot <rockot@chromium.org> Reviewed-by:
Tom Sepez <tsepez@chromium.org> Cr-Commit-Position: refs/heads/master@{#532555}
-
Christian Fremerey authored
* Move base::Feature for enabling video capture service to content_features.h/cc. * Added base::Feature "RunVideoCaptureServiceInBrowserProcess" to allow forcing the service to run in the browser process * Add logic for determining if and where service should run. * In file device_factory_media_to_mojo_adapter.cc, allow devices that report zero supported formats, since this appears to be a valid case on Android. This CL does not yet register the service factory as an embedded service in the Browser process. This needs to be done in a follow-up step as soon as questions regarding EmbeddedInstanceManager have been resolved, see [1]. [1] https://chromium-review.googlesource.com/c/chromium/src/+/817646 Design Doc: https://docs.google.com/document/d/1Kg5S6K8rwIqMVzo4lbipy_rxjxO9zqKdYrnxSvLJZkg/edit?usp=sharing Bug: 792621 Change-Id: I5b3c4a79e2f267238e3b726a736852d6a4205e0d Reviewed-on: https://chromium-review.googlesource.com/759412 Commit-Queue: Christian Fremerey <chfremer@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
-
Samuel Huang authored
Recent refactoring in Zucchini Trunk replaced explicit "separator" (archive content outside matched elements) computation with "gap" handling that occurs close to element handling. This CL removes the now-obsolete explicit separator computation code from Zucchini Chromium, to prepare for merging in ensemble matching code from Trunk. Bug: 729154 Change-Id: I7c917df058e104d8f1d518d37a673edaf0a2918c Reviewed-on: https://chromium-review.googlesource.com/891443Reviewed-by:
Samuel Huang <huangs@chromium.org> Commit-Queue: Samuel Huang <huangs@chromium.org> Cr-Commit-Position: refs/heads/master@{#532553}
-
Zentaro Kavanagh authored
- Makes NTLMv2 the default version. - This implicitly disables NTLMv1. - Leaving the flag available for the first release with the default changed. - Subsequent release will remove the flag but leave a policy. BUG=chromium:22532 Change-Id: Ibb2778806b2a19b70abbc5300d20e06327077fb8 Reviewed-on: https://chromium-review.googlesource.com/885509 Commit-Queue: Zentaro Kavanagh <zentaro@chromium.org> Reviewed-by:
Asanka Herath <asanka@chromium.org> Reviewed-by:
Ryan Sleevi <rsleevi@chromium.org> Cr-Commit-Position: refs/heads/master@{#532552}
-
Benjamin Shaya authored
Bug: b/72556352 Test: cast_audio_backend_unittests, on device Change-Id: I1696bce76de6aa311cc8b25b9ff3f445fb23e9d9 Reviewed-on: https://chromium-review.googlesource.com/889503 Commit-Queue: Benjamin Shaya <bshaya@chromium.org> Reviewed-by:
Kenneth MacKay <kmackay@chromium.org> Cr-Commit-Position: refs/heads/master@{#532551}
-
Raphael Kubo da Costa authored
tools/binary_size/libsupersize/testdata/mock_output_directory/obj/third_party/icu was being wrongly identified by licenses.py as missing a README.chromium. Bug: 39240 Change-Id: I69227968fe716bae4bfb12734fc2098bfaf68d14 Reviewed-on: https://chromium-review.googlesource.com/886342 Commit-Queue: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> Reviewed-by:
-
Chris Harrelson authored
OOPIF renderers can have the local root throttled. Bug: 798486 Change-Id: I56fde149e6ad75ad49c38839a0f619dc84129b6f Reviewed-on: https://chromium-review.googlesource.com/890288 Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Reviewed-by:
-
Chris Harrelson authored
This reverts commit 484efec4. Reason for revert: Makes performance worse on the bots, not better. Unclear why. Original change's description: > [PE] Reduce copies of LayoutRect in PaintLayerClipper. > > Bug: 798378 > Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 > Change-Id: Ic3c0b29430b06e76a3c81e654bc780e4a969592d > Reviewed-on: https://chromium-review.googlesource.com/880403 > Commit-Queue: Chris Harrelson <chrishtr@chromium.org> > Reviewed-by: Stephen Chenney <schenney@chromium.org> > Cr-Commit-Position: refs/heads/master@{#532031} TBR=chrishtr@chromium.org,schenney@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 798378 Change-Id: I8c6ec640efffe8cd7e2adaacd2ecc47d469794bb Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Reviewed-on: https://chromium-review.googlesource.com/891559Reviewed-by:
Stephen Chenney <schenney@chromium.org> Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#532548}
-
rbpotter authored
Displays list of destinations in dialog. Selecting does not yet work. Bug: 773928 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I07cf498a25b248b2f6e11c13e09f139aebf20184 Reviewed-on: https://chromium-review.googlesource.com/875290 Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#532547}
-
Qiang Xu authored
changes: Add a switch to make the feature dev behind the flag. Bug: 805046 Test: unit_tests --gtest_filter=AboutFlagsHistogramTest* Change-Id: I1b63060cf6b08557d94447b4a87f9ab07b192e1c Reviewed-on: https://chromium-review.googlesource.com/890633Reviewed-by:
-
Yunlian Jiang authored
We want to keep minimal symbols when remove_webcore_debug_symbols is set, so that we can get readable backtrace. On ChromeOS arm build, the size of debug file increases from 899MB to 1.244GB. It increases 245 MB. Bug: chromium:792999 Change-Id: Ibc238308754a2727505cfbac3ce24f7a70027529 Reviewed-on: https://chromium-review.googlesource.com/862607Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Ryo Hashimoto <hashimoto@chromium.org> Commit-Queue: Yunlian Jiang <yunlian@chromium.org> Cr-Commit-Position: refs/heads/master@{#532545}
-
erikchen authored
The current flakiness occurs in the form of a timeout waiting for profiling to start for renderers. On Android, there's a warm-up renderer that could start before ProfilingProcessHost gets a chance to start up - as such, it will never be profiled. This CL adds logic to force profiling to start for all renderers, which should fix the flakiness. This CL also fixes a bug in ProfilingClient, which was only keeping the most recent binding. Bug: 804412 Change-Id: I836e55650b30a6360e0bc0f9189aacb7a75ea0c9 Reviewed-on: https://chromium-review.googlesource.com/889999Reviewed-by:
Maria Khomenko <mariakhomenko@chromium.org> Commit-Queue: Erik Chen <erikchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#532544}
-
Daniel Cheng authored
Bug: 608780 Change-Id: I4b699a8322702e117a0e2a5b81b61fd294e781b5 Reviewed-on: https://chromium-review.googlesource.com/889522Reviewed-by:
Łukasz Anforowicz <lukasza@chromium.org> Commit-Queue: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#532543}
-
Nico Weber authored
R=dalecurtis@chromium.org Change-Id: If38dfc4fb4deb50f8e82fe89e4d98fef5fd81863 Reviewed-on: https://chromium-review.googlesource.com/889782Reviewed-by:
-
xdai authored
Bug: 761288 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I0630b778aa8b758c7742af15541e83162f13d431 Reviewed-on: https://chromium-review.googlesource.com/875165Reviewed-by:
Michael Giuffrida <michaelpg@chromium.org> Commit-Queue: Xiaoqian Dai <xdai@chromium.org> Cr-Commit-Position: refs/heads/master@{#532541}
-
bsheedy authored
Ports most of WebVrTransitionTest to have a WebXR equivalent. Does not port testNfcFiresVrdisplayactivate or testTrustedIntentAllowsAutoPresent since there is not currently an implemented equivalent of the functionality they test in WebXR. Bug: 804043 Change-Id: I20985416985ca777a541cf42e9a377c2c29a5456 Reviewed-on: https://chromium-review.googlesource.com/885098 Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Reviewed-by:
Michael Thiessen <mthiesse@chromium.org> Cr-Commit-Position: refs/heads/master@{#532540}
-
Andrii Shyshkalov authored
R=dpranke@chromium.org, jbudorick@chromium.org No-Try: True Bug: 731553 Change-Id: I12cd97bfee4d1cc7bf81f5c990014a27335a1c50 Reviewed-on: https://chromium-review.googlesource.com/891666Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org> Cr-Commit-Position: refs/heads/master@{#532539}
-
Troy Hildebrandt authored
NewApi warnings were suppressed accidentally and an AssertionError constructor that requires API 19 was used. The NewApi warnings are back, so this fix avoids using the AssertionError, and throws the exceptions as they are. This is an accidental leftover from the previous fixes, and is blocking the CL that removes the NewApi error suppression. Bug: 805509,803484 Change-Id: Ib2cc11c3ffdcfc50a4618d98d016ab52e0f1f624 Reviewed-on: https://chromium-review.googlesource.com/891578Reviewed-by:
David Trainor <dtrainor@chromium.org> Commit-Queue: Troy Hildebrandt <thildebr@chromium.org> Cr-Commit-Position: refs/heads/master@{#532538}
-
Kevin Marshall authored
This is a reland of b2b018c5. Original change's description: > Build Fuchsia packages for test and executable targets. > > All targets that use the test() or fuchsia_executable_runner rules > will produce Fuchsia packages, which contain the test executable and > their runtime dependencies. > > The packages are modules which can be deployed in an already-running > system, as opposed to the current scheme which bakes the files into > the system boot image. > > Deployment and support for dynamic libraries will be addressed > in followup CLs. > > This CL also: > * Fixes PathService logic for packaged invocations. > * Adds a new "build_manifest.py" GN helper script. > * Fixes the dependency graph for Fuchsia runner script generation > so that it accurately captures the real dependency ordering. > > > Bug: 796779 > Change-Id: I4e3a38e0075573b328ad98425cc493e28cff1ca4 > Reviewed-on: https://chromium-review.googlesource.com/841749 > Commit-Queue: Kevin Marshall <kmarshall@chromium.org> > Reviewed-by: Wez <wez@chromium.org> > Reviewed-by: Daniel Cheng <dcheng@chromium.org> > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > Reviewed-by: Sergey Ulanov <sergeyu@chromium.org> > Cr-Commit-Position: refs/heads/master@{#531288} Bug: 796779 Change-Id: I8c365a51abb49c2542aec8f66073e7fb7217cf75 Reviewed-on: https://chromium-review.googlesource.com/886982 Commit-Queue: Kevin Marshall <kmarshall@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#532537}
-
Kristian H. Kristensen authored
Upstream has allocated DRM_FORMAT_MOD_INVALID as a special modifier that indicates the absence of a modifier. This is the legacy mode where the kernel gets the tiling/layout information through back channels, typically as a property of the BO. It's a little more concise that passing addfb_flags around as we did before and can be encoded into the NativePixmap handle as well. Bug: b:70546200, b:71416883, chromium:789292, b:69238712, b:68003124 Change-Id: I4340355e56d4117afebb06e1d96d4f8b93900a6e Reviewed-on: https://chromium-review.googlesource.com/885904 Commit-Queue: Kristian H. Kristensen <hoegsberg@chromium.org> Reviewed-by:
Daniele Castagna <dcastagna@chromium.org> Cr-Commit-Position: refs/heads/master@{#532536}
-
Allen Bauer authored
Ensure focusability is enabled along with the correct tool-tip. Bug: 806706 Change-Id: Ic60278a2d57f1c23cf36c8633994eb39fc7a5417 Reviewed-on: https://chromium-review.googlesource.com/890388Reviewed-by:
Bret Sepulveda <bsep@chromium.org> Commit-Queue: Allen Bauer <kylixrd@chromium.org> Cr-Commit-Position: refs/heads/master@{#532535}
-
