- 26 Sep, 2018 14 commits
-
-
Sidney San Martín authored
Bug: 865901 Change-Id: I02010ee8fec71011353f1b0be23e54055af0adf4 Reviewed-on: https://chromium-review.googlesource.com/1236675 Commit-Queue: Sidney San Martín <sdy@chromium.org> Reviewed-by:
ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#594160}
-
Maggie Chen authored
1. If HW overlay scaling is supported, set swap chain size to the minimum of the decoded video buffer size and the onscreen video size. 2. If HW overlay scaling is not supported, set swap chain size to onscreen video size. This CL removes overlay down scaling, and therefore fixes no hardware overlays due to down scaling not working on Intel display HW. BUG=868561 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: I251ddb4f5e24807dd7267eca38180cae241fb6f6 Reviewed-on: https://chromium-review.googlesource.com/1225295 Commit-Queue: Maggie Chen <magchen@chromium.org> Reviewed-by:
Sunny Sachanandani <sunnyps@chromium.org> Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Cr-Commit-Position: refs/heads/master@{#594159}
-
Siddhartha S authored
This reverts commit 3e6c0cd8. Reason for revert: Causes crashes on Mac while accessing TLS. Original change's description: > memlog: Add task contexts from allocation context to native mode > > The task context is useful to debug mojo memory leaks since IPC messages > are tagged with contexts > > BUG=874530 > > Change-Id: Id59d016f963f41fdeda6af69b3c470f0101dbfe7 > Reviewed-on: https://chromium-review.googlesource.com/1232683 > Reviewed-by: Erik Chen <erikchen@chromium.org> > Commit-Queue: Siddhartha S <ssid@chromium.org> > Cr-Commit-Position: refs/heads/master@{#593458} TBR=erikchen@chromium.org,ssid@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 874530, 888899 Change-Id: I70e2dc4a91f8512dc98a68d5dd0736f5e511da54 Reviewed-on: https://chromium-review.googlesource.com/1244829Reviewed-by:
Siddhartha S <ssid@chromium.org> Commit-Queue: Siddhartha S <ssid@chromium.org> Cr-Commit-Position: refs/heads/master@{#594158}
-
Jia authored
In order to check if an experiment is enabled from //chromeos, this CL also moves the feature flag from //chrome/common/chrome_features to //chromeos/chromeos_features. Bug: 888392 Change-Id: I05c6f7f096c8f1ed98e867ac147da3607c043776 Reviewed-on: https://chromium-review.googlesource.com/1242253Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Dan Erat <derat@chromium.org> Commit-Queue: Jia Meng <jiameng@chromium.org> Cr-Commit-Position: refs/heads/master@{#594157}
-
siyua authored
Adding metrics logging according to go/ib-paradise Metrics section Bug: 852904 Change-Id: Ibcdd00998baf0e216b4acae8567e7bce4c5e42fd Reviewed-on: https://chromium-review.googlesource.com/1229079 Commit-Queue: Siyu An <siyua@chromium.org> Reviewed-by:
Evan Stade <estade@chromium.org> Reviewed-by:
Jared Saul <jsaul@google.com> Reviewed-by:
Robert Kaplow (sloooow) <rkaplow@chromium.org> Cr-Commit-Position: refs/heads/master@{#594156}
-
Scott Graham authored
I was confused by some weird behaviour (see linked bug) when I forgot to reboot my device after syncing a new SDK. To detect this, stash SDK_ROOT/.hash as /data/.hash after successfully netbooting, and if that doesn't match on a subsequent run then reboot the target before continuing. This is not quite correct, in that if you sync a new SDK and then run (without building) it will be looking at the synced SDK's hash rather than whatever the binary you're running is built against. But I don't think we have a way to figure out what SDK a binary was built against, so this seems low-cost/more-correct than what we had before. Bug: 889215 Change-Id: I578e9acf33beba17769acebe8f46f7216f93b596 Reviewed-on: https://chromium-review.googlesource.com/1244825Reviewed-by:
Kevin Marshall <kmarshall@chromium.org> Commit-Queue: Scott Graham <scottmg@chromium.org> Cr-Commit-Position: refs/heads/master@{#594155}
-
Gyuyoung Kim authored
kNetwork0QuietWindowTimeout and kNetwork2QuietWindowTimeout constants have not used anywhere since "FMPDetector: Use network quiet signal from IdlenessDetector" commit. This CL removes them and all uses in FirstMeaningfulPaintDetector. Bug: 659021,850403 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I48c3349d208818ceb8d3cde18fdd7177e310b788 Reviewed-on: https://chromium-review.googlesource.com/1237896Reviewed-by:
Kunihiko Sakamoto <ksakamoto@chromium.org> Reviewed-by:
Timothy Dresser <tdresser@chromium.org> Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Gyuyoung Kim <gyuyoung.kim@lge.com> Cr-Commit-Position: refs/heads/master@{#594154}
-
Kurt Horimoto authored
This CL updates BVC's new tab animation to use the visible URL when it is expected to be loaded by the WebStateListWebUsageEnabler. Bug: 880262 Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs Change-Id: I5d948051d39a016f25987fca8840c40c7c8ae99b Reviewed-on: https://chromium-review.googlesource.com/1241555Reviewed-by:
Eugene But <eugenebut@chromium.org> Reviewed-by:
Justin Cohen <justincohen@chromium.org> Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#594153}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/89ae8c86b8c8..d57b80dd25bd Created with: gclient setdep -r src-internal@d57b80dd25bd The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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=mmoss@chromium.org Change-Id: I8990148aa9a12c663aa1f39dd33de78be10fa26b Reviewed-on: https://chromium-review.googlesource.com/1244722Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#594152}
-
wutao authored
Currently spoken of shortcut viewer shortcut item is verbose and has not seperation between description and shortcut. This patch fixes the two a11y spoken issues by: 1. Remove category text in each item. 2. Add a punctuation between description and shortcut. Bug: 876398, 876400 Test: manual. Change-Id: I42b1558c0e165ad7a25227475309c205b6fdabaa Reviewed-on: https://chromium-review.googlesource.com/1244158Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Commit-Queue: Tao Wu <wutao@chromium.org> Cr-Commit-Position: refs/heads/master@{#594151}
-
Mei Liang authored
During tab restoration, a tab is considered as a duplicated tab when it has an identical url with another restored tab. This CL records a set of histograms about duplicated tabs on cold start: 1. Tabs.Tasks.DuplicatedTab.Count 2. Tabs.Tasks.DuplicatedTab.DuplicatedTabRatio This CL modifies TaskUma to collect and record the metric. These histograms are only captured in Tabbed Activity. Bug: 882071 Change-Id: Ie09d7977e464d93baff148df065e669ac69b0df6 Reviewed-on: https://chromium-review.googlesource.com/1229077 Commit-Queue: Mei Liang <meiliang@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Cr-Commit-Position: refs/heads/master@{#594150}
-
Jun Mukai authored
BookmarkBarViewTest12.CloseWithModalDialog is in timeout. That's because DialogWaiter is observing for a wrong aura::Env instance. BUG=883523 TEST=interactive_ui_tests --enable-features=SingleProcessMash Change-Id: Ia2b057763e87458a564dbffa25c6cc92889992a6 Reviewed-on: https://chromium-review.googlesource.com/1244125Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Jun Mukai <mukai@chromium.org> Cr-Commit-Position: refs/heads/master@{#594149}
-
Shubhie Panicker authored
Bug: 822954 Change-Id: Ife5a6460c0215fa188e3734fa781ecfb994e94b9 Reviewed-on: https://chromium-review.googlesource.com/1241994 Commit-Queue: Shubhie Panicker <panicker@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Alexander Timin <altimin@chromium.org> Cr-Commit-Position: refs/heads/master@{#594148}
-
Jun Mukai authored
BUG=888779 TEST=interactive_ui_tests --enable-features=SingleProcessMash Change-Id: If0653a7dae1e7c156f122680fd6be71b001dd9f3 Reviewed-on: https://chromium-review.googlesource.com/1244300Reviewed-by:
Jacob Dufault <jdufault@chromium.org> Commit-Queue: Jun Mukai <mukai@chromium.org> Cr-Commit-Position: refs/heads/master@{#594147}
-
- 25 Sep, 2018 26 commits
-
-
Ben Pastene authored
This is needed for both sanity test and tast tests, so this applies the env var changes for every type of test. Normal GTest tests don't need it, but they'll get it anyway. Shouldn't be harmful. Change-Id: Ida2bd856fc75a089f899c4e4cfdc56de90d5fa48 Reviewed-on: https://chromium-review.googlesource.com/1244876Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#594146}
-
Devlin Cronin authored
Use the constants from manifest_constants.* in extension_builder.cc instead of using string literals. Bug: None Change-Id: I111beee9274c7ac347ffb3df0657bb1d1b6327fb Reviewed-on: https://chromium-review.googlesource.com/1242274 Commit-Queue: Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Istiaque Ahmed <lazyboy@chromium.org> Cr-Commit-Position: refs/heads/master@{#594145}
-
Christopher Cameron authored
DragDropClientMac is one of the few remaining structures that Cocoa and Views code depends on. Break this dependency cycle, so that we can move all Cocoa code to ui/views_brige_mac. * Separate out the interface that Cocoa depends on and move it to views_bridge_mac::DragDropClient. * Make views::DragDropClientMac be a member of the browser side structure views::BridgedNativeWidgetHostImpl Note that this does not solve the problem that drag drop behavior is not implemented over mojo. When using RemoteMacViews, drag drop functionality will still be absent. Bug: 859152 Change-Id: I3d5b8a3b8ae9403effd17436e727ba4298bcae61 Reviewed-on: https://chromium-review.googlesource.com/1244720Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#594144}
-
Hongchan Choi authored
Currently the destructor of BaseAudioContext has 3 DCHECKs touching GC-managed objects. This is a violation of GC system. Move them from the destructor to Uinitialize() method, which gets called before the destruction. with --repeat-each=50 option. Bug: 856317 Test: webaudio/Analyser/realtimeanalyser-float-data.html passes Change-Id: Ifa898d95feda3fcc1ae82e3e99a27e45edca38ab Reviewed-on: https://chromium-review.googlesource.com/1237247 Commit-Queue: Hongchan Choi <hongchan@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Raymond Toy <rtoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#594143}
-
Tobias Sargeant authored
Bug: 865062 Change-Id: I8efb1817b1b2bf390189ed117c8773b6a0329ded Reviewed-on: https://chromium-review.googlesource.com/1244798Reviewed-by:
Nate Fischer <ntfschr@chromium.org> Commit-Queue: Tobias Sargeant <tobiasjs@chromium.org> Cr-Commit-Position: refs/heads/master@{#594142}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/9412c8ec36d1..072d829e2cd1 git log 9412c8ec36d1..072d829e2cd1 --date=short --no-merges --format='%ad %ae %s' 2018-09-25 thestig@chromium.org Optimize MaybeEmbedPositionAdjustmentPatterns(). Created with: gclient setdep -r src/third_party/pdfium@072d829e2cd1 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. TBR=dsinclair@chromium.org Change-Id: I77630b895f881d4edeac45c9d9c614fc1e50f782 Reviewed-on: https://chromium-review.googlesource.com/1244537Reviewed-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@{#594141}
-
Etienne Pierre-doray authored
This CL uses ScopedBlockingCall to mark blocking calls in /device/usb. This CL was created by replacing calls to AssertBlockingAllowed() with instantiations of ScopedBlockingCall(MAY_BLOCK). I kindly ask the reviewer to make sure of the following: - ScopedBlockingCall is instantiated in a scope with minimal CPU usage. If this is not the case, ScopedBlockingCall should be instantiated closer to the blocking call. See scoped_blocking_call.h for more info. Please let me know when/where the blocking call happens if this needs to be changed. - Parameter |blocking_type| matches expectation (MAY_BLOCK/WILL_BLOCK). See BlockingType for more info. While I assumed MAY_BLOCK by default, that might not be the best fit if we know that this callsite is guaranteed to block. - The ScopedBlockingCall's scope covers the entirety of the blocking operation previously asserted against by the AssertBlockingAllowed(). This CL was uploaded by git cl split. R=reillyg@chromium.org Bug: 874080 Change-Id: I0ee2ff9b2a81c101f943716b4965d4f21f231e41 Reviewed-on: https://chromium-review.googlesource.com/1191322Reviewed-by:Reilly Grant <reillyg@chromium.org> Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org> Cr-Commit-Position: refs/heads/master@{#594140}
-
Lei Zhang authored
Make them available to other unit tests. Change-Id: If1166a9611b4b5455440ceb75c449f61e4cbb8ce Reviewed-on: https://chromium-review.googlesource.com/1244112 Commit-Queue: Lei Zhang <thestig@chromium.org> Reviewed-by:
Henrique Nakashima <hnakashima@chromium.org> Cr-Commit-Position: refs/heads/master@{#594139}
-
Becky Zhou authored
Bug: 886975 Change-Id: Ic4717d4fc2fbac73137f65154b3055332f9c23ed Reviewed-on: https://chromium-review.googlesource.com/1244612Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Becky Zhou <huayinz@chromium.org> Cr-Commit-Position: refs/heads/master@{#594138}
-
Oriol Brufau authored
Currently only 'position: absolute' uses the padding area of the containing block in 'top' and 'bottom' properties, 'position: fixed' uses the content area instead. The change only affects the value returned by getComputedStyle, the used value was already correct. BUG=883585 TEST=external/wpt/css/cssom/getComputedStyle-insets-fixed.html The test still has some failures due to http://crbug.com/883582, http://crbug.com/883574 and http://crbug.com/888532. Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Change-Id: I91a07472026f50cb60e0225a4e8edd515c04ec6a Reviewed-on: https://chromium-review.googlesource.com/1240124 Commit-Queue: Oriol Brufau <obrufau@igalia.com> Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#594137}
-
David Tseng authored
Profiles are unneeded since the changes to use AutomationEventRouter. Previously, we went through the extension system's routing layer, which required a context. Bug: 888152 Change-Id: I57260ad0507267fee94d6764464b18a141d3b09e Reviewed-on: https://chromium-review.googlesource.com/1239265 Commit-Queue: David Tseng <dtseng@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#594136}
-
Avi Drissman authored
BUG=880210 Change-Id: I44e80bc0866fef5370936db3f2cb4d3eacf620f2 Reviewed-on: https://chromium-review.googlesource.com/1241094Reviewed-by:
Leonard Grey <lgrey@chromium.org> Reviewed-by:
Mike Wittman <wittman@chromium.org> Commit-Queue: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#594135}
-
Christopher Cameron authored
Use the RenderWidgetResizeHelper's task runner to handle the mojo messages to and from the BridgedNativeWidget and BridgedNativeWidgetHost. Bug: 859152 Change-Id: I3d9fab6cd81edafd74e45d06c658d1bd15e1fde4 Reviewed-on: https://chromium-review.googlesource.com/1244103 Commit-Queue: Sidney San Martín <sdy@chromium.org> Reviewed-by:
Sidney San Martín <sdy@chromium.org> Cr-Commit-Position: refs/heads/master@{#594134}
-
François Beaufort authored
With User Activation V2, the click activation is carried on to the following tests since the state is no longer stack-scoped. By re-ordering tests, this CL makes sure test doesn't fail when User Activation V2 is enabled. Bug: 860718 Change-Id: I54ebc6ca2d808323e4b87997b9687c56e2c8606d Reviewed-on: https://chromium-review.googlesource.com/1244239 Commit-Queue: Mounir Lamouri <mlamouri@chromium.org> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Cr-Commit-Position: refs/heads/master@{#594133}
-
Marijn Kruisselbrink authored
Bug: 878581 Change-Id: I65fc0029da2e3951495a6cd96704085e5c1b942c Reviewed-on: https://chromium-review.googlesource.com/1227366Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Cr-Commit-Position: refs/heads/master@{#594132}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/29788f1ac1da..89ae8c86b8c8 Created with: gclient setdep -r src-internal@89ae8c86b8c8 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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. BUG=chromium:868213 TBR=mmoss@chromium.org Change-Id: Ib90caca078f76ca4972dbefc844348541a2ae32b Reviewed-on: https://chromium-review.googlesource.com/1244717Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#594131}
-
David Tseng authored
In Android, accessibility services can respect the |isImportantForAccessibility| property. Chrome-side, this best matches the concept of an ignored role. In particular, this means, during linear navigation, a service should ignored this node while looking for the next directed node to visit. Note that this should have no impact on descendants, unless, of course, they also have isImportantForAccessibility set to false. Bug: 889074 Change-Id: I33ace3fc1e88450a9d2ce3798bd92feed2e08a19 Reviewed-on: https://chromium-review.googlesource.com/1243486Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#594130}
-
Christopher Cameron authored
Move some of the static methods in DisplayLinkMac to be anonymous namespace methods in the cc file, and add comments clarifying their usage. Remove the DCHECK ensuring that the initially-captured main thread task runner be equal to the current main thread task runner, and add a comment indicating that this may not always be the case. Bug: 885329 Change-Id: Idfdeb3ba1d20840161f26669e19bdee42aa155c5 Reviewed-on: https://chromium-review.googlesource.com/1234229Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#594129}
-
Stephen Martinis authored
Swarming mixins had not been used by gpu tests. This CL makes them work, and adds a test case. Bug: 871872 Change-Id: I914e16ab57ad3b514cf263f18e0fff195a0f37d8 Reviewed-on: https://chromium-review.googlesource.com/1244172Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Stephen Martinis <martiniss@chromium.org> Cr-Commit-Position: refs/heads/master@{#594128}
-
Xiaohan Wang authored
This is a preparation step before we add AV1 support. - Remove container from codec enum names. - EME_CODEC_WEBM_VP9 -> EME_CODEC_LEGACY_VP9 to differentiate from EME_CODEC_VP9, which is for the new multi-part VP9. - DV -> DOLBY_VISION for better readability. Bug: 884898 Test: No functionality change. Change-Id: I23117298ca604c0266487c637cacebdfd6884942 Reviewed-on: https://chromium-review.googlesource.com/1240502Reviewed-by:
Luke Halliwell <halliwell@chromium.org> Reviewed-by:
John Rummell <jrummell@chromium.org> Commit-Queue: Xiaohan Wang <xhwang@chromium.org> Cr-Commit-Position: refs/heads/master@{#594127}
-
Alexey Kozyatinskiy authored
New acorn support couple nice ES features, e.g., - for await (...) loop, - spread operator. R=lushnikov@chromium.org Bug: chromium:863656 Change-Id: I057ebf01fcc220ee1e98707343df457358f248f6 Reviewed-on: https://chromium-review.googlesource.com/1244600 Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Reviewed-by:
Andrey Lushnikov <lushnikov@chromium.org> Cr-Commit-Position: refs/heads/master@{#594126}
-
Jonathan Freed authored
This callback allows Java to fetch a favicon for a site from the native code. Change-Id: Id4a8d86f68ade3b48e0f0dc937fa4b19c3ba8a50 Reviewed-on: https://chromium-review.googlesource.com/1241694 Commit-Queue: Jonathan Freed <freedjm@chromium.org> Reviewed-by:
Justin DeWitt <dewittj@chromium.org> Cr-Commit-Position: refs/heads/master@{#594125}
-
Maks Orlovich authored
If the error is caused by a suspend (or some other kill), it will get delivered to URLLoader while there may still be live use in a disk_cache layer write. Bug: 882246, 881493, 884692 Cq-Include-Trybots: luci.chromium.try:linux_mojo Change-Id: Ic4f46b8f358940418045351e3f41bb29ef13d05b Reviewed-on: https://chromium-review.googlesource.com/1240518 Commit-Queue: Maks Orlovich <morlovich@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Cr-Commit-Position: refs/heads/master@{#594124}
-
Ryan Sturm authored
Change-Id: I0fe4991ff74227084f179282e9f1d12f471e6bc0 Reviewed-on: https://chromium-review.googlesource.com/1244603Reviewed-by:
Doug Arnett <dougarnett@chromium.org> Commit-Queue: Ryan Sturm <ryansturm@chromium.org> Cr-Commit-Position: refs/heads/master@{#594123}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/30dc6aaf878b..9412c8ec36d1 git log 30dc6aaf878b..9412c8ec36d1 --date=short --no-merges --format='%ad %ae %s' 2018-09-25 thestig@chromium.org Get rid of "exceptions" in CBC_QRCoderMatrixUtil. 2018-09-25 thestig@chromium.org Roll third_party/freetype/src/ dfddc2d97..abd997aa7 (9 commits) 2018-09-25 thestig@chromium.org Revert "Remove unreachable code in CPDF_DIBBase." Created with: gclient setdep -r src/third_party/pdfium@9412c8ec36d1 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:888743 TBR=dsinclair@chromium.org Change-Id: I81e542c61d7966800fd2d4efc2fc4a8f04e8cacc Reviewed-on: https://chromium-review.googlesource.com/1244115Reviewed-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@{#594122}
-
rajendrant authored
Tracking pixel images are small in general and would fit in the 2KB placeholder image. But it could be double fetched if it gets near the viewport, before the placeholder range response is received. One heuristic is to avoid lazyloading image elements with small dimensions (10x 10) specified in attributes. This CL implements this. Bug: 875086 Change-Id: I70149e5d57ee7e6216238d84bbdc9d24ee9114fd Reviewed-on: https://chromium-review.googlesource.com/1198562 Commit-Queue: rajendrant <rajendrant@chromium.org> Reviewed-by:
Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#594121}
-