- 28 May, 2019 40 commits
-
-
Caitlin Fischer authored
Bug: 966830 Change-Id: I738b691847869439dd38df6d6fa7595e87af9688 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628042 Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Reviewed-by:
Fabio Tirelo <ftirelo@chromium.org> Reviewed-by:
Tommy Martino <tmartino@chromium.org> Cr-Commit-Position: refs/heads/master@{#664010}
-
Thanh Nguyen authored
Proto with the features and related information to be logged for Chrome OS Search and Ranking project. Bug: 959705 Change-Id: I047dfc312d37862800fb3b48e5f30a98e85da254 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626837 Commit-Queue: Thanh Nguyen <thanhdng@chromium.org> Reviewed-by:
Jenny Zhang <jennyz@chromium.org> Reviewed-by:
Jia Meng <jiameng@chromium.org> Cr-Commit-Position: refs/heads/master@{#664009}
-
Nate Fischer authored
No change to production logic. This adds a regression test for http://crbug.com/960165. This loads a page and ensures that WebView correctly respects the Access-Control-Allow-Origin header, by using the JavaScript fetch() API. Bug: 960165 Test: run_webview_instrumentation_test_apk --enable-features=NetworkService,NetworkServiceInProcess -f AwNetworkConfigurationTest#testAccessControlAllowOriginHeader Change-Id: I74b6e789bb47a5ba8d70e1416bf963b0afbcb2ed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1618160 Commit-Queue: Nate Fischer <ntfschr@chromium.org> Reviewed-by:
Changwan Ryu <changwan@chromium.org> Cr-Commit-Position: refs/heads/master@{#664008}
-
Mason Freed authored
Previous to this CL, all blur filters, including those used within backdrop-filters, would use kClampToBlack tile mode. For backdrop- filters, that would cause the implied transparent black edge pixels to be drawn in within the element bounds, which made that portion of the backdrop-filtered content partially transparent, and exposed the unfiltered content underneath. With this change, backdrop-filter blur filters now use the kClamp tile mode, which clamps to the image's edge pixel values, instead of transparent black. Bug: 963031 Change-Id: I22c99eb339886c098330d1f21504909446657c36 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627637Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Mason Freed <masonfreed@chromium.org> Auto-Submit: Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#664007}
-
Hesen Zhang authored
Bug: 966969 Change-Id: I1178622066411bad23e14386511583fabe8971d2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1629015 Commit-Queue: Hesen Zhang <hesen@chromium.org> Reviewed-by:
David Trainor <dtrainor@chromium.org> Reviewed-by:
Xing Liu <xingliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#664006}
-
Sunny Sachanandani authored
Bug: 937108 Change-Id: If1a8979c5493204d40efcd262c8cb60650c95696 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632288 Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Frank Liberato <liberato@chromium.org> Cr-Commit-Position: refs/heads/master@{#664005}
-
Henry Jian authored
Currently, when a web app manifest adds new WST v2 parameters (or modifies existing ones), Chromium won't trigger an update because it's not doing diffs on WST v2 parameters. This CL adds web app manifest diffing for WST v2 parameters. Bug: 885313 Change-Id: I440e1f9681d2209868e15ec34c1c01e8c99a8a47 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1592359Reviewed-by:
Peter Kotwicz <pkotwicz@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Commit-Queue: Henry Jian <hzjian@google.com> Cr-Commit-Position: refs/heads/master@{#664004}
-
Kurt Horimoto authored
This CL creates OverlayPresenterUIDelegateImpl, which handles the UI for OverlayPresenters. Additionally, it adds OverlayContainerCoordinator, which provides the presentation context upon which to present requested overlay UI. Bug: 941745 Change-Id: Id44c906952260fbd0cb9e7f541c93fd70d2d7d4c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614696 Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org> Reviewed-by:
Mike Dougherty <michaeldo@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Reviewed-by:
Mark Cogan <marq@chromium.org> Cr-Commit-Position: refs/heads/master@{#664003}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/0cb2fdefc219..1f02e8488551 git log 0cb2fdefc219..1f02e8488551 --date=short --no-merges --format='%ad %ae %s' 2019-05-28 fmalita@chromium.org [skottie] Add support for more font weights 2019-05-28 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). 2019-05-28 reed@google.com skia helper for encoding video 2019-05-28 herb@google.com Use bulk advances in SkPDFEmitType1Font 2019-05-28 herb@google.com Replace SkStrikeSpec with SkStrikeSpecStorage 2019-05-28 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (nontrivial). Created with: gclient setdep -r src/third_party/skia@1f02e8488551 The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=kjlubick@google.com Change-Id: I4c315de542d664a71897310547e95fe52e6a5640 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632881Reviewed-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@{#664002}
-
Lan Wei authored
This reverts commit 42f777c7. Reason for revert: <INSERT REASONING HERE> Original change's description: > Use promise in wpt pointer event tests to finish the tests > > Instead of adding a variable to check if the test is finished, we can > create a promise object and finish the test at its last callback. > > Bug: 606367 > Change-Id: Iabf281a1fffca85630683e79436a8b442057b824 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1618002 > Commit-Queue: Lan Wei <lanwei@chromium.org> > Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#663936} TBR=lanwei@chromium.org,nzolghadr@chromium.org Change-Id: Ic907a109cc3c377347b80882318c95e05f2b2389 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 606367 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631364Reviewed-by:
Lan Wei <lanwei@chromium.org> Commit-Queue: Lan Wei <lanwei@chromium.org> Cr-Commit-Position: refs/heads/master@{#664001}
-
Malay Keshav authored
gfx::RRectF is a wrapper for SkRRect. SkRRect normalizes the corner radii values if the sum of 2 corner radii is larger than the length of the side between these two corners. This means that the constructor cannot initialize a rounded rect by sequentially setting the corner radius for each corner. All the corners have to be set atomically using the API provided by SkRRect so that the normalization happens correctly. Bug: 966488 Change-Id: I0e3f373e4425af905f1be1fc1bc9fda983bdf600 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1629010Reviewed-by:
Mason Freed <masonfreed@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Malay Keshav <malaykeshav@chromium.org> Cr-Commit-Position: refs/heads/master@{#664000}
-
Yue Li authored
Bug: b/123953783 Test: Local Build Change-Id: I2eccb356604ade028cb63471ee73484a470aeff5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1536767 Commit-Queue: Yue Li <updowndota@chromium.org> Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Reviewed-by:
Tao Wu <wutao@chromium.org> Reviewed-by:
Sam McNally <sammc@chromium.org> Cr-Commit-Position: refs/heads/master@{#663999}
-
Esmael El-Moslimany authored
A couple things have changed since this logic was added. cr-icon-button removes ripples before showing ripple. FocusRowBehavior focuses on the equivalent component when the row gains focus. With those changes, the extra logic to focus on the remove button after an item is removed is no longer necessary. Bug: 967579 Change-Id: Ie393dd3ab0ab9b82766ab23379e371b0487d8808 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1629722Reviewed-by:
Hector Carmona <hcarmona@chromium.org> Commit-Queue: Esmael El-Moslimany <aee@chromium.org> Cr-Commit-Position: refs/heads/master@{#663998}
-
Brandon Wylie authored
calling end on the animation instead of cancel (introduced in https://chromium-review.googlesource.com/c/chromium/src/+/1599741) is causing the focus animation to happen twice. Changing it back to cancel fixes the problem. Bug: 967289 Change-Id: I9d66ad85ac63aaf0fb369af32a4a518f1cebb4a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631947Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Brandon Wylie <wylieb@chromium.org> Cr-Commit-Position: refs/heads/master@{#663997}
-
Esmael El-Moslimany authored
Bug: 967610 Change-Id: I8a6c2f080a4f9d984ca186fece34b8c715f24afa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632812Reviewed-by:
-
danakj authored
The |ui_task| is injected by BrowserTestBase to replace the main message loop, and runs as part of BrowserMainRunner::Initialize(). Previously there were no Android browser tests so this path would not have been hit and had a NOTREACHED() for Android. We remove the OS_ANDROID defines and let Android run the |ui_task| the same way that desktop chrome browser tests do. R=jam@chromium.org Bug: 961849 Change-Id: Ic2e1362ea3bc76c4c31fe0d92d9c93a9350256d9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628160 Commit-Queue: danakj <danakj@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Cr-Commit-Position: refs/heads/master@{#663995}
-
Dale Curtis authored
This was never enabled due to crashing everywhere (across multiple attempts to enable), so remove the last (already non-functional) remaining vestiges. This should slightly speed up vp8 decoder selection time, since we have been falsely advertising support and failing in Initialize() for some time. BUG=769819 TEST=builds R=liberato Change-Id: I74cdfd0e45280ad621cc44036728d6bed8498c5f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1633035 Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Auto-Submit: Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
-
Jun Mukai authored
TBR=tsepez@chromium.org Bug: 958201 Test: trybot Change-Id: Ic3150a3c42b4956b64f5de62833d80c2237b23cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1623587 Commit-Queue: Jun Mukai <mukai@chromium.org> Reviewed-by:
-
Chris Palmer authored
It is flaky on that platform. Bug: 966169 Change-Id: Ifb58e50c26370965213cf5a81d8c55a9d93d9fee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1633033Reviewed-by:
Albert J. Wong <ajwong@chromium.org> Commit-Queue: Chris Palmer <palmer@chromium.org> Cr-Commit-Position: refs/heads/master@{#663992}
-
Austin Eng authored
Sharding in dawn_end2end_tests is unecessary. Remove it first in gpu_dawn_gtests. There may be remaining flakiness in Dawn's OpenGL backend so we should first remove sharding on ToT Dawn before removing sharding from DEPS Dawn bots. Change-Id: I52ae3886b382eedcec59cd0ea4448abbe0d2eb7a Bug: 948902 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1564546Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Austin Eng <enga@chromium.org> Cr-Commit-Position: refs/heads/master@{#663991}
-
Anne Lim authored
Remove unneeded callbacks in CCSM. They were present because an older version of StrikeDatabase used them, but it got phased out. Bug: 884817 Change-Id: I51b38a2a9606795f47aa77a879ed75ced092058f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628331 Commit-Queue: Anne Lim <annelim@google.com> Reviewed-by:
Jared Saul <jsaul@google.com> Reviewed-by:
Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#663990}
-
Ryan Sturm authored
This adds a client holdback to the otherwise GWS study. This will go to Beta soon. Change-Id: Ie7f7b5bf328641b25bd6cf7202afcce1995a8ab6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1623142Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Ryan Sturm <ryansturm@chromium.org> Commit-Queue: Ryan Sturm <ryansturm@chromium.org> Cr-Commit-Position: refs/heads/master@{#663989}
-
Daniel McArdle authored
Preallocation in BookmarkNodeData::Element::ReadFromPickle can be abused by a pickle consisting of N nested children. If each child claims to contain M more children, the fast-fail logic (returns false when fewer than M children were provided) would never run until reading the last element at depth N. Along the way, we would have allocated N * M elements rather than N. Bug: 966282 Change-Id: I02de64d091091e5ab5b1628cabe9a5caea6fbe2c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628836Reviewed-by:
-
Daniel Murphy authored
A recent bug fix caused another problem with re-entry (or lack of re-entry) where the connections_ list was no longer updated during force close, causing uaf issues when that list was iterated later. R=pwnall@chromium.org Bug: 966557 Change-Id: I3d5ed163b030c1da8a6515d32108e86868be75b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632287 Commit-Queue: Daniel Murphy <dmurph@chromium.org> Commit-Queue: Victor Costan <pwnall@chromium.org> Auto-Submit: Daniel Murphy <dmurph@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#663987}
-
Ned Williamson authored
BUG=967098 Change-Id: I733da2f77f521bb551e0e50e9c5f5e69eace3411 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631353Reviewed-by:
Abhishek Arya <inferno@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/5a808b86d890..ee244c772a41 git log 5a808b86d890..ee244c772a41 --date=short --no-merges --format='%ad %ae %s' 2019-05-28 geofflang@chromium.org Vulkan: Move command graph and garbage to ContextVk. 2019-05-28 jonahr@google.com Addition of dEQP "KHR" test variants to generate_stats Created with: gclient setdep -r src/third_party/angle@ee244c772a41 The AutoRoll server is located here: https://autoroll.skia.org/r/angle-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=cwallez@google.com Change-Id: I4849036e4e57bda9f15484aef228c3fe8d51ec48 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632970Reviewed-by:
-
Alex Leung authored
* Add CastAudioDeviceFactory to use simple AudioOutputDevice; disables mixer * Use MakeAudioOutputStream instead of MakeAudioOutputStreamProxy; prevents AudioOutputStream from closing * Update CastAudioOutputStream Start/Stop/Flush logic. Bug: b/124402185 Change-Id: Iabf4c06e7b2af40dd714d589713ac00880c25e89 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1625959Reviewed-by:
Yuchen Liu <yucliu@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
-
Xiaocheng Hu authored
Since we have now supported CSS-generated contents in |NGOffsetMapping|, we should make sure an |NGOffsetMappingUnit| is not CSS-generated before calling |GetOwner()|, otherwise we should use |AssociatedNode()| instead. This patch converts too calls of |GetOwner()| into |AssociatedNode()| so that we don't hit the DCHECK in |GetOwner()|. Bug: 967106 Change-Id: I62c362d93ba0608d0e6bcdd74c0d27fe0ffa7554 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632900 Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> Commit-Queue: Emil A Eklund <eae@chromium.org> Auto-Submit: Xiaocheng Hu <xiaochengh@chromium.org> Reviewed-by:
Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#663983}
-
Ehsan Karamad authored
The process of creating MimeHandlerView is: * Navigation to resource starts * MimeHandlerViewEmbedder is created * HTMLPlugInElement::UpdatePlugin is called * MimeHandlerViewContainerManager is notified * HTMLPlugInElement creates a frame * MimeHandlerViewEmbedder observes the new frame and attaches GuestView, and destroys itself. These steps are legitimately disturbed when the embedder is not authorized to load plugins (e.g., in <webview> when using permissions). In such cases, the update from HTMLPlugInElement does not reach the MimeHandlerViewContainerManager and also a plugin frame is not created. Therefore, MimeHandlerViewEmbedder does not get destroyed. This CL will change the update process so that even for blocked plugins the MHVCM is notified (of the failure) which gives it a chance to notify the browser in turn and clean up the MimeHandlerViewEmbedder. In line with the change, the test: WebViewPluginTest.TestLoadPluginInternalResource is modified to assert no MimeHandlerViewEmbedders are lying around. Bug: 967045 Change-Id: Ic63a980883240fe8098a4ee8d5e3ae3b9cc46415 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1629071Reviewed-by:Karan Bhatia <karandeepb@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Reviewed-by:
Ehsan Karamad <ekaramad@chromium.org> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Reviewed-by:
James MacLean <wjmaclean@chromium.org> Commit-Queue: Ehsan Karamad <ekaramad@chromium.org> Cr-Commit-Position: refs/heads/master@{#663982}
-
Mei Liang authored
This CL refactors some tab group specific logic in TabLiseMediator#onMovedTab() to TabGroupModelFilter. And TabListMediator should listen to additional the TabGroupModelFilter.Observer to update the UI model. Change-Id: Ieb7bf00b4811956b11dbb0a44fcc3f6415cd4340 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628272 Commit-Queue: Mei Liang <meiliang@chromium.org> Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Cr-Commit-Position: refs/heads/master@{#663981}
-
Kyle Milka authored
Add a flag to show a Google Search shortcut on the NTP by default. Only add the shortcut if this is a Chrome branded build. Bug: 962558 Change-Id: I4f5cd18b0dc3182264057f55eb381cb94d6ee49b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614457Reviewed-by:
Marc Treib <treib@chromium.org> Reviewed-by:
Ramya Nagarajan <ramyan@chromium.org> Commit-Queue: Kyle Milka <kmilka@chromium.org> Cr-Commit-Position: refs/heads/master@{#663980}
-
chromium-autoroll authored
This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 Please note that, despite rolling to chrome/android, this profile is used for both Linux and Android. The AutoRoll server is located here: https://autoroll.skia.org/r/afdo-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=gbiv@chromium.org Change-Id: I26ffa0087edc9ef4feea29b7ab7f30b566ae3c6a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632944Reviewed-by:
-
Evan Stade authored
ShowWarningBanner() and HideWarningBanner() are combined into UpdateWarningMessage(). TBR=tsepez@chromium.org Bug: 958206 Change-Id: I1569d2cec960357c5e6151bdfc32800be495c268 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1629428 Commit-Queue: Evan Stade <estade@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#663978}
-
Khushal authored
R=piman@chromium.org Bug: 958981 Change-Id: I28cc5808f02c17b372e0557652c188ae1e2b9a27 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632899 Commit-Queue: Khushal <khushalsagar@chromium.org> Commit-Queue: Antoine Labour <piman@chromium.org> Auto-Submit: Khushal <khushalsagar@chromium.org> Reviewed-by:
Antoine Labour <piman@chromium.org> Cr-Commit-Position: refs/heads/master@{#663977}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/12d7da217249..698a4380c296 git log 12d7da217249..698a4380c296 --date=short --no-merges --format='%ad %ae %s' 2019-05-28 tsepez@chromium.org Remove unneeded circular include between fpdfdoc and fpdfapi/page 2019-05-28 thestig@chromium.org Minimize allow_circular_includes_from entries for fxge. 2019-05-28 thestig@chromium.org Move AdobeCMYK_to_sRGB functions to fxge. 2019-05-28 thestig@chromium.org Break circular dependency between fxge and fpdfdoc. 2019-05-28 thestig@chromium.org Rename |g_CMYK| to |kCMYK|. Created with: gclient setdep -r src/third_party/pdfium@698a4380c296 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=pdfium-deps-rolls@chromium.org Change-Id: Ib132633eff1dea4222e61e1f2096ae25c1cddc01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632972Reviewed-by:
-
Gil Dekel authored
A lightweight WebP parser that validates that a given data stream encodes a lossy WebP image by following the WebP Container Specification found at: https://devsite.googleplex.com/speed/webp/docs/riff_container After format validation, the parser uses the Vp8Parser to parse the VP8 key frame and returns a Vp8FrameHeader when parsing succeeds. Note: This parser only supports lossy WebP formats. There are two reasons in favor of rolling out a new lightweight WebP parser (instead of using libwebp): 1) It's going to be used both by the render and gpu processes. Avoiding a third-party lib is preferable. 2) the Vp8Parser was written to fit the VA-API better, i.e. it produces objects that can be fed into the VA-API with minimum processing. This change also moves the VP8 parser from //media/filters to //media/parser. Bug: 877694 Test: WebpParserTest.* Change-Id: Ia553bc320cf0c136a859d24a4422e2bcc6e9c2c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617637 Commit-Queue: Gil Dekel <gildekel@chromium.org> Reviewed-by:
Miguel Casas <mcasas@chromium.org> Reviewed-by:
Andres Calderon Jaramillo <andrescj@chromium.org> Cr-Commit-Position: refs/heads/master@{#663975}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/bcf517c0..2cb25737 Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I2b96edd135093ea4854ccce28cea1bfe0d06381c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632878Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#663974}
-
James Cook authored
It was added as part of the mustash project to work around test failures due to minimum window sizes. "chromeos: converts WindowState to aura::Window" https://codereview.chromium.org/2901663003 That CL's comments mention making the windows bigger as a better workaround. This CL increases the window widths to >104 dips, which appears to be our current minimum. Bug: none Test: ash_unittests Change-Id: Icb79d12bb48dc8335bdfb6346297fc777d0abe9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1620485 Commit-Queue: James Cook <jamescook@chromium.org> Reviewed-by:
-
Drew Stonebraker authored
This is primarily to move the main content from https://www.chromium.org/developers/androidwebview/android-webview-beta to our new location for docs in markdown. Also, this adds some detail that the previous chromium.org page didn't have. Bug: 965357 Test: Click on the markdown file in this CL, then click "gitiles" at the Test: top of the page to view in formatted markdown. Change-Id: I55dffa24e3fb72b5a2eaf87de2a47a8d9e362af3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1621490 Commit-Queue: Drew Stonebraker <stonebraker@chromium.org> Reviewed-by:
Richard Coles <torne@chromium.org> Reviewed-by:
Nate Fischer <ntfschr@chromium.org> Cr-Commit-Position: refs/heads/master@{#663972}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/c5b8a73247c4..10e57cf61851 git log c5b8a73247c4..10e57cf61851 --date=short --no-merges --format='%ad %ae %s' 2019-05-28 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). Created with: gclient setdep -r src/third_party/depot_tools@10e57cf61851 The AutoRoll server is located here: https://autoroll.skia.org/r/depot-tools-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=agable@chromium.org Change-Id: I194e77a3dc7ba23f35e6ce8b6d83163f65575ed2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632808Reviewed-by:
-
