I had written a Mutation events tester... the code is on my machine at home and I'm at the office.
But this where I started: http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113/events.html#Events-eventgroupings-mutationevents On Thu, Jan 14, 2010 at 1:37 PM, Allen Madsen <bla...@gmail.com> wrote: > Matti, is talking about cross browser support. Not all of the mutation > methods are supported by all the browsers. It would be nice if prototype > provided a common way to use these methods even though they are not fully > supported on each browser. > > Allen Madsen > http://www.allenmadsen.com > > > On Thu, Jan 14, 2010 at 12:12 PM, Rick Waldron <waldron.r...@gmail.com>wrote: > >> Supported* >> >> >> On Thu, Jan 14, 2010 at 12:12 PM, Rick Waldron <waldron.r...@gmail.com>wrote: >> >>> I've used all of the support Mutation Events with $(document).observe() >>> without changing anything in Prototype. >>> >>> >>> >>> >>> >>> >>> On Thu, Jan 14, 2010 at 7:23 AM, Allen Madsen <bla...@gmail.com> wrote: >>> >>>> I wouldn't mind if this made it into core either. >>>> >>>> Allen Madsen >>>> http://www.allenmadsen.com >>>> >>>> >>>> On Tue, Jan 12, 2010 at 3:21 PM, matti <matti.t.jarvi...@gmail.com>wrote: >>>> >>>>> Is there a reason why Prototypejs doesn't fire mutation events >>>>> ( >>>>> http://www.w3.org/TR/DOM-Level-2-Events/events.html#Events-eventgroupings-mutationevents-h3 >>>>> ) as custom events (like dom:subtreemodified) when using >>>>> Element.update and Element.insert? >>>>> >>>>> I know that browser support for those events are lacking but I'd >>>>> believe that DOMSubtreeModified, DOMNodeInsertedIntoDocument and >>>>> DOMAttrModified would be easy to implement as custom events (or >>>>> simulated as such if browser has support for them) and could add value >>>>> preventing memory leaks on AJAX heavy UIs. >>>>> >>>>> Point in all this would be that it would be easier to handle >>>>> Event.stopObserving. >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Prototype: Core" group. >>>>> To post to this group, send email to prototype-core@googlegroups.com >>>>> To unsubscribe from this group, send email to >>>>> prototype-core-unsubscr...@googlegroups.com >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/prototype-core?hl=en >>>>> >>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Prototype: Core" group. >>>> To post to this group, send email to prototype-core@googlegroups.com >>>> To unsubscribe from this group, send email to >>>> prototype-core-unsubscr...@googlegroups.com >>>> For more options, visit this group at >>>> http://groups.google.com/group/prototype-core?hl=en >>>> >>> >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Prototype: Core" group. >> To post to this group, send email to prototype-core@googlegroups.com >> To unsubscribe from this group, send email to >> prototype-core-unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/prototype-core?hl=en >> > > > -- > You received this message because you are subscribed to the Google Groups > "Prototype: Core" group. > To post to this group, send email to prototype-core@googlegroups.com > To unsubscribe from this group, send email to > prototype-core-unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/prototype-core?hl=en >
-- You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to prototype-core-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en
