[TextInput] Image nested in TextInput will be invisible
See original GitHub issueIs this a bug report?
Yes.
Have you read the Contributing Guidelines?
Yes.
Environment
Environment: OS: macOS Sierra 10.12.6 Node: 7.7.4 Yarn: - npm: 4.1.2 Watchman: 4.1.0 Xcode: 9.2.0 Android Studio: -
Packages: (wanted => installed) react-native: 0.42.2 => 0.42.2 react: 15.4.2 => 15.4.2
Target Platform: iOS (11)
Steps to Reproduce
(Write your steps here:)
- Create a
<TextInput>
- Nest a
<Image>
within<TextInput>
Expected Behavior
(Write what you thought would happen.)
- The
<Image>
could be displayed within<TextInput>
- The
<Image>
could be removed with pressing delete button.
Actual Behavior
<Image>
will be invisible but it seems like it occupied same space with thewidth
andheight
we set to<Image>
- There is also cursor around the invisible image, but when we press delete button, sometimes the space could not be removed. If we move the cursor around the invisible image back and forth and try to press delete button again, the space will be removed
In addition, I know in iOS we could use NSAttributedString
while using SpannableString
in Android, but not sure how we could archive inserting custom image into <TextInput>
with React Native.
Reproducible Demo
(Paste the link to an example project and exact instructions to reproduce the issue.)
https://stackoverflow.com/questions/45062363/react-native-image-inside-multiline-textinput
(https://snack.expo.io/ is really slow in China, so I use the same issue on stack overflow here, there is screenshot there.)
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:8
Top GitHub Comments
Would love for this to be supported as well. I would say custom view will be amazing…
Thanks for posting this! It looks like you may not be using the latest version of React Native, v0.53.0, released on January 2018. Can you make sure this issue can still be reproduced in the latest version?
I am going to close this, but please feel free to open a new issue if you are able to confirm that this is still a problem in v0.53.0 or newer.
How to Contribute • What to Expect from Maintainers