LibWeb: Initial steps towards implementing NavigationActivation #1808
+159
−16
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 gets the bulk of the implementation prepared for NavigationActivation. Unfortunately, it isn't working fully at this stage due to what appear to be spec bugs - and also some of our own!
The first issue is a simple editorial one whatwg/html#10703 - which I saw now after seeing that wehave not been passing through "displayedEntry" to "update_for_history_step_application":
ladybird/Userland/Libraries/LibWeb/HTML/TraversableNavigable.cpp
Line 756 in 7a92b47
Unfortunately, even after doing a local patch for that, we then run into a crash due to document() being null on the "previousEntry" inside of "update_for_history_step_application", which I am still trying to figure out. It is maybe possible the issue is related to whatwg/html#9869 - it could also simply be a bug in our code somewhere - but my understanding is still very much lacking in this area to have narrowed this down at all. Ideas appreciated for what might be going wrong!