history.js: Properly handle data attributes upon navigation #4752
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.
This is required so that attributes like
data-icinga-container-id
are properly managed if the user navigates using the history buttons. Previously these were not managed at all asapplyLocationBar
didn't made use of ui.js' capabilities to paste/cut/move contents.I've rewritten
applyLocationBar
basically. It now also just moves a column if only the location has changed, not the url.I will add a comment with test-cases the next days.