Re: [whatwg] documentFragment and innerHTML

WebKit already has insertAdjacentHTML support. On Feb 26, 2011, at 4:47 PM, Aryeh Gregor wrote: > On Sat, Feb 26, 2011 at 9:52 AM, Rafael Holt wrote: >> Yes, I had just never heard of insertAdjacentHTML(), since it doesn't enjoy >> Webkit or Gecko support. Once it does though, I agree it's a

Re: [whatwg] documentFragment and innerHTML

On Sat, Feb 26, 2011 at 9:52 AM, Rafael Holt wrote: > Yes, I had just never heard of insertAdjacentHTML(), since it doesn't enjoy > Webkit or Gecko support. Once it does though, I agree it's a nice addition. > > As for createContextualFragment(), it bring unnecessary complexity to this, > having t

Re: [whatwg] Optional non-blocking mode for simple dialogs (alert, confirm, prompt).

On Sat, Feb 26, 2011 at 2:29 PM, Ben Rimmington wrote: > > > An optional callback parameter could be added to the simple dialogs API: > >> result = window.alert(message, [callback]); >> >> result = window.conf

[whatwg] Optional non-blocking mode for simple dialogs (alert, confirm, prompt).

An optional callback parameter could be added to the simple dialogs API: > result = window.alert(message, [callback]); > > result = window.confirm(message, [callback]); > > result = window.prompt(message, [

Re: [whatwg] The choice of script global object to use when the script element is moved

On Wed, Feb 2, 2011 at 5:48 AM, Henri Sivonen wrote: > On Feb 2, 2011, at 03:07, Ian Hickson wrote: > >> I suppose we could make it so that scripts get neutered when the document >> that they were first associated with gets unloaded. Would that work? > > We did something different. > >> Proposal #

Re: [whatwg] documentFragment and innerHTML

On Fri, Feb 25, 2011 at 4:18 PM, Boris Zbarsky wrote: > If you want to parse this string: > > Some text > > then the DOM it produces depends on whether it's being parsed in the context > of a parent element or not. Try setting the innerHTML of a > and a to the above string, and examine the re