[Webkit-unassigned] [Bug 183583] connectedCallback called when disconnected

[bugzilla-daemon at webkit.org]

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

--- Comment #4 from Justin Ridgewell <jridgewell at google.com> ---
I forgot to link the Chrome bug I also filed: https://bugs.chromium.org/p/chromium/issues/detail?id=821195&desc=2

They closed as a won't fix, for this specific case (reparenter and child with disconnectedCallback, let's call this Case A). However, there's a [similar case](https://bugs.webkit.org/show_bug.cgi?id=183586) (reparenter and child _without_ disconnectedCallback) that shouldn't cause the bad behavior (let's call this Case B).

Chrome thinks Case A should fire when disconnected, and not fire in Case B.
Safari (currently) thinks both Cases should fire.
Firefox thinks neither Case should fire.

In all, it's very confusing to me why these Cases should be different. And given the browser disagreement, it's probably confusing to everyone else too.


Case A: https://output.jsbin.com/qumape/3/quiet
Case B: https://output.jsbin.com/qumape/7/quiet

-- 
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/20180521/c1ddda37/attachment.html>