Status Update
No update yet.
Comments
am...@gmail.com
Project: platform/frameworks/support
Branch: androidx-main
Author: Louis Pullen-Freilich <
Link:
Adds OverscrollEffect#withoutDrawing and OverscrollEffect#withoutEventHandling
Expand for full commit details
Adds OverscrollEffect#withoutDrawing and OverscrollEffect#withoutEventHandling
These APIs allow overscroll to have events dispatched to it by one component, and rendered in a separate component.
Fixes: b/266550551
Fixes: b/204650733
Fixes: b/255554340
Fixes: b/229537244
Test: OverscrollTest
Relnote: "Adds OverscrollEffect#withoutDrawing and OverscrollEffect#withoutEventHandling APIs - these APIs create a wrapped instance of the provided overscroll effect that doesn't draw / handle events respectively, which allows for rendering overscroll in a separate component from the component that is dispatching events. For example, disabling drawing the overscroll inside a lazy list, and then drawing the overscroll separately on top / elsewhere."
Change-Id: Idbb3d91546b49c1987a041f959bce4b2b09a9f61
Files:
- M
compose/foundation/foundation/api/current.txt - M
compose/foundation/foundation/api/restricted_current.txt - M
compose/foundation/foundation/integration-tests/foundation-demos/src/main/java/androidx/compose/foundation/demos/OverscrollDemo.kt - M
compose/foundation/foundation/samples/src/main/java/androidx/compose/foundation/samples/OverscrollSample.kt - M
compose/foundation/foundation/src/androidInstrumentedTest/kotlin/androidx/compose/foundation/OverscrollTest.kt - M
compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/Overscroll.kt
Hash: f64e25b7a473c757d080521e7dd97b3f6670f60d
Date: Fri Nov 01 18:43:56 2024
am...@gmail.com
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.compose.foundation:foundation:1.8.0-alpha06androidx.compose.foundation:foundation-android:1.8.0-alpha06androidx.compose.foundation:foundation-jvmstubs:1.8.0-alpha06androidx.compose.foundation:foundation-linuxx64stubs:1.8.0-alpha06
am...@gmail.com
Hi, it's been 9 months since I reported this. We are now on 1.2.0-beta01 of Material 3. Still no variant provided.
ap...@google.com
Branch: androidx-main
commit 040e3103bc0cfb65b085ec7401e5f4aee7b2f893
Author: Max Alfonso-Ying <maxying@google.com>
Date: Wed Mar 27 17:36:06 2024
Make SearchBar take input field as a slot
- SearchBarInputField moved into SearchBarDefaults and made public
- Deprecated SearchBarColors inputFieldColors param
- renamed "active" to "expanded" in new API to better align with spec language
Bug:
Fixes:
Relnote: "`SearchBar` and `DockedSearchBar` have new overloads that
take a text field parameter. This allows styling the text field
separately from the rest of the search bar as well as passing in
custom text fields. The text field of the current implementation
has been made available as `SearchBarDefaults.InputField`."
Test: tests updated
Change-Id: I50c73509b4a67247df7240207e7ad13d5863a7ff
M compose/material3/benchmark/src/androidTest/java/androidx/compose/material3/benchmark/SearchBarBenchmark.kt
M compose/material3/material3/api/current.txt
M compose/material3/material3/api/restricted_current.txt
M compose/material3/material3/samples/src/main/java/androidx/compose/material3/samples/SearchBarSamples.kt
M compose/material3/material3/src/androidInstrumentedTest/kotlin/androidx/compose/material3/SearchBarScreenshotTest.kt
M compose/material3/material3/src/androidInstrumentedTest/kotlin/androidx/compose/material3/SearchBarTest.kt
M compose/material3/material3/src/androidMain/kotlin/androidx/compose/material3/SearchBar.android.kt
ma...@google.com
A change was made to SearchBar that allows passing the text field as a parameter, so you can use a custom text field that supports TextFieldValue. This should be available in the next 1-2 alpha releases of the library.
However, the reason we have not (and will not) add a TextFieldValue version of SearchBar in the library is because BasicTextField has been undergoing a rewrite. Once the new version is fully stable, we will add support to SearchBar that uses the new TextFieldState API, which supports selection and cursor position and can replace the use case of TextFieldValue. If interested, you can follow this thread:
na...@google.com
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.compose.material3:material3:1.3.0-alpha05androidx.compose.material3:material3-android:1.3.0-alpha05androidx.compose.material3:material3-desktop:1.3.0-alpha05
Description
Jetpack Compose Material 3 version: 1.1.0-beta02
Jetpack Compose component used: androidx.compose.material3.SearchBar
Android Studio Build: #AI-222.4459.24.2221.9862592
Kotlin version: 1.8.20
Currently the query parameter of SearchBar component is only String, there is no TextFieldValue variant which would allow us to control the selection, etc.