Text numberOfLines prop is not respected in Nested Text

[mloureiro]

name: 🐛 Bug Report
about: Report a reproducible bug or regression in the core React Native library.

• Review the documentation: https://facebook.github.io/react-native
• Search for existing issues: https://github.com/facebook/react-native/issues
• Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment

[skip envinfo]
This is reproducible in the expo playground

Description

Property numberOfLines is not respected when used in a child Text component:

<Text>
  <Text  numberOfLines={1}>{'sometext'.repeat(1000)}</Text>
</Tex>

In this #4733 (comment) @oureta mentions that this does not work, I don't understand if it is expected behavior, or a 🐛

According to Text doc the styling has some limitations with inheritance/nesting, although nothing is specified (AFAICT) about the other properties.

Reproducible Demo

https://snack.expo.io/H1IZHzGbN

[react-native-bot]

Can you run react-native info and edit your issue to include these results under the Environment section?

If you believe this information is irrelevant to the reported issue, you may write [skip envinfo] under Environment to let us know.

[bartolkaruza]

This will be difficult to implement on Android, as the nested text is represented by a single TextView on which the maxLines and singleLine props are set to implement numberOfLines at the native level. You can check out that code here. The nested text is represented by a span which does not have those properties. I'm not sure how hard it would be to implement on iOS, but I imagine similar issues will be there.

This should probably be added to the known issues section of the Text component doc. @mloureiro do you feel up to making a PR for that on https://github.com/facebook/react-native-website using the template from here?

[mloureiro]

Will do.

PR: facebook/react-native-website#724

[react-native-bot]

I am closing this issue because it does not contain the necessary environment info, and there has been no followup in a while.

If you found this thread after encountering the same issue in the latest release, please feel free to create a new issue with up-to-date information by clicking here.