Handling of Randomly changing dynamic element id, cookie/cache synchronization and visibility settings #1159
Conversation
This file contains 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
Updating cookie , cache changes also
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
HI All,
In these commits I have made few changes which are actually required for handling :
Randomly changing element id in DOM tree for dynamic elements. The ID field is quintessential for executing actions on remote side.
Apart from session storage I have also added coockie and cache synchronization to allow people to take advantage of logged -in user cobrowsing.
Also added support for changing visibility of any element like show or hide.
Fixed few bugs like in case of hash change detection currentUrl wasn't properly getting updated and during documentClick removed setTimeout to make it synchronous.