- From: Travis Leithead <notifications@github.com>
- Date: Fri, 03 Jun 2016 14:08:27 -0700
- To: w3c/DOM-Parsing <DOM-Parsing@noreply.github.com>
- Cc:
Received on Friday, 3 June 2016 21:08:55 UTC
I looked into innerHTML and confirmed the problem; outerHTML is protected because it uses the parent of the context object (though Chrome throws when the parent is a document fragment). insertAdjacentHTML is [oddly] interoperable in that it doesn't special-case `<template>`. I also don't think there can be a problem with createContextualFragment because it only returns the DocumentFragment and doesn't actually change the DOM. @annevk please take a look at the PR to see if it can be improved. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/DOM-Parsing/issues/1#issuecomment-223694977
Received on Friday, 3 June 2016 21:08:55 UTC