auro-button-light: Missing conditional check before defining custom element #95
Labels
released
Completed work has been released
Status: Review Needed
Work is completed, user is requesting feedback
Type: Bug
Bug or Bug fixes
Describe the bug
auro-button has a conditional check, it prevents the custom element registry from throwing an error by trying to define the same custom element twice. This check is missing from auro-button light.
To Reproduce
Steps to reproduce the behavior:
Outcome: error in the browser console, auro-button-light is already defined.
Expected behavior
First to load auro-button-light defines the element (app or component), second skips the define step.
Screenshots
n/a
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
In discussion, is there a question whether we still need auro-button-light given the enhancements with es5 bundling and eventually dropping IE11 support?
The text was updated successfully, but these errors were encountered: