Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Added a change event to the editor #50
I was looking into this as well. I think this needs a bit more love :) I'm travelling today so I won't be able to complete it, but I was thinking about caching the old version and actually comparing it with the current one before triggering change. this should prevent multiple fake triggers and preventing events that don't change content
I understand the need to make it as accurate as possible. I am worried about holding onto the old value though. If there are a couple of images in the editor then it could be multiple MBs being stored and compared. That could be slow and consume a decent chunk of memory.