remove legacy this.fire event #53
Merged
Conversation
This file contains 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
catwomey
requested review from
alogan519,
awikkerink and
mdgbayly
as code owners
awikkerink
approved these changes
Jul 16, 2019
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.
This would remove the need for using the legacy element mixin. fire is just a convenience method for dispatching the CustomEvent with buble true and composed true.
Reference: https://polymer-library.polymer-project.org/3.0/api/legacy/legacy-element-mixin#LegacyElementMixin-method-fire
Custom events are polyfilled in the webcomponentjs file https://github.com/webcomponents/polyfills/blob/master/packages/webcomponentsjs/src/platform/custom-event.js