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

iOS: opens on long press regardless of shouldOpenOnLongPress setting #901

Open
erquhart opened this issue Sep 5, 2024 · 7 comments
Open

Comments

@erquhart
Copy link

erquhart commented Sep 5, 2024

The menu always opens on long press.

@JacksonML
Copy link

#983 Might be related to this, I started looking into the code in the repo and this PR is pretty much what I was coming up with as a fix.

@yyyyyyounger
Copy link

yyyyyyounger commented Feb 1, 2025

I still encounter this problem in 1.2.2.
With this code structure it always happens:

<MenuView>
  <Touchable... />
</MenuView>

Device: iOS 18.3 (Android will not happen when set the shouldOpenOnLongPress false)

@marcosrdz
Copy link
Contributor

I suggest renaming that prop to something less confusing. Perhaps isOpenOnPress? Something that doesnt imply that it will never open on long press

@erquhart
Copy link
Author

erquhart commented Mar 5, 2025

isOpenOnPress would be very confusing for me 😅

/**
* shouldOpenOnLongPress: determines whether menu should be opened after long press or normal press
*/
RCT_EXPORT_VIEW_PROPERTY(shouldOpenOnLongPress, BOOL)

If this doc is accurate, it seems it's named fine and is just broken, but I could definitely be missing something here.

@marcosrdz
Copy link
Contributor

isOpenOnPress would be very confusing for me 😅

/**
* shouldOpenOnLongPress: determines whether menu should be opened after long press or normal press
*/
RCT_EXPORT_VIEW_PROPERTY(shouldOpenOnLongPress, BOOL)

If this doc is accurate, it seems it's named fine and is just broken, but I could definitely be missing something here.

shouldOnlyOpenOnLongPress?

@marcosrdz
Copy link
Contributor

isOpenMenuPrimaryAction?

Multiple ways to name it

@erquhart
Copy link
Author

erquhart commented Mar 6, 2025

I just don't think the name is the problem - this issue is about the setting effectively doing nothing, it's a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants