Added new .self
modifier for event listeners
#379
Merged
+68
−21
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.
This PR introduces a new
.self
modifier with the same behaviour as Vue's implementation. This should also make it easier to prevent event's bubbled from nested elements being handled by parent elements, as in the case of #378.When used on an element, i.e.
<div @click.self="handle()">
, thehandle()
method will only be called (or expression evaluated) if the element triggering the event matches the element that registered it. This will remove the need to add several.stop
modifiers to nested elements when you don't want any event bubbling for that particular parent / component.I'm not sure if it's worth noting in the docs / README that chaining modifiers in different orders, for example
@click.self.prevent
and@click.prevent.self
, won't have any effect on the order of execution / evaluation since they are not being handled sequentially. The.prevent
and.stop
modifiers are always handled first, then the.self
modifier.P.s. there's a new test for this feature.