- 09 Feb, 2019 29 commits
-
-
Sebastien Marchand authored
Notifying the observers that we have tried to refresh the value but that it failed adds some useless complexity. Bug: 771478 Change-Id: I2f44a115f087fbdad583627b0552ecb466866610 Reviewed-on: https://chromium-review.googlesource.com/c/1461330 Commit-Queue: Sébastien Marchand <sebmarchand@chromium.org> Auto-Submit: Sébastien Marchand <sebmarchand@chromium.org> Reviewed-by:
oysteine <oysteine@chromium.org> Cr-Commit-Position: refs/heads/master@{#630581}
-
Vlad Tsyrklevich authored
Fix missing includes pointed out by git cl lint. Change-Id: Idc50ba106c1fead5729988368ec46f25e9b0290b Reviewed-on: https://chromium-review.googlesource.com/c/1455467 Auto-Submit: Vlad Tsyrklevich <vtsyrklevich@chromium.org> Commit-Queue: Vitaly Buka <vitalybuka@chromium.org> Reviewed-by:
Vitaly Buka <vitalybuka@chromium.org> Cr-Commit-Position: refs/heads/master@{#630580}
-
Kalvin Lee authored
The "grit newgrd" command was found broken from a previous refactor. This change addresses the error. R=thestig@chromium.org Change-Id: Ia3fb3c2d06a43d0f8223ccd14febdb71153972b6 Reviewed-on: https://chromium-review.googlesource.com/c/1461345 Auto-Submit: Kalvin Lee <kdlee@chromium.org> Commit-Queue: Kalvin Lee <kdlee@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#630579}
-
Danyao Wang authored
The failing expectations are required because hasEnrolledInstrument() is not yet turned on by default in Blink. These tests pass when running Chrome with --enable-features=PaymentRequestHasEnrolledInstrument. Bug: 915907 Change-Id: I2189bfedad813e7942c7ddbd44aac78d1b895a30 Reviewed-on: https://chromium-review.googlesource.com/c/1461313 Commit-Queue: Danyao Wang <danyao@chromium.org> Reviewed-by:
Rouslan Solomakhin <rouslan@chromium.org> Cr-Commit-Position: refs/heads/master@{#630578}
-
Esmael El-Moslimany authored
paper-icon-button-light replacements: - action menu button on the bookmarks toolbar - action menu button for each bookmark entry - cr-expand-button - cr-toolbar-selection-overlay X button In cr-toolbar-search-field, the search icon button was changed from a a paper-icon-button. cr-expand-button ripple logic was changed to be consistent with other controls. The ripple is held when focused using the tab or shift+tab. The ripple stays until the control is blurred or clicked with a pointer. Bug: 736891 Change-Id: Ibe0107a096a967cb72ffef795ec983f1c28d18b2 Reviewed-on: https://chromium-review.googlesource.com/c/1436144Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Esmael El-Moslimany <aee@chromium.org> Cr-Commit-Position: refs/heads/master@{#630577}
-
Matt Menke authored
And rewrite most HttpProxyClientSocketPool tests in terms of it. The only remaining tests are for HTTP auth, client certs, socket tagging, or for cases that return a socket on failure, all of which include some aspect of testing the socket pool as well, and will be delth with in future CLs. This CL also changes type of the |respect_limits| argument to HttpProxyConnectJob to a bool, from a ClientSocketPool::RespectLimits. HttpProxyConnectJob is otherwise unchanged. The HttpProxyClientSocketPool class is going to be merged into the TransportClientSocketPool class, but we'll still need these tests. This is part of an effort to flatten the socket pools. https://docs.google.com/document/d/1g0EA4iDqaDhNXA_mq-YK3SlSX-xRkoKvZetAQqdRrxM/edit Bug: 472729 Change-Id: Ic0570a7e48ad012da793723bbecbdf04d3659586 Reviewed-on: https://chromium-review.googlesource.com/c/1446563 Commit-Queue: Matt Menke <mmenke@chromium.org> Reviewed-by:
Eric Roman <eroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#630576}
-
Nektarios Paisios authored
Exposes get_SelectionRanges and SetSelectionRanges methods on Windows for working with arbitrary selection endpoints The existing get_selection and SetSelection APIs in IAccessible2 are limited because they can only work with offsets in IA2Hypertext. This patch adds two additional APIs get_selectionRanges and SetSelectionRanges that enable working with arbitrary selection endpoints, similar to how the DOM selection API works. R=dmazzoni@chromium.org, thakis@chromium.org Bug: 916794 Change-Id: Id4db856408e4200f44ee5afa140091156d5f6adc Reviewed-on: https://chromium-review.googlesource.com/c/1385544Reviewed-by:
Nico Weber <thakis@chromium.org> Reviewed-by:
Nektarios Paisios <nektar@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: Nektarios Paisios <nektar@chromium.org> Cr-Commit-Position: refs/heads/master@{#630575}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/7fb0b73b1aa7..9686153413f3 git log 7fb0b73b1aa7..9686153413f3 --date=short --no-merges --format='%ad %ae %s' 2019-02-08 schuffelen@google.com Early exit in es2::Context::drawElements on count=0. Created with: gclient setdep -r src/third_party/swiftshader@9686153413f3 The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-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 BUG=chromium:b/123716871 TBR=swiftshader-team+autoroll@chromium.org Change-Id: I03c5d5c98ca3a42c285ae6584f6fa6bdb343ea7d Reviewed-on: https://chromium-review.googlesource.com/c/1461457Reviewed-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@{#630574}
-
Vlad Tsyrklevich authored
Change-Id: I67eb6e51a30747d6d58dd725003769aaf3b3632e Reviewed-on: https://chromium-review.googlesource.com/c/1455468 Auto-Submit: Vlad Tsyrklevich <vtsyrklevich@chromium.org> Commit-Queue: Vitaly Buka <vitalybuka@chromium.org> Reviewed-by:
Vitaly Buka <vitalybuka@chromium.org> Cr-Commit-Position: refs/heads/master@{#630573}
-
Morten Stenshorne authored
OverridePercentageResolutionBlockSize is a much better name. Change-Id: I3600fb4d7b711ec1e69991ca3bbcb671fd67e68d Reviewed-on: https://chromium-review.googlesource.com/c/1448174 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#630572}
-
Tommy C. Li authored
For the context menu for suggestions project, this adds the confirmation bubble for Remove Suggestion (from history). This bubble is not yet hooked up to anything, but is just the UI. Screenshots here: go/context-menu-for-suggestions Bug: 929477 Change-Id: I60b7c481c45bb2d1c61584961ad8f69a86e7f9b1 Reviewed-on: https://chromium-review.googlesource.com/c/1461328Reviewed-by:
manuk hovanesian <manukh@chromium.org> Commit-Queue: Tommy Li <tommycli@chromium.org> Cr-Commit-Position: refs/heads/master@{#630571}
-
Scott Violet authored
We use SetTransform() for scrolling sliding browser controls in tablet mode. BUG=930021 TEST=covered by test Change-Id: I8357b66e3feaebc6c61be00fe206cb3811a9b477 Reviewed-on: https://chromium-review.googlesource.com/c/1460113 Commit-Queue: Scott Violet <sky@chromium.org> Commit-Queue: Xiyuan Xia <xiyuan@chromium.org> Auto-Submit: Scott Violet <sky@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#630570}
-
Erik Jensen authored
https://crrev.com/c/1459634 caused rpath_link to be set unconditionally, but not used if gcc_target_rpath was set. This led to an "assignment had no effect" error. Change-Id: Ic5a2167391d49d008f78fa37fdd62bbaa3704eca Reviewed-on: https://chromium-review.googlesource.com/c/1461354Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Commit-Queue: Erik Jensen <rkjnsn@chromium.org> Cr-Commit-Position: refs/heads/master@{#630569}
-
Scott Haseley authored
Change TabLifecycleUnit to consider active --> frozen as a valid state change if initiated from the renderer. Freezing a page through ChromeDriver will trigger a renderer-initiated freeze event and cause this transition. This is necessary for wpt tests to work on DCHECK-enabled builds outside of web_tests. Bug: 930270 Change-Id: I335ba03eba6046e397c4917561c556eb72216a99 Reviewed-on: https://chromium-review.googlesource.com/c/1460433Reviewed-by:
François Doray <fdoray@chromium.org> Commit-Queue: Scott Haseley <shaseley@chromium.org> Cr-Commit-Position: refs/heads/master@{#630568}
-
Manuel Rego Casasnovas authored
As described in crbug.com/779066 even with "contain: strict" we're visiting the whole layer tree when PaintLayer::SetNeedsCompositingInputsUpdate() is called. If we call that inside an element that has "contain: strict" we should be able to avoid visiting paint layers outside that element as they are not affected. Right now we're spending a lot of time in "Update Layer Tree" phase in this situations, calling CompositingInputsUpdater::UpdateRecursive() for all the paint layers. We should be able to do something better here thanks to strict containment. The perftest is based on an attached example on the bug, it has a huge DOM with 200x200 cells that have "contain: strict". We force a call to PaintLayer::SetNeedsCompositingInputsUpdate() in one of these cells (by changing the value overflow property), and we're visiting the whole layer tree. BUG=779066 Change-Id: Iaed26bceb9a270e1989b2dc5a9dafff3d6974f39 Reviewed-on: https://chromium-review.googlesource.com/c/1458299Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Manuel Rego <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#630567}
-
Matt Menke authored
This CL merges the TransportClientSocketPool used for SOCKS proxies with the SSLSocketPool above it use for SSL tunnels over SOCKS proxies. This is part of an effort to flatten the socket pools. https://docs.google.com/document/d/1g0EA4iDqaDhNXA_mq-YK3SlSX-xRkoKvZetAQqdRrxM/edit Bug: 472729 Change-Id: I34a7b575eb7a937adabccfd13d9748edeb170e97 Reviewed-on: https://chromium-review.googlesource.com/c/1449131Reviewed-by:
Eric Roman <eroman@chromium.org> Commit-Queue: Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#630566}
-
Peng Huang authored
Bug: None Change-Id: I3b6693b4c3e6c07806da8899a0f44b46450ff9ee Reviewed-on: https://chromium-review.googlesource.com/c/1461178Reviewed-by:
Bo <boliu@chromium.org> Commit-Queue: Peng Huang <penghuang@chromium.org> Cr-Commit-Position: refs/heads/master@{#630565}
-
Jun Mukai authored
The comment says about desktop-linux but the ifdef includes ChromeOS unexpectedly. Seemingly this hiding actually resolves gotchas happening on attaching, possibly because it can exclude the window-to-disappear properly. Bug: 930004 Test: manually Change-Id: I2ee10e0cbdfc4b15c168e3c3c2c51b33d0a7b563 Reviewed-on: https://chromium-review.googlesource.com/c/1460859Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Jun Mukai <mukai@chromium.org> Cr-Commit-Position: refs/heads/master@{#630564}
-
Raul Tambre authored
The former non-overloaded variants are deprecated. This is a mechanical change; there is no intended behavior change. Bug: 929827 Change-Id: I11213229cc0b41f2f32a5545252d659ceeffe559 Reviewed-on: https://chromium-review.googlesource.com/c/1461377 Auto-Submit: Raul Tambre <raul@tambre.ee> Reviewed-by:
danakj <danakj@chromium.org> Commit-Queue: Raul Tambre <raul@tambre.ee> Cr-Commit-Position: refs/heads/master@{#630563}
-
Karan Bhatia authored
This reverts commit c8e48580. Reason for revert: The test is failing as part of non_single_process_mash_browser_tests. Original change's description: > Reenable NetworkContextConfigurationBrowserTests on ChromeOS. > > crrev.com/c/1460185 and crrev.com/c/1457478 should have fixed these > tests on ChromeOS. > > Bug: 927293 > Change-Id: I506f4f5023e431df942797c6820feb7997e514cf > Reviewed-on: https://chromium-review.googlesource.com/c/1460125 > Reviewed-by: Matt Menke <mmenke@chromium.org> > Commit-Queue: Robbie McElrath <rmcelrath@chromium.org> > Cr-Commit-Position: refs/heads/master@{#630415} TBR=mmenke@chromium.org,rmcelrath@chromium.org Change-Id: Ib68f2ead09605f798f444f02fcfbc10e699860b2 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 927293 Reviewed-on: https://chromium-review.googlesource.com/c/1461510Reviewed-by:
Karan Bhatia <karandeepb@chromium.org> Commit-Queue: Karan Bhatia <karandeepb@chromium.org> Cr-Commit-Position: refs/heads/master@{#630562}
-
Steven Bingler authored
Change-Id: I3e14d19bef87a2f91d5cb7749afbd65a1c0323a3 Reviewed-on: https://chromium-review.googlesource.com/c/1452918Reviewed-by:
Shivani Sharma <shivanisha@chromium.org> Reviewed-by:
Maks Orlovich <morlovich@chromium.org> Commit-Queue: Steven Bingler <bingler@chromium.org> Cr-Commit-Position: refs/heads/master@{#630561}
-
Tommy C. Li authored
This CL adds a context menu for suggestions. It currently only contains a "Remove suggestion..." entry to mirror the Shift+Delete behavior, but currently doesn't do anything. In the future, it will be wired to a confirm bubble. Bug: 929477 Change-Id: If12de2e04c41c4a639fd31a39a80efeac936883c Reviewed-on: https://chromium-review.googlesource.com/c/1457234 Commit-Queue: Tommy Li <tommycli@chromium.org> Reviewed-by:
manuk hovanesian <manukh@chromium.org> Cr-Commit-Position: refs/heads/master@{#630560}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/e59d40e0bcab..be39f713e530 git log e59d40e0bcab..be39f713e530 --date=short --no-merges --format='%ad %ae %s' 2019-02-08 jvanverth@google.com Add Metal context to Viewer. 2019-02-08 bsalomon@google.com Add GrContext::resetGLTextureBindings(). 2019-02-08 jvanverth@google.com Manage Mac paint events more directly. 2019-02-08 benjaminwagner@google.com Distinguish DDL in Gold results. 2019-02-08 halcanary@google.com SkQP: make text context outlast gm Created with: gclient setdep -r src/third_party/skia@be39f713e530 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 BUG=chromium:926017 TBR=fmalita@chromium.org Change-Id: Ib478b33e1cb433103301aad6a7712c86ccfec242 Reviewed-on: https://chromium-review.googlesource.com/c/1461155Reviewed-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@{#630559}
-
Mohamed Amir Yosef authored
Bug: 889819 Change-Id: I102d62cf4a8e050566a17b9796abcbc56e77ea0b Reviewed-on: https://chromium-review.googlesource.com/c/1458442 Auto-Submit: Mohamed Amir Yosef <mamir@chromium.org> Commit-Queue: Jesse Doherty <jwd@chromium.org> Reviewed-by:
Jesse Doherty <jwd@chromium.org> Cr-Commit-Position: refs/heads/master@{#630558}
-
Johannes Henkel authored
- This adds the CBOR template impl. Change-Id: Iff3854e4dda2e912518a96fd21739f0882eca544 Reviewed-on: https://chromium-review.googlesource.com/c/1461300Reviewed-by:
Pavel Feldman <pfeldman@chromium.org> Reviewed-by:
Andrey Kosyakov <caseq@chromium.org> Commit-Queue: Johannes Henkel <johannes@chromium.org> Cr-Commit-Position: refs/heads/master@{#630557}
-
Alexander Alekseev authored
This CL separates resources of oobe.html and md_login.html, so that they could be cleaned separately. Bug: 926638 Change-Id: I71708cd7e07e872d80245d77524c7920482979a7 Reviewed-on: https://chromium-review.googlesource.com/c/1455636Reviewed-by:
Jacob Dufault <jdufault@chromium.org> Commit-Queue: Alexander Alekseev <alemate@chromium.org> Cr-Commit-Position: refs/heads/master@{#630556}
-
Yuwei Huang authored
This reverts commit 0a58b6a5. Reason for revert: <INSERT REASONING HERE> Original change's description: > Reland "Add remoting FTL API key" > > This is a reland of c0cf050d > > Original change's description: > > Add remoting FTL API key > > > > Add API key for remoting to use during the signaling process. Note that > > this key is only used by Chrome Remote Desktop and will not be used in > > the Chrome browser. > > > > Internal CL: https://chrome-internal-review.googlesource.com/c/chrome/google_apis/internal/+/831973 > > > > Bug: 927962 > > Change-Id: Iecfa48aebe1078a4a0c747f42711000d9155fc3f > > Reviewed-on: https://chromium-review.googlesource.com/c/1450409 > > Reviewed-by: Joe Downing <joedow@chromium.org> > > Reviewed-by: Roger Tawa <rogerta@chromium.org> > > Auto-Submit: Yuwei Huang <yuweih@chromium.org> > > Commit-Queue: Roger Tawa <rogerta@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#630352} > > TBR=rogerta@chromium.org > > Bug: 927962 > Change-Id: I63c2e7e16621a01827609fab0c8969fd85b2399c > Reviewed-on: https://chromium-review.googlesource.com/c/1461306 > Commit-Queue: Yuwei Huang <yuweih@chromium.org> > Auto-Submit: Yuwei Huang <yuweih@chromium.org> > Reviewed-by: Joe Downing <joedow@chromium.org> > Cr-Commit-Position: refs/heads/master@{#630504} TBR=rogerta@chromium.org,joedow@chromium.org,yuweih@chromium.org Change-Id: I4711f1ae08235ab65b6c141ca4cee6e7b49c3e66 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 927962 Reviewed-on: https://chromium-review.googlesource.com/c/1461507Reviewed-by:
Yuwei Huang <yuweih@chromium.org> Commit-Queue: Yuwei Huang <yuweih@chromium.org> Cr-Commit-Position: refs/heads/master@{#630555}
-
Jordan Taylor authored
web_tests/animations/animationworklet/worklet-animation-set-keyframes.html -> web_tests/external/wpt/animation-worklet/worklet-animation-set-keyframes.https.html web_tests/animations/animationworklet/worklet-animation-set-keyframes-expected.html -> web_tests/external/wpt/animation-worklet/worklet-animation-set-keyframes-ref.html web_tests/animations/animationworklet/worklet-animation-set-timing.html -> web_tests/external/wpt/animation-worklet/worklet-animation-set-timing.https.html web_tests/animations/animationworklet/worklet-animation-set-timing-expected.html -> web_tests/external/wpt/animation-worklet/worklet-animation-set-timing-ref.html Bug: 915352 Change-Id: I95f69fcfaea64b8d779e136facb87b6f5c16c27c Reviewed-on: https://chromium-review.googlesource.com/c/1459069Reviewed-by:
Yi Gu <yigu@chromium.org> Commit-Queue: Jordan Taylor <jortaylo@microsoft.com> Cr-Commit-Position: refs/heads/master@{#630554}
-
Karan Bhatia authored
BUG=930345 TBR=achuith@chromium.org Change-Id: I980527d14f03d9f57f1f0ae9ba1206b3941189ad Reviewed-on: https://chromium-review.googlesource.com/c/1461499Reviewed-by:
Karan Bhatia <karandeepb@chromium.org> Commit-Queue: Karan Bhatia <karandeepb@chromium.org> Cr-Commit-Position: refs/heads/master@{#630553}
-
- 08 Feb, 2019 11 commits
-
-
Collin Baker authored
This implements an animated app menu button highlight when an in-product help promo is showing. A custom InkDropMask is used. Bug: 909755 Change-Id: Ib282525c8af1cdda416002641332164ba64942e5 Reviewed-on: https://chromium-review.googlesource.com/c/1450671 Commit-Queue: Collin Baker <collinbaker@chromium.org> Reviewed-by:
Peter Boström <pbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#630552}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/f256339a1959..2b0553ce59c3 git log f256339a1959..2b0553ce59c3 --date=short --no-merges --format='%ad %ae %s' 2019-02-08 jonahr@google.com Implement EXT_instanced_arrays 2019-02-08 jmadill@chromium.org Refine Ozone suppression. Created with: gclient setdep -r src/third_party/angle@2b0553ce59c3 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=geofflang@chromium.org Change-Id: I64dc2fdf02da599d30aadd5d0142fb79eb72573b Reviewed-on: https://chromium-review.googlesource.com/c/1461456Reviewed-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@{#630551}
-
Karan Bhatia authored
This reverts commit 45675d0d. Reason for revert: Speculative revert for crbug.com/930338 Original change's description: > Picture-in-Picture: move key methods into a service. > > This is moving most of the Picture-in-Picture feature into a service. > Follow-up CLs will move the remaining methods and some Android auto-pip > code. It will also include further cleanups. > > This CL was meant to be the smallest CL that could move the core feature > set without breaking compilation or tests. It's larger than expected. > > Bug: 919860, 908400 > Change-Id: I72c5faad9a14de6645a7cd1565b29d6a353e24a3 > Binary-Size: cause unknown, landing approved by agrieve@ > Reviewed-on: https://chromium-review.googlesource.com/c/1379049 > Commit-Queue: Mounir Lamouri <mlamouri@chromium.org> > Reviewed-by: Daniel Cheng <dcheng@chromium.org> > Reviewed-by: Dale Curtis <dalecurtis@chromium.org> > Reviewed-by: Jochen Eisinger <jochen@chromium.org> > Cr-Commit-Position: refs/heads/master@{#630361} TBR=dcheng@chromium.org,dalecurtis@chromium.org,beaufort.francois@gmail.com,mlamouri@chromium.org,agrieve@chromium.org,jochen@chromium.org Change-Id: I88efa31a23ab1c55b256e5813fa20fd2d8776a21 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 919860, 908400, 930338 Reviewed-on: https://chromium-review.googlesource.com/c/1461546Reviewed-by:
Karan Bhatia <karandeepb@chromium.org> Commit-Queue: Karan Bhatia <karandeepb@chromium.org> Cr-Commit-Position: refs/heads/master@{#630550}
-
Xing Liu authored
NotificationIntentInterceptorTest is flaky on kitkat, this CL enables it on post Android K versions. TBR=dtrainor@chromium.org, peter@chromium.org Bug: 910870 Change-Id: I8643bee6718dc05e73e0f62f481e9150a0f38d75 Reviewed-on: https://chromium-review.googlesource.com/c/1459520Reviewed-by:
David Trainor <dtrainor@chromium.org> Commit-Queue: Xing Liu <xingliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#630549}
-
Majid Valipour authored
Pausing worklet animation now holds the time. This works as expected for main thread animations. Implementing this for composited worklet animations will be done in a follow up patch. Major changes: - Add and expose pause() method pausing the animation. - Introduce hold_time that is used when animation is paused. - Rework how current time is computed, it is now closer to regular animations i.e., we either compute it based on "start time and timeline.currentTime" or use "hold time". - Instead of setting start time we now set the current time which then works backward to compute either the start time or the hold time based on the animation state. - When transitioning animation play state, we now always set the current time. Previously this was adhoc and inconsistent. - Introduce has_started_ to differentiate when playing an animation for the first time vs playing it from pause. - Update playback_rate related calculation to use new logic. Relanding: Original CL was reverted here [1]. Took the following steps to address this: - Address flakiness in unit test by using more accurate error value matching other tests. - Fix flakiness in layout test (worklet-animation-pause.https.html) by using startTime and waiting for time to actually advance working around pre-existing animation clock issue [2]. Also got rid of an invalid state transition from pause->idle. [1] https://chromium-review.googlesource.com/c/chromium/src/+/1434815 [2] http://crbug.com/785940 TEST: - wpt/animation-worklet/worklet-animation-pause.https.html: js test for basic current time calculations - wpt/animation-worklet/worklet-animation-pause-immediately.https.html: reftest for basic pause - wpt/animation-worklet/worklet-animation-pause-result.https.html: reftest for pause/resume. - WorkletAnimationTest.PausePlay: unit test for basic state transition and time calc Bug: 821910, Change-Id: I11fd2960443081be81055904d6d56a2abc3282f5 Reviewed-on: https://chromium-review.googlesource.com/c/1456640Reviewed-by:
Majid Valipour <majidvp@chromium.org> Reviewed-by:
Yi Gu <yigu@chromium.org> Commit-Queue: Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#630548}
-
Danan S authored
Bug: 929570 Change-Id: I027130d4301bd9d3a6c2e19f5ac56d9600c16af2 Reviewed-on: https://chromium-review.googlesource.com/c/1457920Reviewed-by:
Dan Erat <derat@chromium.org> Commit-Queue: Danan S <danan@chromium.org> Cr-Commit-Position: refs/heads/master@{#630547}
-
Jeff Fisher authored
Adds a new test for DOMDebugger.setInstrumentationBreakpoint Change-Id: Icb420733979c8ba3dad0aafd33b8c8cb744cae45 Reviewed-on: https://chromium-review.googlesource.com/c/1461340Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Jeff Fisher <jeffish@microsoft.com> Cr-Commit-Position: refs/heads/master@{#630546}
-
Tibor Goldschwendt authored
Having all translations for webview strings in the base module breaks the use of current_detected_ui_locale_name as an indicator for the current UI language. To fix this, move current_detected_ui_locale_name into Chrome resources and, thus, prevent its translations being added to base. Furthermore, use the fixed current_detected_ui_locale_name to record via UMA whether Chrome resumes in the wrong language. I.e. we support the current system language but Chrome is not displayed in it. That can happen if the user changes the language but the language split is not installed in time. Bug: 906082 Change-Id: I084220643e864329360463ef47e84e8632fc6f24 Reviewed-on: https://chromium-review.googlesource.com/c/1460176 Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Commit-Queue: David Trainor <dtrainor@chromium.org> Reviewed-by:
Jesse Doherty <jwd@chromium.org> Reviewed-by:
David Trainor <dtrainor@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Auto-Submit: Tibor Goldschwendt <tiborg@chromium.org> Cr-Commit-Position: refs/heads/master@{#630545}
-
Khushal authored
Once a tile is done rasterizing, we inform the layer associated with the tile. In the case of pending layer tiles, no additional damage needs to be added from this update, since it is already accounted for in the invalidation on the pending layer which contributes to this layer's overall damage. However, on the active tree, where this raster may be for content previously checkerboarded and its update will be driven by cc, we ensure that the damage from this update is added to this layer's damage at this step. The complete tile's area is assumed to be damaged. Currently LayerTreeHostImpl dispatches the notification for tile raster complete to both the twin (active and pending) layers. This was creating a scenario where when an update which partially invalidates a tile is received on the pending tree, the notification for its raster finishing was being processed by its active and pending layer. The active layer would then damage the complete tile, and the frame damage would unnecessarily include this full tile damage instead of the partial invalidation receieved on the pending tree. Fix the above by routing the tile raster finished notification to only the layer that tile belongs to. Note that this means that if a pending tile finishes after activation, we might still be doing additional damage. But since we only activate after all visible content has been rasterized, those pending tiles are likely not visible anyway. R=danakj@chromium.org,enne@chromium.org Change-Id: I721480af0d7ea3889ef1de2bd5bbee693062f671 Reviewed-on: https://chromium-review.googlesource.com/c/1460181Reviewed-by:
enne <enne@chromium.org> Commit-Queue: Khushal <khushalsagar@chromium.org> Auto-Submit: Khushal <khushalsagar@chromium.org> Cr-Commit-Position: refs/heads/master@{#630544}
-
Vlad Tsyrklevich authored
When GWP-ASan is enabled with use_allocator_shim=false (e.g. Windows component builds) it prints a diagnostic warning. Only enable GWP-ASan if it can actually be initialized to avoid printing unnecessary warnings. This means we can't use enable_gwp_asan to enable running tests, as the tests already test for use_allocator_shim=true when necessary. Bug: 929878 Change-Id: I4a8aaaca80c0185fd1c5e07bd7692437665407d3 Reviewed-on: https://chromium-review.googlesource.com/c/1460192 Auto-Submit: Vlad Tsyrklevich <vtsyrklevich@chromium.org> Commit-Queue: Vitaly Buka <vitalybuka@chromium.org> Reviewed-by:
Vitaly Buka <vitalybuka@chromium.org> Cr-Commit-Position: refs/heads/master@{#630543}
-
Raul Tambre authored
The former non-overloaded variants are deprecated. Removed casts where they are now unnecessary. This is a mechanical change; there is no intended behavior change. Bug: 929827 Change-Id: Ib064163c5cbdc2a1d596ec26457eb0f41e0d39c2 Reviewed-on: https://chromium-review.googlesource.com/c/1461129 Commit-Queue: Raul Tambre <raul@tambre.ee> Commit-Queue: John Budorick <jbudorick@chromium.org> Auto-Submit: Raul Tambre <raul@tambre.ee> Reviewed-by:
John Budorick <jbudorick@chromium.org> Cr-Commit-Position: refs/heads/master@{#630542}
-