[composable toolbar] Bottom toolbar not seen when starting search on home from cold start
Categories
(Firefox for Android :: Toolbar, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox142 | --- | unaffected |
| firefox143 | --- | unaffected |
| firefox144 | --- | fixed |
People
(Reporter: petru, Assigned: petru)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression, Whiteboard: [fxdroid][group3][composable toolbar])
Attachments
(2 files)
Steps to reproduce
- Have the toolbar position set to the bottom of the screen
- Have no tabs open to ensure cold start shows the home screen
- Cold start the application
- Tap on the toolbar to start search
Expected behaviour
The software keyboard appears and the toolbar is on top of it (y axis)
Actual behaviour
The software keyboard appears but the toolbar is underneath it (z axis)
Any additional information?
Only happens with cold starts, doing anything else, starting search from home after coming from other screens doesn't exhibit the issue.
Used git bisect to find that this is a regression after updating to the new Jetpack Compose version.
Does not happen after cold starts on browser and starting a search here for search terms, happens only on searches started from home.
Does not happen with the old toolbar.
Does not happen on Android 8 so different behaviour depending on Android versions show that whatever was changed is definitely buggy.
Comment 1•11 months ago
|
||
Set release status flags based on info from the regressing bug 1983174
:RyanVM, since you are the author of the regressor, bug 1983174, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Updated•11 months ago
|
| Assignee | ||
Updated•11 months ago
|
Updated•11 months ago
|
| Assignee | ||
Comment 2•11 months ago
|
||
Added a few more bits of information.
Given the very specific scenario in which this happens and other similar scenarios in which it doesn't I think we can find a workaround.
| Assignee | ||
Comment 3•11 months ago
|
||
Investigations showed that insets listeners were not called in this scenario but
using a View instead of the newly built ComposeView restores the behavior we had.
Comment 5•11 months ago
|
||
| bugherder | ||
Description
•