If we can get away with it WRT web compat, we should make createContextualFragment work context-less and we should make DocumentFragment.innerHTML work as Yehuda describes. There are clear use-cases for this that web devs want to do all the time. I don't see any downside except if the web already depends on the current behavior of these two cases throwing an error. On Thu, Nov 3, 2011 at 4:53 PM, Tim Down <timdown@gmail.com> wrote: > Yes, now I re-read it, that's clear. Sorry. > > Tim > > On 3 November 2011 23:51, James Graham <jgraham@opera.com> wrote: > > On Thu, 3 Nov 2011, Tim Down wrote: > > > >> Have you looked at the createContextualFragment() method of Range? > >> > >> > http://html5.org/specs/dom-parsing.html#dom-range-createcontextualfragment > > > > That doesn't meet the use case where you don't know the contextual > element > > upfront. As I understand it that is important for some of the use cases. > > > > I think this is possible to solve, but needs an extra mode in the parser. > > Also, createcontextualFragment could be modified to take null as the > context > > to work in this mode. > > > >
Received on Thursday, 3 November 2011 23:59:37 UTC