You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 2, 2024. It is now read-only.
Is there a StackOverflow question about this issue?
I have searched StackOverflow
Is this an issue related to the sample app?
Yes, this is a specific issue related to this samples repo.
What happened?
When scrolling on the PlantDetails screen, an issue has been observed where the "Add" button does not disappear when the associated image collapses. This behavior creates a visual inconsistency and affects the overall user experience.
Video to explain the bug 👇🏻
Screen.Recording.2023-06-30.at.2.15.03.PM.mov
Steps to Reproduce:
Navigate to the PlantDetails screen.
Scroll down the screen until the associated image starts collapsing.
Observe that the "Add" button remains visible even when the image collapses.
Expected Behavior:
The "Add" button should disappear when the associated image collapses during scrolling on the PlantDetails screen. This behavior ensures a consistent and aesthetically pleasing user interface.
Is there an existing issue for this?
Is there a StackOverflow question about this issue?
Is this an issue related to the sample app?
What happened?
When scrolling on the PlantDetails screen, an issue has been observed where the "Add" button does not disappear when the associated image collapses. This behavior creates a visual inconsistency and affects the overall user experience.
Video to explain the bug 👇🏻
Screen.Recording.2023-06-30.at.2.15.03.PM.mov
Steps to Reproduce:
Expected Behavior:
The "Add" button should disappear when the associated image collapses during scrolling on the PlantDetails screen. This behavior ensures a consistent and aesthetically pleasing user interface.
Part of GTC open source initiative
Relevant logcat output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: