Status Update
Comments
de...@gmail.com <de...@gmail.com> #3
Thanks for the report!
jo...@google.com <jo...@google.com> #4
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 style = LocalTextStyle.current.copy(lineHeight = TextUnit.Unspecified)
, or create a custom Typography
entirely.
jo...@google.com <jo...@google.com>
de...@gmail.com <de...@gmail.com> #5
sy...@gmail.com <sy...@gmail.com> #6
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>
se...@google.com <se...@google.com>
gl...@gmail.com <gl...@gmail.com> #7
se...@google.com <se...@google.com> #8
In progress : )
ma...@quantox.com <ma...@quantox.com> #9
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> #10
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
se...@google.com <se...@google.com> #11
@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.
de...@gmail.com <de...@gmail.com> #12
@se...@google.com maybe not so good to post the full mail here?
na...@google.com <na...@google.com> #13
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
Description
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 .