annevk: I'm going through Ladybird failures on the scoped custom element registry tests, and passing a registry to Document.importNode() isn't making sense to me. I see that Safari passes all of custom-elements/registries/Document-importNode.html, so maybe the implementation doesn't match the spec there. I'm looking at the second subtest there:

assert_true(document.importNode(document.createElement('some-element'), {customElementRegistry: scopedRegistry}) instanceof ScopedSomeElement);

some-element gets created using the document's registry. The test then expects importNode() to return a node that is using scopedRegistry instead. But, the registry is passed as cloneNode()'s fallbackRegistry, and that's only used if the node doesn't already have a registry. And it does have one!

Hello freddy I am happy to meet the core team!

I was asking, how can I see in the inspector of the dom of mozilla if the result of an innerHTML or what else creation is TrustedTYpe or not pleqse? I need to check for xss.

Hey, im reading through the spec and have a question. Hope this is the place to ask. The first point from the section on inserting a node into a parent is unclear to me: https://dom.spec.whatwg.org/#concept-node-insert

It says:

Let nodes be node’s children, if node is a DocumentFragment node; otherwise « node ».

What does "<< node >>" mean?