Closed harshitagupta30 closed 7 years ago
Sorry I missed this earlier. Will go through the code and let you know.
Yeah. This should be fixed. You can send a PR.
I also wanted to know that why are we backtracing the fragments in the stack in the app? Is there any special reason for that? Since we've limited memory and in almost all apps we don't do this.
If you have any more suggestions, please open up a separate issue and then let's discuss that there. Please include the issue/enhancement (better with a specific example). If you can please add your suggested fix as well. Do this as a best practice.
Apologies and thanks for letting know! :) I'll make a new issue stating the entire scenario.
@sandarumk I have figured out a solution to solve the bug Should I send a PR?
@harshitagupta30 is already working on this. Please pick an issue not assigned to anyone else.
fixed via #378
Actual Behaviour
Expected Behaviour On clicking the same fragment it should not change.
@sandarumk I would like to work on it.