You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As demonstrated here, a custom element that extends a built-in via the is attribute behaves strangely. The extension is recognised and the custom element is constructed as expected; but the is attribute that determined this behaviour is not present on the rendered element. Having been specified in hyperscript, I would expect it to remain.
The text was updated successfully, but these errors were encountered:
As long as we deal with [is], we have a render bug in the update phase. is should be considered part of the element identity along with the tag name when diffing.
As demonstrated here, a custom element that extends a built-in via the
is
attribute behaves strangely. The extension is recognised and the custom element is constructed as expected; but theis
attribute that determined this behaviour is not present on the rendered element. Having been specified in hyperscript, I would expect it to remain.The text was updated successfully, but these errors were encountered: