experimental implementation of page stack#83
Open
drunkhacker wants to merge 1 commit into
Open
Conversation
|
Niveau approach, you should Limit the Stack in Order to prevent memory wasting |
|
Nice approach I mean :) |
Author
|
@wzr1337 Thank you. I found that angular ui provides similar stack structure in |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I had difficulty of losing any dynamic content after new page is pushed. Because this library doesn't manage pages with stack, it simply replace
mobile-viewwith new page.By adding simple array variable containing pushed DOM information, now we can remember all the pages pushed in this navigation bar.
I know this implementation is creepy and buggy, but hope it'll inspire other guys to improve this structure. Thanks.