From ce565f4832c01cc3b2ddd6c401a65e1f5312b46a Mon Sep 17 00:00:00 2001 From: semantic-release-bot Date: Mon, 16 Dec 2019 16:55:26 +0000 Subject: [PATCH] chore(release): 8.0.0 [skip ci] # [8.0.0](https://github.com/react-native-community/react-native-webview/compare/v7.6.0...v8.0.0) (2019-12-16) ### Features * **ios:** Generate history API events on iOS ([#1082](https://github.com/react-native-community/react-native-webview/issues/1082)) ([3615296](https://github.com/react-native-community/react-native-webview/commit/3615296)) ### BREAKING CHANGES * **ios:** if you use onNavigationStateChange on iOS it will now trigger on # changes to the url. * Hook the `window.history` API on iOS to generate events The underlying WKWebView doesn't seem to generate any events in response to the `window.history` API - none of the `WKNavigationDelegate` methods fire. Given this limitation, the only way to know when the location changes via this API is to inject Javascript into the page and have it notify the native code directly when any of these functions are called. The `setTimeout` call gives up the current tick, allowing the location to change before firing the event. * Remove the outdated section about hash changes Now that this bug is fixed, the workaround is no longer required. --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 73863f0..727cdaf 100644 --- a/package.json +++ b/package.json @@ -8,7 +8,7 @@ "Thibault Malbranche " ], "license": "MIT", - "version": "7.6.0", + "version": "8.0.0", "homepage": "https://github.com/react-native-community/react-native-webview#readme", "scripts": { "ci": "CI=true && yarn lint && yarn test",