Fixed
Status Update
Comments
il...@google.com <il...@google.com>
ap...@google.com <ap...@google.com> #2
Can you rise priority please?
It's a real stopper to use in not helloworld apps.
It must be joke, define it as "An issue that should be addressed eventually. Such an issue is not relevant to core organizational functions or the work of other teams, or else it relates only to the attractiveness or pleasantness of the system."
Why use compose in production, if this base things resolved for years?
It's a real stopper to use in not helloworld apps.
It must be joke, define it as "An issue that should be addressed eventually. Such an issue is not relevant to core organizational functions or the work of other teams, or else it relates only to the attractiveness or pleasantness of the system."
Why use compose in production, if this base things resolved for years?
jb...@google.com <jb...@google.com> #3
This is high priority for us. The "Priority" field on buganizer is misleading, it has a very specific internal meaning and interaction with other systems so we don't use it for actual prioritization for compose text issues. Unfortunately, the way we track actual priority is not visible externally.
Description
Component used: Fragment
Version used:1.3.0-alpha03 up to 1.3.0-alpha05
Devices/Android versions reproduced on: any
Sample code:https://gist.github.com/amihusb/7f2b38904d6245eb1c70064cb3ca6fd4
This is happening because Dialog#onRestoreInstanceState now gets called in DialogFragment#onViewStateRestored and child fragments gets restored their views before parent fragment, dialog restoring its own state and call show() before the parent dialog