[Feature Request] SwipeToDismiss for Material 3 [242889540]

Fixed

Bug

Status Update

No update yet.

Description

de...@gmail.com

created issue #1

Aug 17, 2022 07:18PM

Feature Request to add SwipeToDismiss to Compose for Material 3, as it is not recommended to use material components in a Material 3 project according to this ticket.

Comments

ra...@gmail.com <ra...@gmail.com> #2Aug 26, 2022 09:56AM

There is a report about it in kotlinlang Slack: https://kotlinlang.slack.com/archives/C01D6HTPATV/p1706005056105739

de...@gmail.com <de...@gmail.com> #3Oct 8, 2022 06:29PM

Thanks for the report!

jo...@google.com <jo...@google.com> #4Oct 10, 2022 06:54AM

The release notes documentation has been edited to clarify this change in behavior for line height.

To support non-standard text sizes, we encourage users to follow the Material design system and use a different type scale rather than changing the font size directly. Alternatively, users can overwrite the line height like so: style = LocalTextStyle.current.copy(lineHeight = TextUnit.Unspecified), or create a custom Typography entirely.

jo...@google.com <jo...@google.com> Oct 10, 2022 08:11AM

Reassigned to se...@google.com.

de...@gmail.com <de...@gmail.com> #5Oct 10, 2022 09:50AM

deleted

sy...@gmail.com <sy...@gmail.com> #6Oct 13, 2022 06:43AM

In my case, I have multiple font sizes in the same Text (using SpanStyle in AnnotatedString). There are legitimate reasons for this. For example, when combining Chinese and English (phonetic) together (for language-learning purposes).

se...@google.com <se...@google.com> Oct 18, 2022 06:35PM

Assigned to se...@google.com.

se...@google.com <se...@google.com> Oct 21, 2022 05:13PM

Accepted by se...@google.com.

gl...@gmail.com <gl...@gmail.com> #7Nov 3, 2022 10:19PM

⌛ Waiting...

se...@google.com <se...@google.com> #8Nov 8, 2022 03:27PM

In progress : )

ma...@quantox.com <ma...@quantox.com> #9Dec 2, 2022 09:28AM

Question for Google devs: I see Pull-To-Refresh component has been added to Material2 but NOT Material3, so I'm wondering what is an actual priority and future development plan for these 2 libraries? As someone who started a project on Material3, and already missing both BottomSheet and now a Pull-To-Refresh component, I'm really second guessing my choices and wondering if even future projects should be started on Material3, since even NEW stuff is being implemented on Material2..

So the question is, should we actually be starting new projects on Material3 or not? It's even "final" now. And is it really more future proof from the project maintenance perspective?

ap...@google.com <ap...@google.com> #10Dec 5, 2022 01:44PM

Project: platform/frameworks/support
Branch: androidx-main

commit e6892a2153fca43e348b0de7c2614e7bf6cbc708
Author: José Figueroa <serniebanders@google.com>
Date: Tue Nov 01 10:38:11 2022

[Material3][SwipeToDismiss] Update Swipe To Dismiss to M3 library

Updates:
* Threshold calculation simplified and moved to DismissState.
* SwipeableState inheritance moved internally, with relevant parameters exposed to DismissState API.
* Splits more complex demo and simple sample code logic.

Test: Forked M2 Unit Tests
Bug: 242889540
RelNote: Implement SwipeToDismiss in Material 3 library.
Change-Id: I458a8e1359896712a2a8aede43e0283977be4601

M compose/material3/material3/api/current.txt
M compose/material3/material3/api/public_plus_experimental_current.txt
M compose/material3/material3/api/restricted_current.txt
M compose/material3/material3/integration-tests/material3-demos/src/main/java/androidx/compose/material3/demos/Material3Demos.kt
A compose/material3/material3/integration-tests/material3-demos/src/main/java/androidx/compose/material3/demos/SwipeToDismissDemo.kt
M compose/material3/material3/samples/src/main/java/androidx/compose/material3/samples/SwipeToDismissSamples.kt
M compose/material3/material3/src/androidAndroidTest/kotlin/androidx/compose/material3/SwipeToDismissTest.kt
M compose/material3/material3/src/commonMain/kotlin/androidx/compose/material3/SwipeToDismiss.kt

https://android-review.googlesource.com/2282010

se...@google.com <se...@google.com> #11Dec 5, 2022 01:58PM

Marked as fixed.

@marko I can't speak to the PullToRefresh feature as I've not worked on it, but to generally answer your question: I would say that is ultimately your call to make. Personally I would recommend using Material3, as it has a longer window of active development (feature requests, bug fixes, other dev time resources) while the goal is to sunset M2 support over time. However M2 is of course more feature complete at this time.

PullToRefresh is not currently on the M3 radar however you are welcome to file a feature request.

Message last modified on Dec 5, 2022 02:28PM

de...@gmail.com <de...@gmail.com> #12Dec 5, 2022 02:15PM

@se...@google.com maybe not so good to post the full mail here?

na...@google.com <na...@google.com> #13Jan 11, 2023 08:12PM

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.compose.material3:material3:1.1.0-alpha04