Fixed
Status Update
No update yet.
Comments
il...@google.com
Please include a sample project that reproduces your issue.
il...@google.com
ap...@google.com
Here is the sample project.
Steps to reproduce:
1. Press on "Search" icon;
2. Write something;
3. Search this text, keyboard will be dismissed;
4. Tap on "Dialog" button;
5. Dissmiss dialog;
With the new 1.5.0 fragment library version text will be cleared in the search box after dismissing dialog.
In the version 1.4.1 and lower text in the search is not clearing and this is correct behaviour.
Please suggest some workarounds or how to fix this issue?
Steps to reproduce:
1. Press on "Search" icon;
2. Write something;
3. Search this text, keyboard will be dismissed;
4. Tap on "Dialog" button;
5. Dissmiss dialog;
With the new 1.5.0 fragment library version text will be cleared in the search box after dismissing dialog.
In the version 1.4.1 and lower text in the search is not clearing and this is correct behaviour.
Please suggest some workarounds or how to fix this issue?
il...@google.com
Hello, have you checked sample project? I hope it will help find the issue.
Description
Version used: 1.1.0-alpha02
We have postponeEnterTransition() to mark that a fragment transition should be postponed, but you usually have to do something like the following to ensure that we don't sit there postponed forever:
var postponed = false
override fun postponeEnterTransition() {
super.postponeEnterTransition()
postponed = true
}
override fun onStart() {
super.onStart()
if (postponed && !startedTransition) {
// We're postponed and haven't started a transition yet, we'll delay for a max of 2000ms
view?.postDelayed(::scheduleStartPostponedTransitions, 2000)
}
}
It would be nice if isPostponed() was made public rather than relying on my flag.