From cd4a8341aa7925c7d870ef7bc398620915796e03 Mon Sep 17 00:00:00 2001 From: Website Deployment Script Date: Wed, 21 Jun 2017 02:31:54 +0000 Subject: [PATCH] Updated docs for next --- releases/next/docs/text.html | 4 ++-- releases/next/docs/view.html | 4 ++-- releases/next/docs/viewproptypes.html | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/releases/next/docs/text.html b/releases/next/docs/text.html index bff4b02a76e..b3978efd5a4 100644 --- a/releases/next/docs/text.html +++ b/releases/next/docs/text.html @@ -45,7 +45,7 @@ default is true.

numberOfLines?: PropTypes.number #

Used to truncate the text with an ellipsis after computing the text +missing text at the end of the line is indicated by an ellipsis glyph. e.g., "abcd..."

  • clip - Lines are not drawn past the edge of the text container.

    • The default is tail.

    clip is working only for iOS

    nativeID?: PropTypes.string #

    Used to locate this view from native code.

    numberOfLines?: PropTypes.number #

    Used to truncate the text with an ellipsis after computing the text layout, including line wrapping, such that the total number of lines does not exceed this number.

    This prop is commonly used with ellipsizeMode.

    onLayout?: PropTypes.func #

    Invoked on mount and layout changes with

    {nativeEvent: {layout: {x, y, width, height}}}

    onLongPress?: PropTypes.func #

    This function is called on long press.

    e.g., onLongPress={this.increaseSize}>

    onPress?: PropTypes.func #

    This function is called on press.

    e.g., onPress={() => console.log('1st')}

    pressRetentionOffset?: {top: number, left: number, bottom: number, right: number} #

    When the scroll view is disabled, this defines how far your touch may move off of the button, before deactivating the button. Once deactivated, @@ -79,7 +79,7 @@ For best results also set textAlignVertical to center. ['solid' /*default*/, 'double', 'dotted','dashed'] )

    ioswritingDirection ReactPropTypes.oneOf( ['auto' /*default*/, 'ltr', 'rtl'] -)

    testID?: PropTypes.string #

    Used to locate this view in end-to-end tests.

    androiddisabled?: PropTypes.bool #

    Specifies the disabled state of the text view for testing purposes

    androidnativeID?: PropTypes.string #

    Used to locate this view from native code.

    androidselectionColor?: color #

    The highlight color of the text.

    androidtextBreakStrategy?: PropTypes.oneOf(['simple', 'highQuality', 'balanced']) #

    Set text break strategy on Android API Level 23+, possible values are simple, highQuality, balanced +)

    testID?: PropTypes.string #

    Used to locate this view in end-to-end tests.

    androiddisabled?: PropTypes.bool #

    Specifies the disabled state of the text view for testing purposes

    androidselectionColor?: color #

    The highlight color of the text.

    androidtextBreakStrategy?: PropTypes.oneOf(['simple', 'highQuality', 'balanced']) #

    Set text break strategy on Android API Level 23+, possible values are simple, highQuality, balanced The default value is highQuality.

    iosadjustsFontSizeToFit?: PropTypes.bool #

    Specifies whether font should be scaled down automatically to fit given style constraints.

    iosminimumFontScale?: PropTypes.number #

    Specifies smallest possible scale a font can reach when adjustsFontSizeToFit is enabled. (values 0.01-1.0).

    iossuppressHighlighting?: PropTypes.bool #

    When true, no visual change is made when text is pressed down. By default, a gray oval highlights the text on press down.

    You can edit the content above on GitHub and send us a pull request!

    Description #

    Nested Text #

    Both iOS and Android allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (NSAttributedString on iOS, SpannableString on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.

    import React, { Component } from 'react'; import { AppRegistry, Text } from 'react-native'; diff --git a/releases/next/docs/view.html b/releases/next/docs/view.html index 344812f66e4..4b3f4c34c74 100644 --- a/releases/next/docs/view.html +++ b/releases/next/docs/view.html @@ -24,7 +24,7 @@ Typical interface guidelines recommend touch targets that are at least 30 - 40 points/density-independent pixels.

    For example, if a touchable view has a height of 20 the touchable height can be extended to 40 with hitSlop={{top: 10, bottom: 10, left: 0, right: 0}}

    The touch area never extends past the parent view bounds and the Z-index of sibling views always takes precedence if a touch hits two overlapping -views.

    onAccessibilityTap?: PropTypes.func #

    When accessible is true, the system will try to invoke this function +views.

    nativeID?: PropTypes.string #

    Used to locate this view from native classes.

    This disables the 'layout-only view removal' optimization for this view!

    onAccessibilityTap?: PropTypes.func #

    When accessible is true, the system will try to invoke this function when the user performs accessibility tap gesture.

    onLayout?: PropTypes.func #

    Invoked on mount and layout changes with:

    {nativeEvent: { layout: {x, y, width, height}}}

    This event is fired immediately once the layout has been calculated, but the new layout may not yet be reflected on the screen at the time the event is received, especially if a layout animation is in progress.

    onMagicTap?: PropTypes.func #

    When accessible is true, the system will invoke this function when the @@ -95,7 +95,7 @@ fires accessibility events and if it is reported to accessibility services that query the screen. Works for Android only.

    Possible values:

    • 'auto' - The system determines whether the view is important for accessibility - default (recommended).
    • 'yes' - The view is important for accessibility.
    • 'no' - The view is not important for accessibility.
    • 'no-hide-descendants' - The view is not important for accessibility, nor are any of its descendant views.

    See the Android importantForAccessibility docs -for reference.

    androidnativeID?: PropTypes.string #

    Used to locate this view from native classes.

    This disables the 'layout-only view removal' optimization for this view!

    androidneedsOffscreenAlphaCompositing?: PropTypes.bool #

    Whether this View needs to rendered offscreen and composited with an alpha +for reference.

    androidneedsOffscreenAlphaCompositing?: PropTypes.bool #

    Whether this View needs to rendered offscreen and composited with an alpha in order to preserve 100% correct colors and blending behavior. The default (false) falls back to drawing the component and its children with an alpha applied to the paint used to draw each element instead of rendering the full diff --git a/releases/next/docs/viewproptypes.html b/releases/next/docs/viewproptypes.html index a5bb00f595d..030dd137745 100644 --- a/releases/next/docs/viewproptypes.html +++ b/releases/next/docs/viewproptypes.html @@ -6,7 +6,7 @@ Typical interface guidelines recommend touch targets that are at least 30 - 40 points/density-independent pixels.

    For example, if a touchable view has a height of 20 the touchable height can be extended to 40 with hitSlop={{top: 10, bottom: 10, left: 0, right: 0}}

    The touch area never extends past the parent view bounds and the Z-index of sibling views always takes precedence if a touch hits two overlapping -views.

    onAccessibilityTap?: PropTypes.func #

    When accessible is true, the system will try to invoke this function +views.

    nativeID?: PropTypes.string #

    Used to locate this view from native classes.

    This disables the 'layout-only view removal' optimization for this view!

    onAccessibilityTap?: PropTypes.func #

    When accessible is true, the system will try to invoke this function when the user performs accessibility tap gesture.

    onLayout?: PropTypes.func #

    Invoked on mount and layout changes with:

    {nativeEvent: { layout: {x, y, width, height}}}

    This event is fired immediately once the layout has been calculated, but the new layout may not yet be reflected on the screen at the time the event is received, especially if a layout animation is in progress.

    onMagicTap?: PropTypes.func #

    When accessible is true, the system will invoke this function when the @@ -77,7 +77,7 @@ fires accessibility events and if it is reported to accessibility services that query the screen. Works for Android only.

    Possible values:

    • 'auto' - The system determines whether the view is important for accessibility - default (recommended).
    • 'yes' - The view is important for accessibility.
    • 'no' - The view is not important for accessibility.
    • 'no-hide-descendants' - The view is not important for accessibility, nor are any of its descendant views.

    See the Android importantForAccessibility docs -for reference.

    androidnativeID?: PropTypes.string #

    Used to locate this view from native classes.

    This disables the 'layout-only view removal' optimization for this view!

    androidneedsOffscreenAlphaCompositing?: PropTypes.bool #

    Whether this View needs to rendered offscreen and composited with an alpha +for reference.

    androidneedsOffscreenAlphaCompositing?: PropTypes.bool #

    Whether this View needs to rendered offscreen and composited with an alpha in order to preserve 100% correct colors and blending behavior. The default (false) falls back to drawing the component and its children with an alpha applied to the paint used to draw each element instead of rendering the full