renderersProps.a.onPress, see Stack Overflow | How to open the browser when a link is pressed? and
You can define custom renderers for that purpose. See Custom Rendering.
That's really a piece of cake. See @native-html/iframe-plugin.
You should use
See this example from the docs: Example: Displaying Inline Images.
However, the end-user won't be able to select across multiple blocks: this is a limitation of React Native.
There is a detailed explaination for this warning here: Stack Overflow | react-native-render-html, "You seem to update ...".
That would often happen in the HTML markup when your custom tags is self-closing such as in
<customtag />. The HTML5 standard strictly prohibits non-void elements to be self-closing, and the required behavior for a parser is to ignore the
/ character in that case. Abding by this standard, the HTML parser will end up considering
<customtag /> as equivlent to
<customtag >. Therefore, any content below it will be considered as children of
<customtag>. Because it is forgiving, the parser will close this tag when it reaches the end of the stream. To overcome this issue, you have two options:
<customtag></customtag>in your HTML markup.
This is caused by a known limitation in React Native. The issue is being tracked on Github.
Likely a bug between
react-native-screens. See Stack Overflow | When rendering iframes, Android crashes while navigating back to stack screen.
Probably an issue with your package manager. See Stack Overflow | Unable to resolve XXX from module YYY.
This is a limitation of FaceBook's fresco library and React Native
Image component. You need to downsize the image.