Feature add stop event property #323
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
U29
force-pushed
the
feature-add-stopEvent-property
branch
from
8845ed7 to
6058e10
Compare
U29
force-pushed
the
feature-add-stopEvent-property
branch
from
6058e10 to
37e6a49
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Currently, the stopEvent property of ROverlay cannot be controlled and is always true. Also, if “pointer-events-none” is not specified in ROverlay, it will not work correctly when the map is moved or expanded on ROverlay. However, if “pointer-events-none” is removed, the onClick event will no longer fire.
Setting
stopEvent=falsesolves the above problem.