Chrome's native implementation appears to be enforcing specification requirements that the polyfill was not. According to the "Requirements for custom element constructors" section of the spec:
The element must not gain any attributes or children, as this violates the expectations of consumers who use the createElement or createElementNS methods.
The element that I was attempting to create added children to itself in its constructor.
The solution was to follow the recommendations of the spec:
In general, work should be deferred to connectedCallback as much as possible—especially work involving fetching resources or rendering. However, note that connectedCallback can be called more than once, so any initialization work that is truly one-time will need a guard to prevent it from running twice.
That is, add children in the connected callback and use a flag to ensure the element is only initialized on first connection.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…