Summary: | importNode from template doesn't instantiate custom element | ||
---|---|---|---|
Product: | WebKit | Reporter: | Jan Miksovsky <jan> |
Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | Normal | CC: | cdumez, rniwa |
Priority: | P2 | ||
Version: | Safari Technology Preview | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Bug Depends on: | |||
Bug Blocks: | 154907 |
Description
Jan Miksovsky
2016-10-07 15:10:27 PDT
This is kind of expected right now because we don't fully implement custom elements reactions yet. Ah, okay, we hadn't seen a description of what was/wasn't implemented. If such a description is posted somewhere, that would help us determine what bugs should be reported. Or should we just back off on reporting bugs for the time being? (In reply to comment #2) > Ah, okay, we hadn't seen a description of what was/wasn't implemented. If > such a description is posted somewhere, that would help us determine what > bugs should be reported. Or should we just back off on reporting bugs for > the time being? I'm actively fixing this but expect that no custom element reaction would fire beyond handful of DOM functions like appendChild, setAttribute, cloneNode, etc... Oh actually, this behavior is expected. You need to insert the imported node into a document since upgrading now happens when an element is connected, not when it's instantiated. On my second thought, we should probably just fix the spec so that this case works. This has been fixed in https://trac.webkit.org/changeset/207170. |