diff options
author | zachh <zachh@google.com> | 2017-08-25 16:11:00 -0700 |
---|---|---|
committer | Eric Erfanian <erfanian@google.com> | 2017-08-30 23:27:58 +0000 |
commit | 196e3fe631a3c7a0073273b41e76387d01ed3baf (patch) | |
tree | a93deda491a7cf62949d44a0aaa1cad535c673d5 /java/com/android/dialer/searchfragment | |
parent | 51f2b28ae6a45f57f94e5c9a66081a10aebc8349 (diff) |
Moved new call log fragment to NUI.
I have removed the flag for rolling out the feature and now just rely on the mechanism which enables NUI.
The annotated call log is built when a user views the new call log for the first time using the NUI activity. However, new call log content observers may now be registered before that if the user has a bugfood/debug build. (Previously observers were enabled based on the presence of a phenotype flag which has now been deleted.)
Moving it to NUI involved converting it to a support fragment.
Finally, I temporarily modified the espresso test to target the old call log; it can't work in the NUI until we implement dialing, clearing call history, deleting entries, etc. I considered keeping the new fragment in Dialtacts activity but that wouldn't work because it requires app.Fragments. I'll port the espresso test as soon as is feasible and for now we at least have better coverage for the old call log.
Bug: 34672501
Test: none
PiperOrigin-RevId: 166538972
Change-Id: I7782b93aaf6ad0719f5b9f763fa4752cf5d8ce68
Diffstat (limited to 'java/com/android/dialer/searchfragment')
0 files changed, 0 insertions, 0 deletions