## [10.9.2](https://github.com/react-native-community/react-native-webview/compare/v10.9.1...v10.9.2) (2020-10-05)

### Bug Fixes

* **macOS:** Don't include iOS pull-to-refresh control ([#1636](https://github.com/react-native-community/react-native-webview/issues/1636)) ([dbf4659](dbf46593fa/))
* **podspec:** Lowered deployment target for MacOS to 10.13 ([#1673](https://github.com/react-native-community/react-native-webview/issues/1673)) ([f204195](f2041955a2/))

* Update RNCWebView.h

Limit methods relating to pull to refresh to only iOS

* Update RNCWebView.m

Block methods relating to pull to refresh when the target is macOS as macOS does not have the UIRefreshControl

Co-authored-by: Eloy Durán <eloy.de.enige@gmail.com>

## [10.9.1](https://github.com/react-native-community/react-native-webview/compare/v10.9.0...v10.9.1) (2020-09-29)

### Bug Fixes

* **ios:** Xcode 12 compatibility ([#1643](https://github.com/react-native-community/react-native-webview/issues/1643)) ([08b7099](08b709967f/))

* fix: add React-Core to podspec for Xcode 12 compatibility

https://github.com/facebook/react-native/issues/29633

* chore: remove React dependency

[skip ci]

# [10.9.0](https://github.com/react-native-community/react-native-webview/compare/v10.8.3...v10.9.0) (2020-09-15)

### Features

* **iOS:** Add prop autoManageStatusBarEnabled ([#914](https://github.com/react-native-community/react-native-webview/issues/914)) ([22a60fd](22a60fd23a/))

Co-authored-by: Jamon Holmgren <jamon@infinite.red>
Co-authored-by: Jamon Holmgren <jamonholmgren@gmail.com>
Co-authored-by: Thibault Malbranche <thibault.malbranche@epitech.eu>

Co-authored-by: iou90kant <dekang.liu@guokr.com>

## [10.8.3](https://github.com/react-native-community/react-native-webview/compare/v10.8.2...v10.8.3) (2020-08-31)

### Bug Fixes

* **types:** Update Typescript definition file ([#1597](https://github.com/react-native-community/react-native-webview/issues/1597)) ([9dcd108](9dcd108b1f/))

This solves a class of issues when the WebView loses "context"
that a subsequent page load is the same as what was attempted
to be loaded previously. This solves a bug where a HTTP redirect
in combination with history manipulations causes a user to be
stuck and prevented from going back. Since WebView requests are
allowed to happen normally, debugging the WebView and tracking
redirects and page load initiators is more accurate and easier.
This will also bypass bridge latency and provide a faster navigation.

To do this, we must lock in the shouldOverrideUrlLoading callback
and send an event to JS. Currently, this callback is ran on
the main UI thread, of which we have no control over. This is
problematic as using the bridge in most ways seems to require
the main UI thread, which will cause a deadlock. However, using
BatchedBridge for Java->JS and a synchronous method for JS->Java
doesn't cause any problems. Additionally, it's been designed so
that if WebView suddenly runs the callback on a different thread
allowing for concurrency, it will continue to work.

## [10.8.2](https://github.com/react-native-community/react-native-webview/compare/v10.8.1...v10.8.2) (2020-08-25)

### Bug Fixes

* **deps:** Update package.json ([#1583](https://github.com/react-native-community/react-native-webview/issues/1583)) ([8dd9969](8dd9969288/))

* Update package.json

* Remove react version from peerDependencies

* Update package.json

Co-authored-by: Thibault Malbranche <thibault.malbranche@epitech.eu>

## [10.8.1](https://github.com/react-native-community/react-native-webview/compare/v10.8.0...v10.8.1) (2020-08-25)

### Bug Fixes

* **iOS:** changed the way the top view controller is obtained. ([#1592](https://github.com/react-native-community/react-native-webview/issues/1592)) ([2cb2113](2cb2113c29/))
* **ts:** Convert ContentInsetAdjustmentBehavior from an enum back to a string union type ([#1536](https://github.com/react-native-community/react-native-webview/issues/1536)) ([a48c981](a48c9819c5/))

ContentInsetAdjustmentBehavior was originally added as a string union type. The change to support MacOS replaced it with an enum, which was a bit of a breaking change, especially as the enum was not exported from the main library. Exporting the enum would probably also help, but since this was the only enum and the rest of react-native-webview uses string unions instead, it seems best to revert it to a string union.

Co-authored-by: Jamon Holmgren <jamonholmgren@gmail.com>

Co-authored-by: Cristiano Coelho <cristianocca@hotmail.com>

https://github.com/react-native-community/react-native-webview/issues/1554

# [10.8.0](https://github.com/react-native-community/react-native-webview/compare/v10.7.0...v10.8.0) (2020-08-24)

### Features

* **android:** Add androidLayerType as prop ([#1588](https://github.com/react-native-community/react-native-webview/issues/1588)) ([9ffca8f](9ffca8f9db/))

* Add androidLayerType as a prop

* Deprecate "androidHardwareAccelerationDisabled" prop

* Update reference

Co-authored-by: Olivia Caraiman <olcaraim@microsoft.com>

# [10.7.0](https://github.com/react-native-community/react-native-webview/compare/v10.6.0...v10.7.0) (2020-08-17)

### Features

* **iOS:** Add the pull to refresh ([#1265](https://github.com/react-native-community/react-native-webview/issues/1265)) ([a02d88f](a02d88f54f/))

* Add pull to refresh support for iOS

* Add pull to refresh control removal from WebView

* Add the type and reference description about pull to refresh

* Set bounces to true when enabling pull to refresh, add references

* Add the back to props anchor to pullToRefreshEnabled

# [10.6.0](https://github.com/react-native-community/react-native-webview/compare/v10.5.0...v10.6.0) (2020-08-15)

### Features

* **events:** Add isTopFrame to shouldStartLoadForRequest ([#1537](https://github.com/react-native-community/react-native-webview/issues/1537)) ([6a9116f](6a9116f2d1/))