This is unreleased documentation for React Native Next version.
For up-to-date documentation, see the latest version (0.63).
Version: Next
Custom WebView
While the built-in web view has a lot of features, it is not possible to handle every use-case in React Native. You can, however, extend the web view with native code without forking React Native or duplicating all the existing web view code.
Before you do this, you should be familiar with the concepts in native UI components. You should also familiarise yourself with the native code for web views, as you will have to use this as a reference when implementing new features—although a deep understanding is not required.
To get started, you'll need to create a subclass of ReactWebViewManager, ReactWebView, and ReactWebViewClient. In your view manager, you'll then need to override:
You can trigger the event in your web view client. You can hook existing handlers if your events are based on them.
You should refer to ReactWebViewManager.java in the React Native codebase to see what handlers are available and how they are implemented. You can extend any methods here to provide extra functionality.
Finally, you'll need to expose the events in CustomWebViewManager through getExportedCustomDirectEventTypeConstants. Note that currently, the default implementation returns null, but this may change in the future.
To use your custom web view, you'll need to create a class for it. Your class must:
Export all the prop types from WebView.propTypes
Return a WebView component with the prop nativeConfig.component set to your native component (see below)
To get your native component, you must use requireNativeComponent: the same as for regular custom components. However, you must pass in an extra third argument, WebView.extraNativeComponentConfig. This third argument contains prop types that are only required for native code.
If you want to add custom props to your native component, you can use nativeConfig.props on the web view.
For events, the event handler must always be set to a function. This means it isn't safe to use the event handler directly from this.props, as the user might not have provided one. The standard approach is to create a event handler in your class, and then invoking the event handler given in this.props if it exists.
If you are unsure how something should be implemented from the JS side, look at WebView.android.js in the React Native source.
Similar to regular native components, you must provide all your prop types in the component to have them forwarded on to the native component. However, if you have some prop types that are only used internally in component, you can add them to the nativeOnly property of the third argument previously mentioned. For event handlers, you have to use the value true instead of a regular prop type.
For example, if you wanted to add an internal event handler called onScrollToBottom, you would use,