Fix: OnNavigationStateChanged not always called #551
Closed
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.
The
OnNavigationStateChanged
Prop of react-native-community-webview is not called when the history state is manipulated via javascript (e.g.:window.history.pushState({test: "test"}, "Test Title", "index.html")
).With this pull request each history change will be noticed by the native webviews (android and ios) and the navigation change will be forwarded to
onNavigationStateChanged
withnavigationType: "other"
.