Chrome fails a bunch of these tests because it does not implement the Document constructor ( Issue 238234 .)


LayoutTests/fast/custom-elements/attribute-changed-callback.html (various)

Chrome appears to pass empty strings instead of null for old values (when adding) or new values (when removing.) See:

https://dom.spec.whatwg.org/#concept-element-attributes-append
https://dom.spec.whatwg.org/#concept-element-attributes-remove


LayoutTests/fast/custom-elements/adopted-callback.html (various)

Chrome does not pass the old and new documents to adoptedCallback.

https://dom.spec.whatwg.org/#concept-node-adopt


LayoutTests/fast/custom-elements/CustomElementRegistry.html:231
LayoutTests/fast/custom-elements/attribute-changed-callback.html:171

Chrome does not invoke the Symbol.iterator when converting the sequence of observedAttributes.
 

1. Chrome fails a bunch of these tests because it does not implement the Document constructor ( Issue 238234 .)


LayoutTests/fast/custom-elements/attribute-changed-callback.html (various)

2. Chrome appears to pass empty strings instead of null for old values (when adding) or new values (when removing.) See:

https://dom.spec.whatwg.org/#concept-element-attributes-append
https://dom.spec.whatwg.org/#concept-element-attributes-remove


LayoutTests/fast/custom-elements/adopted-callback.html (various)

3. Chrome does not pass the old and new documents to adoptedCallback.

https://dom.spec.whatwg.org/#concept-node-adopt


LayoutTests/fast/custom-elements/CustomElementRegistry.html:231
LayoutTests/fast/custom-elements/attribute-changed-callback.html:171

Chrome does not invoke the Symbol.iterator when converting the sequence of observedAttributes.

4. When defining an element, check for CustomElementRegistry`s element definition flag is running.

5. When defining an element, do not check whether the constructor is an interface object.