update website

docs/known-issues.html

@@ -25,7 +25,7 @@ Alert</div><h3><a class="anchor" name="some-props-are-only-supported-on-one-plat
     opacity<span class="token punctuation">:</span> <span class="token number">0</span><span class="token punctuation">}</span><span class="token punctuation">}</span> <span class="token operator">/</span><span class="token operator">&gt;</span>
 &lt;<span class="token operator">/</span>View<span class="token operator">&gt;</span></div><p>The behavior on Android is what you would expect from the web as well.  If you want to be able to click through an overlaying transparent view, you can set <code>pointerEvents=&#x27;none&#x27;</code> on it.</p><h3><a class="anchor" name="the-overflow-style-property-defaults-to-hidden-and-cannot-be-changed-on-android"></a>The <code>overflow</code> style property defaults to <code>hidden</code> and cannot be changed on Android <a class="hash-link" href="#the-overflow-style-property-defaults-to-hidden-and-cannot-be-changed-on-android">#</a></h3><p>This is a result of how Android rendering works. This feature is not being worked on as it would be a significant undertaking and there are many more important tasks.</p><h3><a class="anchor" name="no-support-for-shadows-on-android"></a>No support for shadows on Android <a class="hash-link" href="#no-support-for-shadows-on-android">#</a></h3><p>We don&#x27;t support shadows on Android currently. These are notoriously hard to implement as they require drawing outside of a view&#x27;s bounds and Android&#x27;s invalidation logic has a hard time with that. A possible solution is to use <a href="https://developer.android.com/training/material/shadows-clipping.html" target="_blank">elevation</a>, but more experimentation will be required.</p><h3><a class="anchor" name="layout-only-nodes-on-android"></a>Layout-only nodes on Android <a class="hash-link" href="#layout-only-nodes-on-android">#</a></h3><p>An optimization feature of the Android version of React Native is for views which only contribute to the layout to not have a native view, only their layout properties are propagated to their children views. This optimization is to provide stability in deep view hierarchies for React Native and is therefore enabled by default. Should you depend on a view being present or internal tests incorrectly detect a view is layout only it will be necessary to turn off this behavior. To do this, set <code>collapsable</code> to false as in this example:</p><div class="prism language-javascript">&lt;View collapsable<span class="token operator">=</span><span class="token punctuation">{</span><span class="token boolean">false</span><span class="token punctuation">}</span><span class="token operator">&gt;</span>
     <span class="token punctuation">.</span><span class="token punctuation">.</span><span class="token punctuation">.</span>
-&lt;<span class="token operator">/</span>View<span class="token operator">&gt;</span></div><h3><a class="anchor" name="memory-issues-with-png-images"></a>Memory issues with PNG images <a class="hash-link" href="#memory-issues-with-png-images">#</a></h3><p>React Native Android depends on <a href="https://github.com/facebook/fresco" target="_blank">Fresco</a> for loading and displaying images. Currently we have disabled downsampling because it is experimental, so you may run into memory issues when loading large PNG images.</p><h3><a class="anchor" name="react-native-init-hangs"></a>react-native init hangs <a class="hash-link" href="#react-native-init-hangs">#</a></h3><p>Try running <code>react-native init</code> with <code>--verbose</code> and see <a href="https://github.com/facebook/react-native/issues/2797" target="_blank">#2797</a> for common causes.</p></div><div class="docs-prevnext"><a class="docs-next" href="performance.html#content">Next →</a></div></div></section><footer class="wrap"><div class="center">© 2015 Facebook Inc.</div></footer></div><div id="fb-root"></div><script>
+&lt;<span class="token operator">/</span>View<span class="token operator">&gt;</span></div><h3><a class="anchor" name="memory-issues-with-png-images"></a>Memory issues with PNG images <a class="hash-link" href="#memory-issues-with-png-images">#</a></h3><p>React Native Android depends on <a href="https://github.com/facebook/fresco" target="_blank">Fresco</a> for loading and displaying images. Currently we have disabled downsampling because it is experimental, so you may run into memory issues when loading large PNG images.</p><h3><a class="anchor" name="react-native-init-hangs"></a>react-native init hangs <a class="hash-link" href="#react-native-init-hangs">#</a></h3><p>Try running <code>react-native init</code> with <code>--verbose</code> and see <a href="https://github.com/facebook/react-native/issues/2797" target="_blank">#2797</a> for common causes.</p><h3><a class="anchor" name="text-input-border"></a>Text Input Border <a class="hash-link" href="#text-input-border">#</a></h3><p>The text input has by default a border at the bottom of its view. This border has its padding set by the background image provided by the system, and it cannot be changed. Solutions to avoid this is to either not set height explicitly, case in which the system will take care of displaying the border in the correct position, or to not display the border by setting underlineColor to transparent.</p></div><div class="docs-prevnext"><a class="docs-next" href="performance.html#content">Next →</a></div></div></section><footer class="wrap"><div class="center">© 2015 Facebook Inc.</div></footer></div><div id="fb-root"></div><script>
             (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
             (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
             m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)