feat(#616): Remove long press in maps #621
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: 5085bb1 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
6 tasks
…e-long-press-in-maps # Conflicts: # packages/web-forms/src/components/common/map/useMapInteractions.ts
…e-long-press-in-maps
latin-panda
commented
Jan 27, 2026
| extent: getProjection(DEFAULT_VIEW_PROJECTION)?.getExtent(), | ||
| }), | ||
| controls: [new Zoom(), new Attribution({ collapsible: false })], | ||
| interactions: defaultInteractions({ doubleClickZoom: false }), |
Collaborator
Author
There was a problem hiding this comment.
We want tap to add only points/vertices (ref: 5th bullet point). The user can still pinch, scroll, and use the +/- buttons to zoom.
Collaborator
Author
|
@garethbowen This is ready for review! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #616
I have verified this PR works in these browsers (latest versions):
What else has been done to verify that this works as intended?
Test video: geoshape, geotrace, geopoint
no-long-press.mp4
Why is this the best possible solution? Were any other approaches considered?
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
New user interaction is described in the ticket.
A faster way to add points. Accidental points are expected, but the user can handle them by deleting points or using the undo feature.
Do we need any specific form for testing your changes? If so, please attach one.
The demo form has forms in the geolocation section
What's changed