From 954df6d13ebc01e1fa0902adfd443b208930bce8 Mon Sep 17 00:00:00 2001 From: Dan Purdy Date: Sun, 30 Oct 2016 11:26:23 -0700 Subject: [PATCH] Update image docs with missing iOS style warning Summary: As discussed in #10570 to document that corner specific border radius styles are unsupported with the iOS image component. Closes #10570 Have signed the CLA and ensured the website section affected still works Screenshot included as suggested in the contribution guidelines. ![rn-doc-update](https://cloud.githubusercontent.com/assets/1386054/19838492/4eb91d7c-9ec8-11e6-98cf-c085ef4af5c2.png) Closes https://github.com/facebook/react-native/pull/10632 Differential Revision: D4102593 fbshipit-source-id: ffc901ec4e7e50f5a189fb2d98d79eaa33a95e37 --- docs/Images.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/Images.md b/docs/Images.md index 56eca6264f..d3f6352d13 100644 --- a/docs/Images.md +++ b/docs/Images.md @@ -136,6 +136,15 @@ return ( ); ``` +## iOS Border Radius Styles + +Please note that the following corner specific, border radius style properties are currently ignored by iOS's image component: + +* `borderTopLeftRadius` +* `borderTopRightRadius` +* `borderBottomLeftRadius` +* `borderBottomRightRadius` + ## Off-thread Decoding Image decoding can take more than a frame-worth of time. This is one of the major sources of frame drops on the web because decoding is done in the main thread. In React Native, image decoding is done in a different thread. In practice, you already need to handle the case when the image is not downloaded yet, so displaying the placeholder for a few more frames while it is decoding does not require any code change.