fix(vue): v-model does not update when other events bubble up

[liamdebeasi]

Pull request checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Build (npm run build) was run locally for affected output targets
• Tests (npm test) were run locally and passed
• Prettier (npm run prettier) was run locally and passed

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

Issue URL: resolves #424

What is the new behavior?

• The Vue wrappers only update the v-model on an element when the event originated from that element and not from any descendant elements.

Does this introduce a breaking change?

• Yes
• No

Other information

Dev build: 0.0.1-dev.11711372539.10de27e3

Verified this issue is fixed using an Ionic Framework build in the sample app from the linked issue.

[rwaskiewicz]

Is it guaranteed that at least one of these two values can never be undefined/null? My only thought here is running into a case where we end up doing:

if (undefined === undefined) {

[liamdebeasi]

Good question. Element.tagName is always defined.

If e.target is defined then it should be an Element (which means tagName is defined). However, EventTarget can potentially be null. My understanding is that target can be null when an event is created but not dispatched on an element. You can test this by logging new CustomEvent('foo'). In this case, the event is dispatched on an element, so target should be non-null.