W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2012

Re: [UndoManager] Re-introduce DOMTransaction interface?

From: Ryosuke Niwa <rniwa@webkit.org>
Date: Fri, 6 Jul 2012 16:53:26 -0700
Message-ID: <CABNRm61_VunZ_EOiBfpSbB2HuU26ka8KgSgEOgHzA-Dxz3LaBw@mail.gmail.com>
To: Jonas Sicking <jonas@sicking.cc>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, public-webapps@w3.org
On Jul 6, 2012 4:48 PM, "Jonas Sicking" <jonas@sicking.cc> wrote:
>
> On Fri, Jul 6, 2012 at 3:18 PM, Ryosuke Niwa <rniwa@webkit.org> wrote:
> >
> > On Jul 6, 2012 3:06 PM, "Boris Zbarsky" <bzbarsky@mit.edu> wrote:
> >>
> >> On 7/5/12 3:05 PM, Ryosuke Niwa wrote:
> >>>
> >>> Also, I think consistency matters a lot here. I'm not aware of any
other
> >>> Web-facing API that takes a pure object with callback functions.
> >>
> >>
> >>
> >>
http://www.w3.org/TR/DOM-Level-2-Traversal-Range/traversal.html#Traversal-NodeFilter
> >> (the acceptNode function).
> >>
> >> Or was the point about having multiple callback functions?
> >
> > Precisely about having multiple callback functions.
> >
> > Also to respond to some of earlier comments, I don't think most web
> > developers think of passing objects when adding event listeners.
>
> Why does having one callback function rather than two make
> implementation harder?

Because we can implement it as a special event listener.

But the difficulty in implementing it correctly in WebKit isn't main point.
The inconsistency with other DOM API is.

- Ryosuke
Received on Friday, 6 July 2012 23:53:53 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:53 GMT