Clarity is a scalable, accessible, customizable, open source design system built with web components. Works with any JavaScript framework, built for enterprises, and designed to be inclusive.
Some custom elements fail to instantiate due to a property being set to early in its life cycle. If a native built in property is set that reflects its attribute before the element has been added to the DOM it can throw an exception in some browsers.
This moves the property to be set in the connectedCallback to prevent the exception. Unfortunately I could not find a great way to test this since this is a life cycle issue controlled by the browser. This will need to be backported to v5
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Some custom elements fail to instantiate due to a property being set to early in its life cycle. If a native built in property is set that reflects its attribute before the element has been added to the DOM it can throw an exception in some browsers.
See references
https://stackoverflow.com/questions/43836886/failed-to-construct-customelement-error-when-javascript-file-is-placed-in-head
https://html.spec.whatwg.org/multipage/custom-elements.html#custom-element-conformance
closes #6589
closes #6590
What is the new behavior?
This moves the property to be set in the connectedCallback to prevent the exception. Unfortunately I could not find a great way to test this since this is a life cycle issue controlled by the browser. This will need to be backported to v5
Does this PR introduce a breaking change?
Other information