Basalt

Platform support

What works on which desktop, prop by prop, counted by this script rather than claimed.

Three desktops, three native toolkits, and not the same amount finished on each. One row per attribute, with anything short of done linking to the entry that says what is missing and which call would do it.

The attributes are React Native's own, read out of its declarations rather than listed here: scripts/scrape_props.py scrapes React Native 0.88.1 and this renders what it found, so a prop added upstream turns up as a row with no status and fails the check until somebody fills it in.

Every style name a <View> or a <Text> takes has a row. Most are fields in one of ReactCommon's prop structs. The rest belong to Yoga: padding, margin, flex, inset, gap and their spellings, which no struct declares one by one, because YogaStylableProps carries a single yogaStyle field. Those names come from React Native's own ____LayoutStyle_Internal and sit in a section of their own. A handful are declared in JavaScript and read by no struct at all, and they are listed too, because an app can still write them.

The scrape reports any style name that is none of those three, which is what makes this list complete rather than long: the layout props were missing from this page until somebody went looking for padding, and nothing could have said so.

Every component this platform mounts now has its props scraped from the struct that declares them: a <View>, a <Text>, an <Image>, a <TextInput> and a <ScrollView>. What is not here is a component none of the three hosts mounts, which is the same thing as a component this platform does not have: backlog/components.md keeps that list.

Each struct is split the way reactnative.dev splits a component page: the style props a style={{...}} takes, then the props written on the element itself. That split is read from React Native too, out of the Flow types that declare both, so a prop that moves between them moves here. Where ReactCommon spells a prop differently from JavaScript, the name an app writes is the one in the row and ReactCommon's is under it; where several names land in one field, as thirteen corner radii land in borderRadii, they are listed under the row that implements them.

HostToolkitWritten itselfAll 281 rows
LinuxGTK4126 of 137, 92%
macOSAppKit130 of 141, 92%
WindowsWin32124 of 137, 91%

Written itself is out of the rows that host writes: what it has written, what it has half written, and what is still missing. The hatched part of the bar is the rest, and it is nobody's work left.

LinuxmacOSWindows
✅ done126130124
◐ partly done101012
✖ not yet111
△ ReactCommon's or Yoga's747474
– deliberately not done706670
  • ReactCommon's or Yoga's is a prop that never reaches one of these toolkits. Yoga lays out flex and padding off the shadow tree before a host sees a view, and ReactCommon parses and animates opacity the same way everywhere. Nothing for a host to write, and nothing for this platform to claim.
  • Deliberately not done is a prop with its reason in the Why column: an Android-only field, a prop upstream itself ignores, a knob no desktop has. These will not move, so counting them as work left would make the bar never fill.

A tick is an index entry, not a proof. What proves a prop behaves is the end-to-end scenario that exercises it on every host, in scripts/integration_test.py. What this page is checked against is narrower and still worth having: a host claiming a prop has to read it, and a host disclaiming one has to not.

BaseViewProps

Every style and behaviour prop a <View> carries. From packages/react-native/ReactCommon/react/renderer/components/view/BaseViewProps.h.

Style props

Written inside style={{...}}. Read from ____LayoutStyle_Internal, ____ShadowStyle_InternalCore, ____ViewStyle_InternalBase, ____TransformStyle_Internal.

LinuxmacOSWindowsWhy
opacity✅✅✅
backgroundColor✅✅✅
borderRadius borderRadii
borderTopLeftRadius borderTopRightRadius borderBottomLeftRadius borderBottomRightRadius borderTopStartRadius borderTopEndRadius borderBottomStartRadius borderBottomEndRadius borderStartStartRadius borderStartEndRadius borderEndStartRadius borderEndEndRadius
✅✅✅
borderColor borderColors
borderTopColor borderBottomColor borderLeftColor borderRightColor borderStartColor borderEndColor borderBlockColor borderBlockStartColor borderBlockEndColor
✅✅✅
borderCurve borderCurves–––only the iOS view config declares it, and the two desktops would draw different corners
borderStyle borderStyles✅✅✅
outlineColor✅✅✅
outlineOffset✅✅✅
outlineStyle✅✅✅
outlineWidth✅✅✅
shadowColor✅✅✅
shadowOffset✅✅✅
shadowOpacity✅✅✅
shadowRadius✅✅✅
cursor✅✅✅
boxShadow✅✅✅
filter✅◐✅macOS casts the second and later drop shadows from the box rather than the alpha
experimental_backgroundImage backgroundImage✅✅✅
experimental_backgroundSize backgroundSize✅✅✅
experimental_backgroundPosition backgroundPosition✅✅✅
experimental_backgroundRepeat backgroundRepeat✅✅✅
mixBlendMode◐✅✅GSK has no plus-lighter
isolation–––no public way to composite a subtree as a group
transform✅✅✅
transformOrigin✅✅✅
backfaceVisibility✅✅✅
zIndex✅✅✅
pointerEvents✅✅✅

Component props

Written on the element itself, as <View onLayout={...} />.

LinuxmacOSWindowsWhy
shouldRasterizeIOS shouldRasterize–––performance hints, and one cannot arrive
hitSlop✅✅✅
onLayout△△△ReactCommon consumes it, and a scenario proves it here
collapsable△△△ReactCommon consumes it, and a scenario proves it here
collapsableChildren△△△ReactCommon consumes it, and a scenario proves it here
removeClippedSubviews–––performance hints, and one cannot arrive

Neither

Declared in ReactCommon and in no public prop type, so nothing an app writes reaches them: they are filled in by the renderer or are the innards of a component's own behaviour.

AccessibilityProps

What a view tells the platform's accessible layer. BaseViewProps inherits these. From packages/react-native/ReactCommon/react/renderer/components/view/AccessibilityProps.h.

Component props

Written on the element itself, as <View onLayout={...} />.

LinuxmacOSWindowsWhy
accessible✅✅✅
accessibilityState✅✅✅
accessibilityLabel✅✅✅
experimental_accessibilityOrder accessibilityOrder✅✅–UIA has no reading-order property: the tree order is the order
accessibilityLabelledBy✅✅✅
accessibilityLiveRegion✅✅✅
accessibilityRole✅✅✅
accessibilityHint✅✅✅
accessibilityLanguage–◐✅macOS carries it on a run of text, which covers a <Text> and not a view with no text; Windows takes the tag as an LCID; GTK 4 has no accessible language property at all
accessibilityLargeContentTitle–––iOS's own, with no desktop equivalent
accessibilityValue✅✅✅
accessibilityActions–✅–macOS has NSAccessibilityCustomAction and the other two have nothing to map it onto: GTK 4 ships no accessible-action interface, and UIA has no custom-action pattern
accessibilityShowsLargeContentViewer–––iOS's own, with no desktop equivalent
accessibilityViewIsModal✅✅✅
accessibilityElementsHidden✅✅✅
accessibilityIgnoresInvertColors–––iOS's own, with no desktop equivalent
accessibilityRespondsToUserInteraction✅✅✅
onAccessibilityTap–✅–macOS has NSAccessibilityCustomAction and the other two have nothing to map it onto: GTK 4 ships no accessible-action interface, and UIA has no custom-action pattern
onAccessibilityEscape–––iOS's own, with no desktop equivalent
onAccessibilityAction–✅–macOS has NSAccessibilityCustomAction and the other two have nothing to map it onto: GTK 4 ships no accessible-action interface, and UIA has no custom-action pattern
importantForAccessibility✅✅✅
role✅✅✅
testID testId◐✅✅GTK publishes an accessible id from 4.22; CI's 4.14 carries it and cannot publish it

Neither

Declared in ReactCommon and in no public prop type, so nothing an app writes reaches them: they are filled in by the renderer or are the innards of a component's own behaviour.

LinuxmacOSWindowsWhy
accessibilityTraits–––iOS's own, with no desktop equivalent
onAccessibilityMagicTap–––iOS's own, with no desktop equivalent

TextAttributes

Per-fragment text styling, so a nested <Text> can differ from its parent. From packages/react-native/ReactCommon/react/renderer/attributedstring/TextAttributes.h.

Style props

Written inside style={{...}}. Read from ____ViewStyle_InternalBase, ____TextStyle_InternalBase.

LinuxmacOSWindowsWhy
color foregroundColor✅✅✅
backgroundColor✅✅✅
opacity✅✅✅
fontFamily✅✅✅
fontSize✅✅✅
fontWeight✅✅✅
fontStyle✅✅✅
fontVariant✅✅✅
fontVariationSettings✖✖✖variable-font axes reach ReactCommon and no host applies them yet, though Core Text, Pango and DirectWrite all could
letterSpacing✅✅✅
textTransform✅✅✅
lineHeight✅✅✅
textAlign alignment✅✅✅
writingDirection baseWritingDirection✅✅✅
textDecorationColor✅✅✅
textDecorationLine textDecorationLineType✅✅✅
textDecorationStyle◐◐✅each engine draws the styles it has: Pango no dots or dashes, Core Text no wavy; the Win32 renderer draws all five
textShadowOffset◐◐◐one shadow per paragraph, not per fragment
textShadowRadius◐◐◐one shadow per paragraph, not per fragment
textShadowColor◐◐◐one shadow per paragraph, not per fragment

Component props

Written on the element itself, as <View onLayout={...} />.

Neither

Declared in ReactCommon and in no public prop type, so nothing an app writes reaches them: they are filled in by the renderer or are the innards of a component's own behaviour.

LinuxmacOSWindowsWhy
fontSizeMultiplier✅✅✅
isHighlighted–––iOS's own, with no desktop equivalent
isPressable–––iOS's own, with no desktop equivalent
layoutDirection✅✅✅
textEffects–––iOS's own, with no desktop equivalent

ImageProps

What an <Image> carries beyond a view's own props: the source, how it fills its box, and the Android and iOS extras. From packages/react-native/ReactCommon/react/renderer/components/image/ImageProps.h.

Style props

Written inside style={{...}}. Read from ____ImageStyle_InternalCore.

LinuxmacOSWindowsWhy
resizeMode
objectFit
✅✅✅
tintColor✅✅✅
overlayColor–––Android's own, and recorded as ignored with the rest of that group

Component props

Written on the element itself, as <View onLayout={...} />.

LinuxmacOSWindowsWhy
source sources✅✅✅
defaultSource✅✅✅
loadingIndicatorSource✅✅✅
blurRadius✅✅✅
capInsets–––iOS's resizable slicing, with no desktop equivalent
internal_analyticTag–––Meta's own analytics tag, which nothing outside their infrastructure reads
resizeMethod–––Android's own, and recorded as ignored with the rest of that group
resizeMultiplier–––Android's own, and recorded as ignored with the rest of that group
fadeDuration–––Android's own, and recorded as ignored with the rest of that group
progressiveRenderingEnabled–––Android's own, and recorded as ignored with the rest of that group

Neither

Declared in ReactCommon and in no public prop type, so nothing an app writes reaches them: they are filled in by the renderer or are the innards of a component's own behaviour.

LinuxmacOSWindowsWhy
shouldNotifyLoadEvents–––every host emits load events unconditionally, as iOS does

BaseScrollViewProps

What a <ScrollView> carries: which way it scrolls, what it bounces and snaps to, its indicators and its insets. From packages/react-native/ReactCommon/react/renderer/components/scrollview/BaseScrollViewProps.h.

Component props

Written on the element itself, as <View onLayout={...} />.

LinuxmacOSWindowsWhy
scrollEnabled✅✅✅

Neither

Declared in ReactCommon and in no public prop type, so nothing an app writes reaches them: they are filled in by the renderer or are the innards of a component's own behaviour.

LinuxmacOSWindowsWhy
alwaysBounceHorizontal–––a desktop scroll view has no rubber band, so there is nothing to turn off
alwaysBounceVertical–––a desktop scroll view has no rubber band, so there is nothing to turn off
bounces–––a desktop scroll view has no rubber band, so there is nothing to turn off
bouncesZoom–––no host zooms, and a desktop has no obvious gesture for it
canCancelContentTouches–––iOS's own, with no desktop equivalent
centerContent✅✅✅
automaticallyAdjustContentInsets–––iOS's own, with no desktop equivalent
automaticallyAdjustsScrollIndicatorInsets–––iOS's own, with no desktop equivalent
automaticallyAdjustKeyboardInsets–––iOS's own, with no desktop equivalent
decelerationRate✅◐◐all three project a fling's landing point with it, which is where a snap is chosen from; GTK also animates its own momentum at that rate, where AppKit uses the system's and Windows has no fling yet
endDraggingSensitivityMultiplier–––iOS's own, with no desktop equivalent
directionalLockEnabled–––iOS's own, with no desktop equivalent
indicatorStyle✅✅✅
keyboardDismissMode–––a soft keyboard, which a desktop does not have
maintainVisibleContentPosition✅✅✅
maximumZoomScale–––no host zooms, and a desktop has no obvious gesture for it
minimumZoomScale–––no host zooms, and a desktop has no obvious gesture for it
pagingEnabled✅✅✅
pinchGestureEnabled–––no host zooms, and a desktop has no obvious gesture for it
scrollsToTop–––iOS's own, with no desktop equivalent
showsHorizontalScrollIndicator✅✅✅
showsVerticalScrollIndicator✅✅✅
persistentScrollbar–––Android's own
horizontal–––the axis is derived from the content's size, so the hint goes unread
scrollEventThrottle✅✅✅
zoomScale–––no host zooms, and a desktop has no obvious gesture for it
contentInset✅✅✅
contentOffset✅✅✅
scrollIndicatorInsets✅✅✅
snapToInterval✅✅✅
snapToAlignment✅✅✅
disableIntervalMomentum✅✅✅
snapToOffsets✅✅✅
snapToStart✅✅✅
snapToEnd✅✅✅
contentInsetAdjustmentBehavior–––iOS's own, with no desktop equivalent
scrollToOverflowEnabled–––iOS's own, with no desktop equivalent
isInvertedVirtualizedList–––iOS's own, with no desktop equivalent

BaseTextInputProps

What a <TextInput> carries on every platform: the text, the placeholder, the tint colours and what the field will accept. From packages/react-native/ReactCommon/react/renderer/components/textinput/BaseTextInputProps.h.

Component props

Written on the element itself, as <View onLayout={...} />.

LinuxmacOSWindowsWhy
defaultValue△△△TextInput.js folds it into text before a host sees anything
placeholder✅✅✅
placeholderTextColor✅✅✅
cursorColor✅✅✅
selectionColor✅✅◐a Win32 EDIT draws its selection in COLOR_HIGHLIGHT, which no message changes: it wants a windowless RichEdit
selectionHandleColor–––Android's own
underlineColorAndroid–––Android's own
maxLength✅✅✅
text✅✅✅
autoFocus✅✅✅
autoCapitalize–––read through the iOS variant's trait of the same name, which has its own row
editable–––read through the iOS variant's trait of the same name, which has its own row
readOnly✅✅✅
submitBehavior✅✅✅
multiline✅✅✅
disableKeyboardShortcuts–––iOS's own, with no desktop equivalent

Neither

Declared in ReactCommon and in no public prop type, so nothing an app writes reaches them: they are filled in by the renderer or are the innards of a component's own behaviour.

TextInputProps

The iOS variant, which this platform reuses rather than forking: see docs/DECISIONS.md. It adds the selection and holds the traits below. From packages/react-native/ReactCommon/react/renderer/components/textinput/platform/ios/react/renderer/components/iostextinput/TextInputProps.h.

Component props

Written on the element itself, as <View onLayout={...} />.

LinuxmacOSWindowsWhy
selection✅✅✅
inputAccessoryViewID–––iOS's own, with no desktop equivalent
inputAccessoryViewButtonLabel–––iOS's own, with no desktop equivalent

Neither

Declared in ReactCommon and in no public prop type, so nothing an app writes reaches them: they are filled in by the renderer or are the innards of a component's own behaviour.

TextInputTraits

The keyboard and editing behaviour a field asks for. Declared with no section marker, so this one is read as a whole class. From packages/react-native/ReactCommon/react/renderer/components/textinput/platform/ios/react/renderer/components/iostextinput/primitives.h.

Component props

Written on the element itself, as <View onLayout={...} />.

LinuxmacOSWindowsWhy
autoCapitalize autocapitalizationType✅✅◐ES_UPPERCASE covers characters; an EDIT cannot find a word or a sentence
autoCorrect✅✅◐carried and reported; a Win32 EDIT has no spell checker and ISpellChecker draws nothing
contextMenuHidden◐✅✅GTK covers the pointer and not the Menu key, which GtkText binds internally
editable✅✅✅
enablesReturnKeyAutomatically–––iOS's own, with no desktop equivalent
keyboardAppearance–––iOS's own, with no desktop equivalent
spellCheck✅✅◐carried and reported; a Win32 EDIT has no spell checker and ISpellChecker draws nothing
caretHidden✅✅✅
clearButtonMode–––iOS's own, with no desktop equivalent
scrollEnabled✅✅✅
secureTextEntry✅✅✅
clearTextOnFocus✅✅✅
keyboardType✅✅✅
showSoftInputOnFocus–––a soft keyboard, which a desktop does not have
returnKeyType–––the label on a soft keyboard's return key, and no desktop has one
selectTextOnFocus✅✅✅
dataDetectorTypes–––iOS's own, with no desktop equivalent
textContentType–––iOS's own, with no desktop equivalent
passwordRules–––iOS's own, with no desktop equivalent
smartInsertDelete–––iOS's own, with no desktop equivalent

ParagraphAttributes

What belongs to a whole paragraph rather than to a fragment: how many lines it may take, how it is truncated, and whether it shrinks to fit. From packages/react-native/ReactCommon/react/renderer/attributedstring/ParagraphAttributes.h.

Style props

Written inside style={{...}}. Read from ____TextStyle_InternalBase.

Component props

Written on the element itself, as <View onLayout={...} />.

LinuxmacOSWindowsWhy
numberOfLines maximumNumberOfLines✅✅✅
ellipsizeMode✅✅✅
textBreakStrategy–––Android's own: ReactCommon declares it in that platform's host props
adjustsFontSizeToFit✅✅✅
android_hyphenationFrequency–––Android's own: ReactCommon declares it in that platform's host props
minimumFontScale✅✅✅

Neither

Declared in ReactCommon and in no public prop type, so nothing an app writes reaches them: they are filled in by the renderer or are the innards of a component's own behaviour.

LinuxmacOSWindowsWhy
minimumFontSize✅✅✅
maximumFontSize✅✅✅

BaseParagraphProps

What a <Text> carries that is not styling: the attributes above, whether its text can be selected, and whether it reports its own lines. Missed off this page until 2026-10-10, which is how selectable came to have no row while userSelect had one saying ReactCommon declared no field for it. From packages/react-native/ReactCommon/react/renderer/components/text/BaseParagraphProps.h.

Component props

Written on the element itself, as <View onLayout={...} />.

LinuxmacOSWindowsWhy
selectable isSelectable
userSelect
✅✅✅the paragraph is selected and copied; an inline view inside one is not
onTextLayout△△△the cxx TextLayoutManager has no measureLines

Neither

Declared in ReactCommon and in no public prop type, so nothing an app writes reaches them: they are filled in by the renderer or are the innards of a component's own behaviour.

LinuxmacOSWindowsWhy
paragraphAttributes✅✅✅

YogaStylableProps

Everything Yoga lays out with: padding, margin, flex, inset, gap and the rest. This struct carries one field, yogaStyle, so these names come from React Native's own ____LayoutStyle_Internal instead. From packages/react-native/ReactCommon/react/renderer/components/view/YogaStylableProps.h.

Style props

Written inside style={{...}}. Read from ____LayoutStyle_Internal.

LinuxmacOSWindowsWhy
alignContent△△△Yoga computes it and every host applies the frame it answers with
alignItems△△△Yoga computes it and every host applies the frame it answers with
alignSelf△△△Yoga computes it and every host applies the frame it answers with
aspectRatio△△△Yoga computes it and every host applies the frame it answers with
borderBottomWidth✅✅✅
borderEndWidth✅✅✅
borderLeftWidth✅✅✅
borderRightWidth✅✅✅
borderStartWidth✅✅✅
borderTopWidth✅✅✅
borderWidth✅✅✅
bottom△△△Yoga computes it and every host applies the frame it answers with
boxSizing△△△Yoga computes it and every host applies the frame it answers with
columnGap△△△Yoga computes it and every host applies the frame it answers with
direction△△△Yoga computes it and every host applies the frame it answers with
display△△△Yoga computes it and every host applies the frame it answers with
end△△△Yoga computes it and every host applies the frame it answers with
flex△△△Yoga computes it and every host applies the frame it answers with
flexBasis△△△Yoga computes it and every host applies the frame it answers with
flexDirection△△△Yoga computes it and every host applies the frame it answers with
flexGrow△△△Yoga computes it and every host applies the frame it answers with
flexShrink△△△Yoga computes it and every host applies the frame it answers with
flexWrap△△△Yoga computes it and every host applies the frame it answers with
gap△△△Yoga computes it and every host applies the frame it answers with
height△△△Yoga computes it and every host applies the frame it answers with
inset△△△Yoga computes it and every host applies the frame it answers with
insetBlock△△△Yoga computes it and every host applies the frame it answers with
insetBlockEnd△△△Yoga computes it and every host applies the frame it answers with
insetBlockStart△△△Yoga computes it and every host applies the frame it answers with
insetInline△△△Yoga computes it and every host applies the frame it answers with
insetInlineEnd△△△Yoga computes it and every host applies the frame it answers with
insetInlineStart△△△Yoga computes it and every host applies the frame it answers with
justifyContent△△△Yoga computes it and every host applies the frame it answers with
left△△△Yoga computes it and every host applies the frame it answers with
margin△△△Yoga computes it and every host applies the frame it answers with
marginBlock△△△Yoga computes it and every host applies the frame it answers with
marginBlockEnd△△△Yoga computes it and every host applies the frame it answers with
marginBlockStart△△△Yoga computes it and every host applies the frame it answers with
marginBottom△△△Yoga computes it and every host applies the frame it answers with
marginEnd△△△Yoga computes it and every host applies the frame it answers with
marginHorizontal△△△Yoga computes it and every host applies the frame it answers with
marginInline△△△Yoga computes it and every host applies the frame it answers with
marginInlineEnd△△△Yoga computes it and every host applies the frame it answers with
marginInlineStart△△△Yoga computes it and every host applies the frame it answers with
marginLeft△△△Yoga computes it and every host applies the frame it answers with
marginRight△△△Yoga computes it and every host applies the frame it answers with
marginStart△△△Yoga computes it and every host applies the frame it answers with
marginTop△△△Yoga computes it and every host applies the frame it answers with
marginVertical△△△Yoga computes it and every host applies the frame it answers with
maxHeight△△△Yoga computes it and every host applies the frame it answers with
maxWidth△△△Yoga computes it and every host applies the frame it answers with
minHeight△△△Yoga computes it and every host applies the frame it answers with
minWidth△△△Yoga computes it and every host applies the frame it answers with
overflow✅✅✅
padding△△△Yoga computes it and every host applies the frame it answers with
paddingBlock△△△Yoga computes it and every host applies the frame it answers with
paddingBlockEnd△△△Yoga computes it and every host applies the frame it answers with
paddingBlockStart△△△Yoga computes it and every host applies the frame it answers with
paddingBottom△△△Yoga computes it and every host applies the frame it answers with
paddingEnd△△△Yoga computes it and every host applies the frame it answers with
paddingHorizontal△△△Yoga computes it and every host applies the frame it answers with
paddingInline△△△Yoga computes it and every host applies the frame it answers with
paddingInlineEnd△△△Yoga computes it and every host applies the frame it answers with
paddingInlineStart△△△Yoga computes it and every host applies the frame it answers with
paddingLeft△△△Yoga computes it and every host applies the frame it answers with
paddingRight△△△Yoga computes it and every host applies the frame it answers with
paddingStart△△△Yoga computes it and every host applies the frame it answers with
paddingTop△△△Yoga computes it and every host applies the frame it answers with
paddingVertical△△△Yoga computes it and every host applies the frame it answers with
position△△△Yoga computes it and every host applies the frame it answers with
right△△△Yoga computes it and every host applies the frame it answers with
rowGap△△△Yoga computes it and every host applies the frame it answers with
start△△△Yoga computes it and every host applies the frame it answers with
top△△△Yoga computes it and every host applies the frame it answers with
width△△△Yoga computes it and every host applies the frame it answers with

StyleSheetTypes

Style names JavaScript declares and no ReactCommon struct these hosts read takes. An app can write them, so they are listed; what each one's status says is where it actually goes. From packages/react-native/Libraries/StyleSheet/StyleSheetTypes.js.

Style props

Written inside style={{...}}.

Image

What an <Image> does that is not one prop. Its props are scraped, in the ImageProps section above.

LinuxmacOSWindowsWhy
Files, http(s), data: URIs, decoded off the main thread✅✅✅
Animated images✅✅✅

On this page