- 09 Jun, 2020 40 commits
-
-
Yue Li authored
Bug: b/156405987 Test: Manual Test Change-Id: I57c0c37ca7865f23df730e84167f9be6368dc33a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227900 Commit-Queue: Yue Li <updowndota@chromium.org> Reviewed-by:
Jeroen Dhollander <jeroendh@google.com> Cr-Commit-Position: refs/heads/master@{#776593}
-
Aaron Colwell authored
- Updates directory and filenames to use more inclusive naming. - Updates header guards on renamed files. - Updates build and dependency rules. - Update #includes Bug: 1092096 Change-Id: Ie084d8f786e63c7f49d6af2a546bdf8fe813f24f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2236454Reviewed-by:
Chris Mumford <cmumford@google.com> Reviewed-by:
Michael Crouse <mcrouse@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Reviewed-by:
Charlie Harrison <csharrison@chromium.org> Commit-Queue: Aaron Colwell <acolwell@chromium.org> Auto-Submit: Aaron Colwell <acolwell@chromium.org> Cr-Commit-Position: refs/heads/master@{#776592}
-
Rakib M. Hasan authored
Bug: 1050760, 1050754 Change-Id: I26e3b9262db6a7e7de40f3daf653d66abb959d5e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2236496Reviewed-by:
Robert Ma <robertma@chromium.org> Commit-Queue: Rakib Hasan <rmhasan@google.com> Cr-Commit-Position: refs/heads/master@{#776591}
-
Xi Han authored
We don't re-enable the failing tests in the reland. Original change's description: > [Instant Start] Create ToolbarManger before showing overview. > > In this CL, we introduce an additional state in InflationObserver: > onInflationComplete. This event happens between onPreInflationStartup > and onPostInflationStartup, thus provides a way to split the > implementation of onPostInflationStartup into two methods. > > In RootUiCoordinatior, the ToolbarManger is created in > onInflationComplete, and ChromeTabbedActivity calls showOverview() > after RootUiCoordinatior#onInflationComplete but before initializing > other components in onPostInflationStartup. Thus, ToolbarManager setups > an OverviewModeObserver and won't lose any early events that an > overview is shown or overview mode is changed. > > Bug: 1077022 > Change-Id: I6bc8b96906a9519a928c6490bec0ca158b3d6241 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2181667 > Reviewed-by: Matthew Jones <mdjones@chromium.org> > Reviewed-by: Yaron Friedman <yfriedman@chromium.org> > Reviewed-by: Ender <ender@google.com> > Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org> > Commit-Queue: Xi Han <hanxi@chromium.org> > Cr-Commit-Position: refs/heads/master@{#776073} Bug: 1077022 Change-Id: Id01abc7d9ed2df245a327105e72ab25fa844daa4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2237646Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Commit-Queue: Xi Han <hanxi@chromium.org> Cr-Commit-Position: refs/heads/master@{#776590}
-
Ian Barkley-Yeung authored
Increase the detail on the CrashReport.DumpWithoutCrashingResult.FromInitSharedMemoryIfNeeded metric. In particular, record which of the two crash handlers succeeded or failed. This will allow me to distinguish "Breakpad is always failing, Crashpad is sometimes succeeding" from "Breakpad sometimes succeeds, sometimes fails". NOTE: Renamed CrashReport.DumpWithoutCrashingResult.FromInitSharedMemoryIfNeeded2 because of the new enum. BUG=chromium:1074115 Change-Id: I8bcd6e10177d23f9c7c0f8a6e1c637192406a249 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2236469 Commit-Queue: Ian Barkley-Yeung <iby@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#776589}
-
Bettina authored
Bug: 1038797 Change-Id: Icb3f4412796bae267cd0427ec440b49dd7c6c4dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2236495Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Commit-Queue: Bettina Dea <bdea@chromium.org> Cr-Commit-Position: refs/heads/master@{#776588}
-
Will Harris authored
https://helpx.adobe.com/security/products/flash-player/apsb20-30.html BUG=412078 TBR=jschuh@chromium.org Change-Id: I4975af48096599a480342dacc3d49984be3e4bce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2238012Reviewed-by:
Will Harris <wfh@chromium.org> Commit-Queue: Will Harris <wfh@chromium.org> Cr-Commit-Position: refs/heads/master@{#776587}
-
Pavel Yatsuk authored
This reverts commit 3d506040. Reason for revert: The test fails on multiple builders. E.g.: https://ci.chromium.org/p/chromium/builders/ci/Marshmallow%2064%20bit%20Tester/32695 The call stack is: android.support.test.espresso.base.DefaultFailureHandler$AssertionFailedWithCauseError: View is present in the hierarchy: MessageCardView{id=2131428697, res-name=tab_grid_message_item, visibility=VISIBLE, width=1038, height=156, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, root-is-layout-requested=false, has-input-connection=false, x=21.0, y=603.0, child-count=3} Expected: is <false> Got: <true> at dalvik.system.VMStack.getThreadStackTrace(Native Method) at java.lang.Thread.getStackTrace(Thread.java:580) at android.support.test.espresso.base.DefaultFailureHandler.getUserFriendlyError(DefaultFailureHandler.java:82) at android.support.test.espresso.base.DefaultFailureHandler.handle(DefaultFailureHandler.java:53) at android.support.test.espresso.ViewInteraction.runSynchronouslyOnUiThread(ViewInteraction.java:184) at android.support.test.espresso.ViewInteraction.check(ViewInteraction.java:158) at org.chromium.chrome.browser.tasks.tab_management.TabGridIphTest.testNotShowIPHInMultiWindowMode(TabGridIphTest.java:344) Original change's description: > Skip showing tab switcher message card in multi-window mode > > Bug: 1085630 > Change-Id: If0e6e852458aedf448647e3ab8320519c4775bd2 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2216630 > Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org> > Reviewed-by: Mei Liang <meiliang@chromium.org> > Commit-Queue: Yue Zhang <yuezhanggg@chromium.org> > Cr-Commit-Position: refs/heads/master@{#776308} TBR=wychen@chromium.org,meiliang@chromium.org,yuezhanggg@chromium.org Change-Id: I60c9ff0219832ccda197550ee8de92b6bb91fb54 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1085630 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2236502Reviewed-by:
Pavel Yatsuk <pavely@chromium.org> Commit-Queue: Pavel Yatsuk <pavely@chromium.org> Cr-Commit-Position: refs/heads/master@{#776586}
-
Raphael Kubo da Costa authored
IWYU. This fixes the libstdc++ build after commit 5e47a2b2 ("[gamepad] Keep track of which buttons and axes are used"). Bug: 957519 Change-Id: I835b279a84b129c7af78ff10a42c39b90d0bd6fa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2237253 Auto-Submit: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> Commit-Queue: Matt Reynolds <mattreynolds@chromium.org> Reviewed-by:
Matt Reynolds <mattreynolds@chromium.org> Cr-Commit-Position: refs/heads/master@{#776585}
-
Nazerke authored
Bug: 1072370 Change-Id: Ib3b773f01e3c2f3b3d4d0e1ea60599878efe8840 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2235596 Commit-Queue: Nazerke Kalidolda <nazerke@google.com> Reviewed-by:
Mark Cogan <marq@chromium.org> Cr-Commit-Position: refs/heads/master@{#776584}
-
Raphael Kubo da Costa authored
dict.has_key() does not exist in Python 3. Just use dict.get() to achieve the same result with fewer checks. Bug: 941669 Change-Id: Iaeec0ac1ec8efd88c796c73344fea91eaab0df7f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2236435 Auto-Submit: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> Commit-Queue: Zhenyao Mo <zmo@chromium.org> Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Cr-Commit-Position: refs/heads/master@{#776583}
-
Fan Yang authored
https://quiche.googlesource.com/quiche.git/+log/6cccce4f5870..faf8b0277550 $ git log 6cccce4f5..faf8b0277 --date=short --no-merges --format='%ad %ae %s' 2020-06-08 renjietang For IETF QUIC client: When 0-RTT is rejected, check the server-sent transport params and close connection if server's limit exceeds what the client has already used. 2020-06-08 nharper Create a SessionCache for TLS resumption in QUIC HTTP EndToEndTest 2020-06-08 renjietang In IETF QUIC client: Delay retransmission of 0-RTT data to be after QuicSession config is set to the fresh server config. 2020-06-08 nharper Add support for accepting 0-RTT in TlsServerHandshaker 2020-06-08 danzh (n/a) open source quic gso batch writer. not protected. 2020-06-08 nharper Add SerializeTransportParametersForTicket 2020-06-08 fayang Deprecate gfe2_reloadable_flag_quic_change_default_encryption_level. Created with: roll-dep src/net/third_party/quiche/src src/third_party/quic_trace/src R=dschinazi@chromium.org Change-Id: If3f80075dd3442026dd2e83d4de6fa190738e0ab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2237769 Auto-Submit: Fan Yang <fayang@chromium.org> Commit-Queue: David Schinazi <dschinazi@chromium.org> Reviewed-by:
David Schinazi <dschinazi@chromium.org> Cr-Commit-Position: refs/heads/master@{#776582}
-
Philip Rogers authored
This patch unifies the grouping property logic used for stacking contexts (ComputedStyle::UpdateIsStackingContextWithoutContainment), PaintLayer creation (LayoutBox::LayerTypeRequired), 3d transform flattening (ComputedStyle::UsedTransformStyle3D), and svg isolation (SVGLayoutSupport::IsIsolationRequired). Grouping properties are specified in [1]. This patch reduces complexity and is likely to improve performance with fewer checks in LayoutBox::LayerTypeRequired. Box reflection (-webkit-box-reflect) only applies to boxes but is used to create a stacking context for all objects. To avoid changing this behavior, a parameter is used for HasGroupingProperty. By recognizing CSS clip as a grouping property, compositing reason finder is able to force layers for clips with composited descendants (CSS clip -> HasClipRelatedProperty -> kClipsCompositingDescendants), which results in some test changes. [1] https://drafts.csswg.org/css-transforms-2/#grouping-property-values Bug: 1068596 Change-Id: I86ca4a41b0324f2966c557dce6396b3bba684598 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2234541 Commit-Queue: Philip Rogers <pdr@chromium.org> Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#776581}
-
Dan Harrington authored
Bug: 1092633 Change-Id: I69c0ad234c2d78216c72536ece56e2cbfb45f1c4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2236680 Auto-Submit: Dan H <harringtond@chromium.org> Reviewed-by:
Ian Wells <iwells@chromium.org> Commit-Queue: Ian Wells <iwells@chromium.org> Cr-Commit-Position: refs/heads/master@{#776580}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/2a9754b30e90..929d66714815 2020-06-09 aerotwist@chromium.org Adds estimated TBT to timeline 2020-06-09 alexrudenko@chromium.org Ignore changes to mutable inline stylesheets If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Id16e32b6a5acd7edd6a97cfed15418764932706a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2237869Reviewed-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@{#776579}
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC cr-fuchsia+bot@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast Tbr: cr-fuchsia+bot@chromium.org Change-Id: I9798d78dd73dfeabf6732332ed5b7dc69781a08a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2237872Reviewed-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@{#776578}
-
Teresa Kang authored
Adding performance tests that serve to measure how much performance improvements can be obtained by the addition of willReadFrequently option. Test cases include multiple draws and multiple getImageData calls. The canvas-getImageData-smooth.html is corrected and shows that the discrepancy between cpu and gpu rendering does exist. Bug: 1090180 Change-Id: I8701f4389d8f0c9a26498d35b874453512e4669f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2231808Reviewed-by:
Juanmi Huertas <juanmihd@chromium.org> Reviewed-by:
Fernando Serboncini <fserb@chromium.org> Commit-Queue: Teresa Kang <teresakang@google.com> Cr-Commit-Position: refs/heads/master@{#776577}
-
Adam Norberg authored
It now takes an XPC protocol as a parameter and mocks the service specified. Some type safety is lost in the process, since I had to convert id<P> to raw id in a few spots; I spend a while trying to figure out how to do this with templates and concluded that I probably couldn't (because C++ does not understand an Objective-C protocol, since it is completely outside the C++ type system), and figured the unchecked type is tolerable in test code. Bug: 1055876 Change-Id: I2fe5684b34b64245f6d9fe7716c9bdf7cd97c76e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2231703Reviewed-by:
Sorin Jianu <sorin@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Commit-Queue: Adam Norberg <norberg@google.com> Cr-Commit-Position: refs/heads/master@{#776576}
-
Xida Chen authored
TBR=treib@chromium.org NOTRY=true Bug: 1092721 Change-Id: I680448ba7ca6926d058fb48cbca9c38c83adb8b8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2238267Reviewed-by:
Xida Chen <xidachen@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#776575}
-
Oksana Zhuravlova authored
This is a reland of a0061b0e The updated trace processor for mac has rolled in https://crrev.com/c/2236111. Original change's description: > Reland "[tools/perf] Add webview_cpu_usage metric" > > This is a reland of 5c76e821 > > The test failures that caused the revert have been fixed in > https://r.android.com/1325791 and rolled into chromium in > https://crrev.com/c/2236240. > > Original change's description: > > [tools/perf] Add webview_cpu_usage metric > > > > This change adds a metric that calculates the amount of time WebView > > spends on different frequencies. > > > > Bug: b/157855323 > > Change-Id: Ibb1fa61cc2ba1479f2b76ef642dc03c64a9a14b5 > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2231452 > > Reviewed-by: Mikhail Khokhlov <khokhlov@google.com> > > Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#775713} > > Bug: b/157855323 > Change-Id: I45552ebb5b3ca49c05506495e16a7a20e02ade86 > TBR: khokhlov@google.com > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2236055 > Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org> > Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org> > Cr-Commit-Position: refs/heads/master@{#776374} TBR: oksamyt@chromium.org Bug: b/157855323 Change-Id: If89eab0236486f3d09e381881cac3743d6942368 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2235719Reviewed-by:
Mikhail Khokhlov <khokhlov@google.com> Commit-Queue: Mikhail Khokhlov <khokhlov@google.com> Cr-Commit-Position: refs/heads/master@{#776574}
-
Chris Lu authored
This change adds two classes: TranslateInfobarModalOverlayMediator, which serves as the mediator for Translate Infobar Overlays, and TranslateInfobarModalOverlayCoordinator, which manages the presentation of the modal. FakeInfobarTranslateModalConsumer is created for testing the mediator. Bug: 1071914 Change-Id: Ic6fe7d49966aee1426840f9bdc6033699aa7c09e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2233485 Commit-Queue: Chris Lu <thegreenfrog@chromium.org> Reviewed-by:
Sergio Collazos <sczs@chromium.org> Cr-Commit-Position: refs/heads/master@{#776573}
-
Manuel Rego Casasnovas authored
Change-Id: I783825bb9362df3c1a43f10ac8666f69332bd774 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2238106 Commit-Queue: Manuel Rego <rego@igalia.com> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#776572}
-
Mohsen Izadi authored
Currently, key events set EventTimeForNow() as their time stamp if the provided time stamp is null. This CL expands this to all event types. It also sets a proper time stamp for native key events generated by ui::test::EventGenerator. Hopefully, this change makes tests that rely on event timings more reliable. Bug: 1086620 Change-Id: I79d0e91ce91da227f2c832c7044c5b9b42369af8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2228055Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Mohsen Izadi <mohsen@chromium.org> Cr-Commit-Position: refs/heads/master@{#776571}
-
Antonio Gomes authored
... instead of WebMediaStreamSource. CL is a follow up of https://crrev.com/c/2236014, where the use of MediaStreamComponent was adopted instead of WebMediaStreamTrack. BUG=704136 R=guidou@chromium.org Change-Id: Ic23327f40cc5d1e55e760943477f74723b312e5b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2237768 Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#776570}
-
Jeroen Dhollander authored
Now that the |AssistantState::READY| flag has been removed, we can rename the NEW_READY flag to READY. Bug: b/142428671 Change-Id: If874e8e856e34fefe75e0b39c937258f255261d6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2236289 Commit-Queue: Jeroen Dhollander <jeroendh@google.com> Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#776569}
-
Nate Chapin authored
Change-Id: I93c517158d5c01f777ea8e923efb29efeb48435a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2236397Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Nate Chapin <japhet@chromium.org> Cr-Commit-Position: refs/heads/master@{#776568}
-
Andrew Grieve authored
Dex command was hitting length limits. Bug: 1092918 Change-Id: Idcaf0706bf57882178440d9c8597985daa315d49 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2237713 Commit-Queue: Andrew Grieve <agrieve@chromium.org> Commit-Queue: Sam Maier <smaier@chromium.org> Auto-Submit: Andrew Grieve <agrieve@chromium.org> Reviewed-by:
Sam Maier <smaier@chromium.org> Cr-Commit-Position: refs/heads/master@{#776567}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/a7e60fe18677..3fd631b2397e 2020-06-09 hjd@google.com Merge "ui: Run npm audit fix --force" If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:linux-perfetto-rel Bug: None Tbr: perfetto-bugs@google.com Change-Id: I1d7d112829535aee4d818fe7ce2743961130921b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2237868Reviewed-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@{#776566}
-
Scott Violet authored
As WebLayer is for use on platforms other than Android, I needed a new name. I went with js_injection as this is mostly about injecting js in the renderer. If you can think of a better name, I'm happy to rename. BUG=1042771 TEST=covered by android_webview tests Change-Id: I2fb39266ef5958c73b28f8bf605d4180cd2fa02f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2234551 Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Shimi Zhang <ctzsm@chromium.org> Cr-Commit-Position: refs/heads/master@{#776565}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/7910a8f76121..a01ec53bddbd 2020-06-09 bsalomon@google.com Remove axis alignment restriction on small CPU blur 2020-06-09 johnstiles@google.com Revert "Add JavaInputStreamAdaptor files into third_party directory." 2020-06-09 bungeman@google.com Document skia::textlayout::Run is non-assignable. 2020-06-09 mtklein@google.com remove unnecessary hsw opts If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC bungeman@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md 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 Bug: chromium:1087705 Tbr: bungeman@google.com Change-Id: Iabc6296c420b5c7e0a0a30870bb228bed20f7db9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2237867Reviewed-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@{#776564}
-
Eric Willigers authored
The app launch histograms remain useful until Chrome Apps are removed. https://blog.chromium.org/2020/01/moving-forward-from-chrome-apps.html June 2022: End support for Chrome Apps on Chrome OS for all customers. Bug: 1088772, 1088773 Change-Id: Id2fa7612d52719b814d8736252df1fc95c291516 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2224893Reviewed-by:
Alan Cutter <alancutter@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Auto-Submit: Eric Willigers <ericwilligers@chromium.org> Commit-Queue: Robert Kaplow <rkaplow@chromium.org> Cr-Commit-Position: refs/heads/master@{#776563}
-
Frank Tang authored
https://chromium.googlesource.com/chromium/deps/icu.git/+log/630b884..46f53df 46f53df Add fuzzer to try ToUpper/ToLower by Frank Tang 53eca4c Cherrypick the upstream PR 1140 by Frank Tang ICU-13786 Fix addLikelySubtags/minimizeSubtags #1140 Bug: v8:10448, 1078274 Change-Id: I887bffd5df022689c7c9c07eef6b840a6755d81d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2235734Reviewed-by:
Jungshik Shin <jshin@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#776562}
-
Rouslan Solomakhin authored
Before this patch, PaymentAppService would release its references in the destructor, which is the second phase of browser shutdown, as opposed to the KeyedService::Shutdown() method, which is the first phase, where all references should be released. This may have caused a crash when closing the browser. This is a speculative patch to have PaymentAppService release its references to the payment app factories during the first phase of browser shutdown. After this patch, PaymentAppService releases its references in the KeyedService::Shutdown() method, which is the first phase of browser shutdown. Bug: 1077713 Change-Id: Ic5785f703156bea2af7a1a03fca4ca6a39bb7dfe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2236464Reviewed-by:
Liquan (Max) Gu <maxlg@chromium.org> Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org> Cr-Commit-Position: refs/heads/master@{#776561}
-
Sami Kyostila authored
WebCore.ScriptedIdleTaskController.IdleCallbackOverrun was already removed from Chrome in 2017 by https://chromium-review.googlesource.com/803338. Bug: 1089649 Change-Id: Ib4b1ae39e78f64702815193601d18a0b5f373332 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2236144 Commit-Queue: Sami Kyöstilä <skyostil@chromium.org> Commit-Queue: Alexander Timin <altimin@chromium.org> Auto-Submit: Sami Kyöstilä <skyostil@chromium.org> Reviewed-by:
Alexander Timin <altimin@chromium.org> Cr-Commit-Position: refs/heads/master@{#776560}
-
Etienne Pierre-doray authored
NonEmptyPaint3 is replacing NonEmptyPaint2. As a first step, expiry and owner is updated. https://groups.google.com/a/google.com/g/chrome-catan/c/BhJOc7JIYeY/m/KvfHr2sqBgAJ Bug: 1091379, 1089531 Change-Id: I71134b54c6455b366fdb3f65541a69499ea893e1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2231518Reviewed-by:
Mark Pearson <mpearson@chromium.org> Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org> Cr-Commit-Position: refs/heads/master@{#776559}
-
spdonghao authored
Bug: 1086961 Change-Id: If811181513eced84a7c92960520a5f8e5f398398 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218849 Commit-Queue: Hao Dong <spdonghao@chromium.org> Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Reviewed-by:
Xi Han <hanxi@chromium.org> Cr-Commit-Position: refs/heads/master@{#776558}
-
Jeffrey Cohen authored
Bug: 1083851 Change-Id: I569c5dc14de4d6590cbd96901ecae7b505dbdec2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2236248Reviewed-by:
David Trainor <dtrainor@chromium.org> Reviewed-by:
Patrick Noland <pnoland@chromium.org> Commit-Queue: Jeffrey Cohen <jeffreycohen@chromium.org> Cr-Commit-Position: refs/heads/master@{#776557}
-
Chromium WPT Sync authored
Using wpt-import in Chromium e95a3d28. With Chromium commits locally applied on WPT: 9c24e63c "Check for first frame in CreateImageBitmap" a8a28083 "[Security][Coop] Browsing context switch reporting WPT" b2436c3b "Ensure cloning a template element into an inactive document does not crash." 027aefc6 "OPTION element: Update OPTION label even if it has invalid markup" d29069f3 "Fix issues with declarative shadow dom <template> during parsing" 0776aa6d "Mark pointerevent_pointermove_in_pointerlock test non flaky" Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md NOAUTOREVERT=true TBR=foolip@google.com No-Export: true Change-Id: Id25666c68e846253b2432891a6ee235dde7cc0ab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2237647Reviewed-by:
WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#776556}
-
Mikhail Khokhlov authored
It turns out different devices have different limits for power rails counters, so we can't compute the exact drain value if we don't know the device. This CL replaces the exact value with an estimation in that case. Change-Id: I8b4f1f63a6b9716a119f5f0a8f001c7801e10eb5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2236480Reviewed-by:
Eric Seckler <eseckler@chromium.org> Commit-Queue: Mikhail Khokhlov <khokhlov@google.com> Cr-Commit-Position: refs/heads/master@{#776555}
-
Xida Chen authored
TBR=treib@chromium.org NOTRY=true Bug: 1092924 Change-Id: If9da60f70fc19954493a6ae6bfe082644fe556a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2237721Reviewed-by:
Xida Chen <xidachen@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#776554}
-