[Webkit-unassigned] [Bug 183931] New: Custom Elements connectedCallback invoked always after DOMContentLoaded

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=183931

            Bug ID: 183931
           Summary: Custom Elements connectedCallback invoked always after
                    DOMContentLoaded
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Event Handling
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: andrea.giammarchi at gmail.com

Accordingly with this Chromium bug:
https://bugs.chromium.org/p/chromium/issues/detail?id=821831

It looks like Webkit/Safari have a bug related to Custom Elements and their connectedCallback invoke,
always triggered *after* DOMContentLoaded, even if the definition of the element is known,
and the page is also already served.

Accordingly, using this test page as reference:
https://webreflection.github.io/eyeo/tests/ce.html

The correct result should most likely the following one:
```
constructor: 0
attributeChangedCallback: 0
a
b
c
connectedCallback: 3
ready: 3
```

In Webkit/Safari the result is instead this one:
```
constructor: 0
a
b
c
ready: 3
attributeChangedCallback: 3
connectedCallback: 3
```

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180323/e341e242/attachment.html>