You cannot post messages because only members can post, and you are not currently a member.
|
Ability to rollback and replay Mutation Summaries
|
| |
Hi, this is a great library btw, and I'm currently trying to use it to enhance a collaborative rich text editor. I'm just wondering though if the mutation summaries or lower level records provide enough info to allow them to be rolled back in the DOM, so that it's restored to an earlier state (eg. undo), and then later re-apply the... more »
|
|
summarise the summaries
|
| |
Really great job with the library! I've been wondering though if there is a reasonable way at the moment to summarise the mutation summaries. Since the mutation observer callback is basically fired at will, so is mutation summary callback. Is there a way to have some more control over when it happens? For example, I might want to... more »
|
|
Opera support
|
| |
Any insider info? I've tried to cause a raucous in dev.opera (oxymoron if I ever used one) about this before to no avail... If someone would just kick them hard enough maybe I could forget MutationEvents for good!
|
|
Possible bug, or missuage of the API?
|
| |
I'm trying to work out if I've triggered a bug or mis-understanding the API usage. I've written a test page for my extension which simulates DOM manipulation to ensure I tag text areas correctly: [link] One of the problems I have to deal with is over-exuberant DOM... more »
|
|
tree mirror; possible to bidirectionally share changes?
|
| |
hey Rafael, this library is _amazing_. Thanks for creating it! I have a question about mutation summary, and the tree mirror example. I'm wondering if you could provide some insight into what would be involved in making it so 2 or more viewers could share edits to a DOM. Said differently, in the example, one... more »
|
|
Trying to understand the observeOwnChanges option
|
| |
I'm trying to understand the purpose of the observeOwnChanges option. Looking at the Mutation Summary source, it seems that if observeOwnChanges is set to false, then anytime the Mutation Observer API executes the callback, it disconnects the observer after pulling the mutations, creates summaries from them, returns those summaries inside the passed callback,... more »
|
|
Change in offsetTop value doesn't register
|
| |
What a great script!!! So many thanks for building/implementing
this!!!
I want to use it to monitor the offset of inputs on a webform. So far,
I was able to register changes in styles, but I just don't get alerted
when the offset value changes.
Here is my test page:
[link]... more »
|
|
Issues in mutation-summary
|
| |
I just developed a Chrome extension that makes use of mutation-summary: [link] I encountered this issue during the development: Nodes found by a characterData query may not be text nodes. They can be comment nodes, or their parent nodes can be <style> and <script>.... more »
|
|
Removed nodes and Mutation Summary
|
| |
Hi Clemens, Interesting use case. Thanks for making contact. [Note that I have updated mutation-summary-discuss so that anyone can join and cc'd there so that everyone can have the benefit of this discussion]. I had wondered if this issue would come up. You are correct that internally, for nodes which have been moved, the library is tracking... more »
|
|
|