-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Fix: Text component pressRetentionOffset issue on Windows #14596
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
Changes from all commits
df331c2
2703a66
737bf05
41d0b46
b792837
3c72cea
aec3c0a
4f646c4
f1494e9
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
{ | ||
"type": "none", | ||
"comment": "Fix: Text component pressRetentionOffset issue on Windows", | ||
"packageName": "react-native-windows", | ||
"email": "[email protected]", | ||
"dependentChangeType": "none" | ||
} |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -224,6 +224,14 @@ export interface TextProps | |
* Controls how touch events are handled. Similar to `View`'s `pointerEvents`. | ||
*/ | ||
pointerEvents?: ViewStyle['pointerEvents'] | undefined; | ||
|
||
/** | ||
* Insets for press retention. | ||
* Example: { top: 20, left: 20, bottom: 20, right: 20 } | ||
*/ | ||
pressRetentionOffset?: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This looks like a bug in core. -- This property should be added to Text.d.ts upstream. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yeah this a bug , they are handling it textprops.js file but didnt add as a prop ins text.d.ts file |
||
| {top: number; left: number; bottom: number; right: number} | ||
| undefined; | ||
} | ||
|
||
/** | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to remove the hasMoveEventListeners check here? Isn't there a perf cost to this (now all move events will always have to be fired and propagated to JS, even if no-one is listening?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
only applies to active touches that have already claimed responder status - not to all pointer moves so sending these extra events for ongoing interactions, which is actually a small subset of all pointer movements