Skip to content
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

Closed
semiautomatix opened this issue May 9, 2017 · 4 comments
Closed

RNW Elements being affected by pointerEvents #1109

semiautomatix opened this issue May 9, 2017 · 4 comments

Comments

@semiautomatix
Copy link

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.

image


Install Ignite 2.0 as per instructions
npm install --save-dev rnpm-plugin-windows
react-native windows
react-native run-windows

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:

<View
          pointerEvents={ this._open && this.shouldCaptureGestures() ? 'auto' : 'none' }
/>

and

const pointerEvents = drawerShown ? 'auto' : 'none';

<Animated.View
            pointerEvents={pointerEvents}
/>
@matthargett
Copy link
Contributor

@GantMan or @kevinvangelder can probably make some suggestions on this.

@rozele
Copy link
Collaborator

rozele commented Nov 17, 2017

@semiautomatix sounds like there are two separate problems here:

  1. Cursor position
  2. Issue with drawer and ScrollView gestures

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
@rozele
Copy link
Collaborator

rozele commented Jul 23, 2018

@semiautomatix please update if this is still an issue.

@semiautomatix
Copy link
Author

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
GoldenDragon0710 added a commit to GoldenDragon0710/Lottie-React-Native that referenced this issue Nov 27, 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
Projects
None yet
Development

No branches or pull requests

3 participants