Fixed
Status Update
No update yet.
Comments
ap...@google.com
Please include a sample project that reproduces your issue.
il...@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?
Description
Component used: Fragment Version used: 1.4.0-alpha01
Developers can decide what type of penalties they would like Fragment StrictMode to output, from
penaltyLog()topenaltyDeath(). However, if developers have specifically enabled debug logging viaFragmentManager.enableDebugLogging(true)or via theadb shell setprop log.tag.FragmentManager VERBOSE(orDEBUG), we should always output every violation to logcat with theFragmentManager.TAGasLog.d(), no matter what policy is used.This is ensure that debug logging will inform those debugging Fragments of potential issues that may affect the behavior of Fragments.
The internal helper of
FragmentManager.isLoggingEnabled(Log.DEBUG)can be used to determine whether we should output these debug log violations. This output should happen before any FragmentStrictMode policy specific logging/listeners/death. IfpenaltyLog()is used and you're debug logging, both log messages should appear (they should be independent from one another).