- 17 Aug, 2018 40 commits
-
-
angle-chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/3394a73db973..d731ff82e5a8 git log 3394a73db973..d731ff82e5a8 --date=short --no-merges --format='%ad %ae %s' 2018-08-17 fjhenigman@chromium.org Vulkan: support depth offset. 2018-08-17 tobine@google.com Refactoring EGL validation Created with: gclient setdep -r src/third_party/angle@d731ff82e5a8 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 TBR=geofflang@chromium.org Change-Id: I40e756d43a596483d6237843ad1f7968ef144efa Reviewed-on: https://chromium-review.googlesource.com/1180188Reviewed-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@{#584210}
-
Jennifer Apacible authored
TBR=davidben@chromium.org NOTRY=true (disabling tests) Bug: 875404 Change-Id: I68f0c612342043a91d7d4feef3d91f4353232299 Reviewed-on: https://chromium-review.googlesource.com/1180370Reviewed-by:
apacible <apacible@chromium.org> Commit-Queue: apacible <apacible@chromium.org> Cr-Commit-Position: refs/heads/master@{#584209}
-
Meilin Wang authored
Fix the assistant title bar controls icon spacing and size. Test: local compile and manually test. Bug: b:112312676 Change-Id: I095ad7f7ec4814c4247c75c0e5501e656f7acb18 Reviewed-on: https://chromium-review.googlesource.com/1179249 Commit-Queue: Meilin Wang <meilinw@chromium.org> Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Cr-Commit-Position: refs/heads/master@{#584208}
-
Pavel Yatsuk authored
Current server infrastructure doesn't have dedicated staging endpoint. All traffic should be sent to prod endpoint. BUG=811909 R=wylieb@chromium.org Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: I028f9b0f5fcf80dc313c534347800d8bdcae185d Reviewed-on: https://chromium-review.googlesource.com/1174958 Commit-Queue: Pavel Yatsuk <pavely@chromium.org> Reviewed-by:
Sky Malice <skym@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Reviewed-by:
Filip Gorski <fgorski@chromium.org> Cr-Commit-Position: refs/heads/master@{#584207}
-
Sarah Hu authored
Fingerprint.UnlockEnabled should map to whether there's finger enrolled for screen unlock, instead of tracking a feature flag. Remove the recording in chrome and keep the definition for biod to use. Bug: 862295 Change-Id: Ibb706d0ac8ae05240446a3758c5b2e6d5c2e6224 Reviewed-on: https://chromium-review.googlesource.com/1180343Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Xiaoyin Hu <xiaoyinh@chromium.org> Cr-Commit-Position: refs/heads/master@{#584206}
-
Takumi Fujimoto authored
The Cast toolbar icon has been in the same section as extension icons. This CL puts the icon in the trusted area of the toolbar if the ViewsCastDialog flag is enabled. CastToolbarButton, the main icon object, is owned by ToolbarView, just like AvatarToolbarButton. CastToolbarButton observes MediaRouterActionController (to be renamed in a later patch, because "Action" is specific to the old icon) and sets its visibility and pressed state accordingly. When the ViewsCastDialog flag is disabled, the old icon is used. Screencap: https://drive.google.com/open?id=1IMxDzKSiR8AJ89muOy1-_NDLp0RNYAau Bug: 859216 Change-Id: I0ec14e6d20dd58b0356166520c8511e3f9027b83 Reviewed-on: https://chromium-review.googlesource.com/1158794Reviewed-by:
Peter Boström <pbos@chromium.org> Reviewed-by:
mark a. foltz <mfoltz@chromium.org> Reviewed-by:
Bret Sepulveda <bsep@chromium.org> Commit-Queue: Takumi Fujimoto <takumif@chromium.org> Cr-Commit-Position: refs/heads/master@{#584205}
-
pdfium-chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/1f867bb6e2c7..1b2b76d634ba git log 1f867bb6e2c7..1b2b76d634ba --date=short --no-merges --format='%ad %ae %s' 2018-08-17 npm@chromium.org Add FPDFText_GetFontInfo 2018-08-17 thestig@chromium.org Remove CFPF_SkiaBufferFont and CFPF_SkiaFileFont. 2018-08-17 tsepez@chromium.org Rename CJS_Return to CJS_Result. 2018-08-17 hnakashima@chromium.org Optimize rendering of 2D barcodes: create Rect only on black regions. Created with: gclient setdep -r src/third_party/pdfium@1b2b76d634ba 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. BUG=chromium:872907 TBR=dsinclair@chromium.org Change-Id: If97634d9c5aefb8b3eb86eef4073e9aa314514d5 Reviewed-on: https://chromium-review.googlesource.com/1180278Reviewed-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@{#584204}
-
Sadrul Habib Chowdhury authored
This is a reland of 0cdc1458 Original change's description: > metrics: Initialize persistent metric allocator early. > > The PersistentMemoryAllocator in the gpu (and other) process is created > asynchronously. If any uma-histogram is reported before that time, then > those Histograms are not stored in the shared memory. This has some > implications: > . If the process crashes (which is common for the gpu process on > android), then these metrics are lost. > . If the process stays alive, then the metrics are reported > periodically, but because it is buffered, it doesn't match up > correctly with the other metrics that are reported in the shared > memory. > > The allocator is created in response to a message from the browser, > which includes the handle for the shared memory to use for the allocator. > The browser waits until the process has been launched and connected. > So this happens much later, compared to other messages which are sent > from browser over mojo without waiting for the connection to have > been established first. Therefore, change this so that the browser > immediately shares the shared-memory segment with the gpu process. mojo > takes care of waiting for the process-launch etc. > > BUG=865179, 778749 > > Change-Id: Iccd3d4422de3e22ead4bc6510afc5ea207bf6b6e > Reviewed-on: https://chromium-review.googlesource.com/1174709 > Reviewed-by: Brian White <bcwhite@chromium.org> > Reviewed-by: Avi Drissman <avi@chromium.org> > Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org> > Cr-Commit-Position: refs/heads/master@{#583673} TBR=avi,sadrul Bug: 865179, 778749 Change-Id: I205221ed82b073464e1c4d52593ba727ebc211a5 Reviewed-on: https://chromium-review.googlesource.com/1179346Reviewed-by:
Matthew Jones <mdjones@chromium.org> Commit-Queue: Matthew Jones <mdjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#584203}
-
Devlin authored
This reverts commit cb6c4c2d. Reason for revert: Reverted suspected culprit; checking to see if still flaky. Original change's description: > Disable TabManagerTest.ProactiveFastShutdownWithBeforeunloadHandler > > TBR=wjmaclean@chromium.org > NOTRY=true > > Bug: 874915 > Change-Id: Id0fae86ef2e130185d92ad28383c74036dcd96f3 > Reviewed-on: https://chromium-review.googlesource.com/1177881 > Reviewed-by: Xida Chen <xidachen@chromium.org> > Reviewed-by: James MacLean <wjmaclean@chromium.org> > Commit-Queue: Xida Chen <xidachen@chromium.org> > Cr-Commit-Position: refs/heads/master@{#583660} TBR=xidachen@chromium.org,wjmaclean@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 874915 Change-Id: Ie5e977ce5893b35b7510e19c330b668ee6ff52f0 Reviewed-on: https://chromium-review.googlesource.com/1179348Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
James MacLean <wjmaclean@chromium.org> Commit-Queue: Devlin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/master@{#584202}
-
Prashant Malani authored
Add the histogram entries for remaining LE Credential operations (Check, Remove, Reset, ResetTree, Sync, SyncOutcome) and their actions (if applicable). The CL that introduced the code that generates this data is http://crrev.com/c/1093957 Bug: chromium:809749 Test: None Change-Id: I3959e1696fa3df963f16d834c5d2fdbe8966633f Reviewed-on: https://chromium-review.googlesource.com/1178473 Commit-Queue: Prashant Malani <pmalani@chromium.org> Reviewed-by:
Brian White <bcwhite@chromium.org> Cr-Commit-Position: refs/heads/master@{#584201}
-
kereliuk authored
Went through the docs and issues and made some updates Change-Id: I7f628c45fc9a992c7a70f864e027a3525ea9054b Reviewed-on: https://chromium-review.googlesource.com/1178101 Commit-Queue: Jonathon Kereliuk <kereliuk@google.com> Reviewed-by:
John Chen <johnchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#584200}
-
Lindsay Pasricha authored
Uses the same compile config as gpu_tests_release_trybot. Bug: 855301 Change-Id: I70947b3bd21cbbe0519dcb37cb8c6bf844a3e274 Reviewed-on: https://chromium-review.googlesource.com/1179988Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: Lindsay Pasricha <lindsayw@chromium.org> Cr-Commit-Position: refs/heads/master@{#584199}
-
Marcin Wiacek authored
@IntDef/@StringDef annotation are preferred way for declaring set of String/int values. 1. they need less space in APK than enum, see https://developer.android.com/topic/performance/reduce-apk-size#remove-enums 2. they give more control over allowed values than "static final" values Main goal of patch is writing "static final" values, enum and some classes in one common @IntDef/@StringDef form: 1. with @IntDef/@StringDef first, @Retention second and related @interface third 2. with values inside @interface 3. with NUM_ENTRIES declaring number of entries if necessary 4. with comment about numbering from 0 without gaps when necessary 5. with @Retention(RetentionPolicy.SOURCE) 6. without "static final" in the @interface Change-Id: I6aeb3571f6e72dd3599a4a6055189a227312d5c4 Reviewed-on: https://chromium-review.googlesource.com/1154527Reviewed-by:
agrieve <agrieve@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Reviewed-by:
Amirhossein Simjour <asimjour@chromium.org> Commit-Queue: Marcin Wiącek <marcin@mwiacek.com> Cr-Commit-Position: refs/heads/master@{#584198}
-
Maja Kabus authored
New class TrustedScript added as a C++ implementation of JS TrustedScript. Bug: 739170 Change-Id: Ife70f8838aefa6bb4aac45f09639464c19de6e1b Reviewed-on: https://chromium-review.googlesource.com/1168494 Commit-Queue: Maja Kabus <kabusm@google.com> Reviewed-by:
Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#584197}
-
nacl-chromium-autoroll authored
https://chromium.googlesource.com/native_client/src/native_client.git/+log/1c78a7ba9366..9a87d6b9de35 git log 1c78a7ba9366..9a87d6b9de35 --date=short --no-merges --format='%ad %ae %s' 2018-08-17 dschuff@chromium.org Don't run the performance tests in the emulator Created with: gclient setdep -r src/native_client@9a87d6b9de35 The AutoRoll server is located here: https://nacl-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:868204 TBR=mseaborn@chromium.org Change-Id: I26c25267ac7a2f43446d968c2a9cee6f4fe9c4df Reviewed-on: https://chromium-review.googlesource.com/1180187Reviewed-by:
nacl-chromium-autoroll <nacl-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: nacl-chromium-autoroll <nacl-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#584196}
-
Christopher Grant authored
This allows future UI library module to have one less needless dependency. There's no reason the UI needs to look up the icon for a given omnibox suggestion. BUG= R=acondor 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: I6fd8152ed64dd2201a4d1ad1fef139ce309965b0 Reviewed-on: https://chromium-review.googlesource.com/1180162 Commit-Queue: Christopher Grant <cjgrant@chromium.org> Reviewed-by:
Aldo Culquicondor <acondor@chromium.org> Cr-Commit-Position: refs/heads/master@{#584195}
-
Robbie McElrath authored
GoogleURLTracker needs to be migrated from NetworkChangeNotifier to NetworkConnectionTracker to unblock enabling the network service. NetworkConnectionTracker currently needs a network::mojom::NetworkService* in order to to be constructed, but GoogleURLTracker is used in ios, which doesn't have a NetworkService instance to give it. NetworkConnectionTracker only actually uses the NetworkChangeManager interface, so this change makes it depend only on that, not on the entire NetworkService. Bug: 868018 Cq-Include-Trybots: luci.chromium.try:linux_mojo Change-Id: Ia2d422686eaf2473c25698f6aa3e6bd66dd04ad4 Reviewed-on: https://chromium-review.googlesource.com/1177186 Commit-Queue: Robbie McElrath <rmcelrath@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#584194}
-
Moe Ahmadi authored
Splits Autofill settings page into two separate pages, one for addresses and the other for credit cards. TBR=rohitrao@ Bug: 860526,875313 Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: I1b579976f44b413d24d71e04bfb6ef8642e5c78f Reviewed-on: https://chromium-review.googlesource.com/1180266Reviewed-by:
Moe Ahmadi <mahmadi@chromium.org> Commit-Queue: Moe Ahmadi <mahmadi@chromium.org> Cr-Commit-Position: refs/heads/master@{#584193}
-
Steven Valdez authored
https://boringssl.googlesource.com/boringssl/+log/6b0d82229b2c4ce85b1c3f6d55bda661e07bead2..01e8e625ad83cc9a07288bd4dc285bd8b0ccd550 BUG=none Change-Id: Ia06d532d0a15b3b898396594e1f118818b408437 Reviewed-on: https://chromium-review.googlesource.com/1177906Reviewed-by:
David Benjamin <davidben@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Commit-Queue: Steven Valdez <svaldez@chromium.org> Cr-Commit-Position: refs/heads/master@{#584192}
-
Jennifer Apacible authored
TBR=pkasting@chromium.org NOTRY=true (disabling tests) Bug: 875444 Change-Id: I25183c656dab7f8ef061d2261dbfe517369f68ba Reviewed-on: https://chromium-review.googlesource.com/1179257Reviewed-by:
apacible <apacible@chromium.org> Commit-Queue: apacible <apacible@chromium.org> Cr-Commit-Position: refs/heads/master@{#584191}
-
Daniel Erat authored
Update chromeos::CrosDBusService::Start to call ServiceProviderInterface::Start methods (which export methods) before calling dbus::Bus::RequestOwnership. Otherwise, there's a brief window of time where other D-Bus clients may attempt to call methods before they're available. Bug: 874978 Change-Id: I69bc36e465e8086921b67122514f2607399ea33d Reviewed-on: https://chromium-review.googlesource.com/1178757Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Commit-Queue: Dan Erat <derat@chromium.org> Cr-Commit-Position: refs/heads/master@{#584190}
-
Sam Maier authored
execute() is a confusing function, with a hidden implicit meaning that changed in API 11. It would be better if everyone had to use the more explicit executeOnExecutor() so their preference (serial or thread pool) is called out. Bug: 869907 Change-Id: I79be6d2b3114cb0520df1104ec5849f7c070c99e Reviewed-on: https://chromium-review.googlesource.com/1172446Reviewed-by:
agrieve <agrieve@chromium.org> Commit-Queue: Sam Maier <smaier@chromium.org> Cr-Commit-Position: refs/heads/master@{#584189}
-
webrtc-chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/adc48799090c..c8993d8b01c9 git log adc48799090c..c8993d8b01c9 --date=short --no-merges --format='%ad %ae %s' 2018-08-17 buildbot@webrtc.org Roll chromium_revision 409b9c00..77bf1926 (583992:584099) 2018-08-17 nisse@webrtc.org Delete webrtc::PacketTime and backwards compatibility. 2018-08-17 saza@webrtc.org Toggle AECs via AudioProcessing::Config 2018-08-17 titovartem@webrtc.org Switch webrtc users from deprecated ctors. 2018-08-17 sprang@webrtc.org Don't drop keyframes even if TemporalLayers says so. Created with: gclient setdep -r src/third_party/webrtc@c8993d8b01c9 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: Ided700bf4eb02c9e1f3cfb9cc5e9eaff4f7eb8b0 Reviewed-on: https://chromium-review.googlesource.com/1180246Reviewed-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@{#584188}
-
Eric Orth authored
Slight behavior change to never return any address results when the flag is set (to prevent misuse). Affects even the old API usage, but should be safe since a quick check showed that all current usage of the flag never reads the resulting addresses. Bug: 821021 Cq-Include-Trybots: luci.chromium.try:linux_mojo Change-Id: I2579521d181022a8b0c425f959bcc0808f7ed7fa Reviewed-on: https://chromium-review.googlesource.com/1177913 Commit-Queue: Eric Orth <ericorth@chromium.org> Reviewed-by:
Tom Sepez <tsepez@chromium.org> Reviewed-by:
Maks Orlovich <morlovich@chromium.org> Cr-Commit-Position: refs/heads/master@{#584187}
-
Xiangjun Zhang authored
This CL setup a sandboxed utility service for mirroring. The service encodes the captured audio/video streams and sends them to the remote Cast receiver. The sandbox type is set to "renderer" since the service does media encoding and cast control messages parsing, which has similar requirements as a renderer in term of sandbox policy. Bug: 734672 Change-Id: Ieeb1e373241266c15535f6d4d8fa54337ca59941 Reviewed-on: https://chromium-review.googlesource.com/1162932Reviewed-by:
Nasko Oskov <nasko@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Yuri Wiitala <miu@chromium.org> Commit-Queue: Xiangjun Zhang <xjz@chromium.org> Cr-Commit-Position: refs/heads/master@{#584186}
-
Jacob Dufault authored
Change-Id: I923d4987dcfaa7788451f28005998417521589ce Reviewed-on: https://chromium-review.googlesource.com/1179245Reviewed-by:
Xiaoyin Hu <xiaoyinh@chromium.org> Commit-Queue: Jacob Dufault <jdufault@chromium.org> Cr-Commit-Position: refs/heads/master@{#584185}
-
Mitsuru Oshima authored
We now uses dsf for display zooming. Notable changes: * removed ui_scale_, effective_ui_scale parameters. * ZoomInternalDisplay/ResetInternalDisplayZoom is now used only for UnifiedDesktop (we probably want to change this crbug.com/873828) * ModeList for internal display now contains just one mode. I simplied the code for this cases. I also left methods in ScreenManagerOzoneInternal because it's deprecated. Bug: 823922 Test: Removed tests that are no longer necesary. Adjusted tests when they still make sense. Change-Id: Ifca7d45bba15346bb1d0ae78faa150a57e1cb6e6 Reviewed-on: https://chromium-review.googlesource.com/1173726Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
Michael Wasserman <msw@chromium.org> Reviewed-by:
Greg Kerr <kerrnel@chromium.org> Reviewed-by:
Malay Keshav <malaykeshav@chromium.org> Commit-Queue: Mitsuru Oshima <oshima@chromium.org> Cr-Commit-Position: refs/heads/master@{#584184}
-
Robert Sesek authored
This target was removed in 1a726e03 and the data are now pulled via CIPD. Tbr: jialiu@chromium.org Bug: 817663 Change-Id: I1fc102f8417f2876bed82699dd8ef2092a070d39 Reviewed-on: https://chromium-review.googlesource.com/1180283 Commit-Queue: Robert Sesek <rsesek@chromium.org> Reviewed-by:
Abhishek Arya <inferno@chromium.org> Cr-Commit-Position: refs/heads/master@{#584183}
-
Nate Fischer authored
No change to logic. This removes some include statements for unneeded headers under //android_webview/. I identified these errors by running 'cppclean --include-path="$PWD"', and manually sorting out false positives. Test: ninja -C out/Default system_webview_apk (it still compiles) Change-Id: I724be2e179bb5da6ae7aa1eb9ec8840ed6a7c745 Reviewed-on: https://chromium-review.googlesource.com/1180259 Commit-Queue: Nate Fischer <ntfschr@chromium.org> Reviewed-by:
Changwan Ryu <changwan@chromium.org> Cr-Commit-Position: refs/heads/master@{#584182}
-
Stephen McGruer authored
This CL adds some checks to help investigate crbug.com/826627. They are highly speculative, as currently the bug seems to be in a "this can't happen" state; we seem to be getting a null start_ interpolable_value in TransitionInterpolation even though the existing CHECK in TransitionKeyframe::SetValue never fires. My only currently theory is that the stacktrace file view is misleading, so this CL moves a few things around and adds some CHECKs to try and confirm/refute that. Bug: 826627 Change-Id: I9058e0387f79c9a0ba0bd04cdc54ec128a386782 Reviewed-on: https://chromium-review.googlesource.com/1178263Reviewed-by:
Majid Valipour <majidvp@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#584181}
-
Becca Hughes authored
This adds an AudioFocusObserver content API that can be used to listen to audio focus events on platforms where AudioFocusManager is being used. This also refactors AudioFocusType out of AudioFocusManager as we need it for the observer. BUG=870418 Change-Id: I34dcd664f1bfd5c5d63c0cb8d3a7528534bd2c65 Reviewed-on: https://chromium-review.googlesource.com/1161095 Commit-Queue: Becca Hughes <beccahughes@chromium.org> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Cr-Commit-Position: refs/heads/master@{#584180}
-
Toni Barzic authored
This is a reland of d6bbb56c Inheriting from the original cl (as the files for which these lgtms were given have not changed) TBR=isherman@chromium.org, alemate@chromium.org, gab@chromium.org Original change's description: > Remove pre-installed demo mode resources on low disk space > > Introduces a class that will handle removing pre-installed demo mode > resources when needed. > First incarnation observes low disk space signal from cryptohome > service, and removes pre-installed resources when low space is detected > (provided that the device is not in demo mode). > When demo mode resources get removed from disk, this is recorded in > local state, to avoid future attempts to remove these resources. > > More logic for requesting demo mode resources removal to come. > > BUG=827368 > > Change-Id: I721d1995fa818fc2fc1d056e33ba513380bf441e > Reviewed-on: https://chromium-review.googlesource.com/1173670 > Commit-Queue: Toni Baržić <tbarzic@chromium.org> > Reviewed-by: Alexander Alekseev <alemate@chromium.org> > Reviewed-by: Aga Wronska <agawronska@chromium.org> > Reviewed-by: Gabriel Charette <gab@chromium.org> > Reviewed-by: Ilya Sherman <isherman@chromium.org> > Reviewed-by: Michael Giuffrida <michaelpg@chromium.org> > Cr-Commit-Position: refs/heads/master@{#583976} Bug: 827368 Change-Id: Idd8f42f1f85d8ed0eccd17a342750a4a1150e679 Reviewed-on: https://chromium-review.googlesource.com/1180041 Commit-Queue: Toni Baržić <tbarzic@chromium.org> Reviewed-by:
Michael Giuffrida <michaelpg@chromium.org> Cr-Commit-Position: refs/heads/master@{#584179}
-
Jennifer Apacible authored
These are being disabled on all bots now as they fail on more bots than just Mash. TBR=noel@chromium.org NOTRY=true (disabling test) Bug: 874954 Change-Id: I3b0f4076e7aa4f43abd52040e0120f0bcc8b8ca1 Reviewed-on: https://chromium-review.googlesource.com/1180277 Commit-Queue: apacible <apacible@chromium.org> Reviewed-by:
apacible <apacible@chromium.org> Cr-Commit-Position: refs/heads/master@{#584178}
-
Justin Cohen authored
CIPD packages: infra_internal/ios/xcode/mac 10l232m infra_internal/ios/xcode/ios 10l232m Also fixes the LUCI buildbucket caches for Xcode 10. Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: I30453ed7b40c86547ed34ff0bc9fd6d53a2a5127 Reviewed-on: https://chromium-review.googlesource.com/1177916Reviewed-by:
Sergey Berezin <sergeyberezin@chromium.org> Reviewed-by:
John Budorick <jbudorick@chromium.org> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Commit-Queue: Justin Cohen <justincohen@chromium.org> Cr-Commit-Position: refs/heads/master@{#584177}
-
gogerald authored
Rename protocols as well Bug: 806868 Change-Id: Ib24e4d4f8821451a9ee56d27efd1c142a4f2d60b Reviewed-on: https://chromium-review.googlesource.com/1179966Reviewed-by:
Rouslan Solomakhin <rouslan@chromium.org> Commit-Queue: Ganggui Tang <gogerald@chromium.org> Cr-Commit-Position: refs/heads/master@{#584176}
-
sczs authored
ClearBrowsingDataManager causes a cell reload on CBDTableVC. A crash was happening since this reload was occuring before the TableView was properly loaded, this CL prevents those updates. Once the TableView load it will use the latest model, so there's no need for that reload. Bug: 873929 Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: I9f50fbd039d3572895d5424a7ad1855e414ffb62 Reviewed-on: https://chromium-review.googlesource.com/1175106 Commit-Queue: Sergio Collazos <sczs@chromium.org> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Cr-Commit-Position: refs/heads/master@{#584175}
-
Fredrik Söderquist authored
If |values_| does not contain any entries, then CheckIndexBound will fail, so the 'values_.IsEmpty()' condition can never be true here. Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I3c96b6b198a8d9f345a08a436101d803384d11e2 Reviewed-on: https://chromium-review.googlesource.com/1179834Reviewed-by:
Stephen Chenney <schenney@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#584174}
-
pdfium-chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/21068062a038..1f867bb6e2c7 git log 21068062a038..1f867bb6e2c7 --date=short --no-merges --format='%ad %ae %s' 2018-08-17 thestig@chromium.org Remove default arguments from CFPF_SkiaFontMgr. 2018-08-17 tsepez@chromium.org Introduce safer CJS_Return::Success() and Failure(). Created with: gclient setdep -r src/third_party/pdfium@1f867bb6e2c7 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: Iff8f931de6cad4be2aae3bfc30669525ad2a39e5 Reviewed-on: https://chromium-review.googlesource.com/1180009Reviewed-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@{#584173}
-
Alex Deymo authored
This new metric computes the image file size relative to the image area, also called "compression density" in the compression world. This value is the number of compressed bits per pixel, and it is only reported for large enough images (at least 100px per side), to avoid degenerated cases where the image is too small giving a meaningless value. Image compression formats and encoders for these formats use different techniques to compress an image, discarding some of the original data (for lossy compression). Depending on the range of the desired quality (as measured in bits per pixel) some techniques are more efficient than others. For example, at very low qualities (such as 0.2 bits per pixel) typical 8x8 DCT strategies like in JPEG are not the best since the 8x8 independent blocks are too small to allow sharing information (only 12.8 bits per block). Test: Added unittest. Checked chrome://histograms after browsing some pages. Bug: None Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: Ia4454f66f1b7bde6a1d1b2cfb533f7539f425780 Reviewed-on: https://chromium-review.googlesource.com/1177750Reviewed-by:
Philip Rogers <pdr@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Commit-Queue: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#584172}
-
Jennifer Apacible authored
Relanding to fix compiler error. TBR=tedchoc@chromium.org NOTRY=true (disabling a test) Bug: 875372 Change-Id: Idc4c7863dd6e8e1d97ec974c2b8dff3fd09d91f1 Reviewed-on: https://chromium-review.googlesource.com/1180268 Commit-Queue: apacible <apacible@chromium.org> Reviewed-by:
apacible <apacible@chromium.org> Cr-Commit-Position: refs/heads/master@{#584171}
-