Re: [whatwg/dom] Adoption and DocumentFragment, part two (#819)

@jded76 commented on this pull request.



> + <li>
+  <p>If <var>node</var> is a {{DocumentFragment}} <a for=/>node</a> and its
+  <a for=DocumentFragment>host</a> is non-null, then return <var>node</var>.
+
+  <p class=note>Unfortunately this does not throw for web compatibility.

> From reading the issue you linked it seems that implementations never matched the specification and some applications (such as yours) relied on that. 
That's not true. The implementations were according to the spec until #754, that inserted a rule about template's fragment for the first time. 
That rule returned undefined, there were some issues with that and the browsers didn't implemented (according to [this ](https://github.com/whatwg/dom/issues/813#issuecomment-570191640).
Then with #819 the spec changed again. 
On July webkit implemented the new rule. Before one month Safari went public with the new version of webkit and many applications broke on **production**.
And since then we are trying to figure out what's going on.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/pull/819#discussion_r1006583041
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/dom/pull/819/review/1157857688@github.com>