-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RNW Elements being affected by pointerEvents #1109
Comments
@GantMan or @kevinvangelder can probably make some suggestions on this. |
@semiautomatix sounds like there are two separate problems here:
|
rozele
added a commit
to rozele/react-native-windows
that referenced
this issue
Nov 17, 2017
When `value` or `defaultValue` is set on the TextInput, if the cursor started at the end, it should remain at the end after the text is updated. Towards microsoft#1109
rozele
added a commit
to rozele/react-native-windows
that referenced
this issue
Nov 17, 2017
When `value` or `defaultValue` is set on the TextInput, if the cursor started at the end, it should remain at the end after the text is updated. Towards microsoft#1109
rozele
added a commit
that referenced
this issue
Nov 17, 2017
When `value` or `defaultValue` is set on the TextInput, if the cursor started at the end, it should remain at the end after the text is updated. Towards #1109
lbochenek
pushed a commit
to lbochenek/react-native-windows
that referenced
this issue
Dec 13, 2017
When `value` or `defaultValue` is set on the TextInput, if the cursor started at the end, it should remain at the end after the text is updated. Towards microsoft#1109
keatongreve
pushed a commit
to keatongreve/react-native-windows
that referenced
this issue
Jan 15, 2018
When `value` or `defaultValue` is set on the TextInput, if the cursor started at the end, it should remain at the end after the text is updated. Towards microsoft#1109
keatongreve
pushed a commit
to hudl/react-native-windows
that referenced
this issue
May 2, 2018
When `value` or `defaultValue` is set on the TextInput, if the cursor started at the end, it should remain at the end after the text is updated. Towards microsoft#1109
@semiautomatix please update if this is still an issue. |
Thanks @rozele. I'm no longer on this project, so can't comment on whether the issue persists. I'm happy to close. |
matinzd
added a commit
to lottie-react-native/lottie-react-native
that referenced
this issue
Jan 17, 2023
BREAKING CHANGE: remove react-native-windows support on paper due to microsoft/react-native-windows#1109
alyssaharvey3
added a commit
to alyssaharvey3/react-native-lottie
that referenced
this issue
Aug 2, 2023
BREAKING CHANGE: remove react-native-windows support on paper due to microsoft/react-native-windows#1109
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a peculiar problem resulting from using Ignite 2.0 and react-native-windows whereby the TextInputs are positioning the cursor at the beginning of a field when the field is populated using the value property. See below.
It's also preventing ScrollView from scrolling - so could be a bigger problem than just a textinput,
I believed I've narrowed down the issue to the pointerEvents property. The react-native-drawer component contains this property in View (and I've also tested react-native-drawer-layout
that contains this property in Animated.View). The specific piece of code is:
and
The text was updated successfully, but these errors were encountered: