Thanks Paul. This (very usefull experiment ) shows mutation events "faking", using jQuery. What I am talking about is jQ 1.5 implementing and relying on mutation events internal "infrastructure" to solve the problems that MutationEvents are solving : CRUD operations on the persistent storage (dom document in this context) by two or more "simultaneous" visitors, in this context two or more jquery instances. Like depicted in my imaginary example. This would require conformance to DOM Level 2 MutationEvent interface, etc...
The implementation effort, may be great indeed, but I think this is doable. I think the performance hit of this might be much bigger challenge to solve than actual implementation. And this will be very usefull, just as jQ is usefull to deal with parts of DOM that are alreay there, but not universaly supported and not encapsulated behind one JavaScript API. As an closest example to this discussion, remember the w3c Event object, which is available "everywhere", for jQ users. --DBJ -- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-...@googlegroups.com. To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en.
