Timeline for How can a userscript detect when a post's been edited in place, so that it can do stuff to the newly edited post?
Current License: CC BY-SA 3.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 23, 2017 at 12:39 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
Apr 12, 2016 at 9:25 | vote | accept | doppelgreener | ||
Dec 5, 2016 at 18:52 | |||||
Jan 14, 2015 at 5:25 | history | edited | Brock Adams | CC BY-SA 3.0 |
added 1 character in body
|
Jan 14, 2015 at 5:24 | comment | added | Brock Adams |
Found an event that's close to what we want and added code showing how to exploit it. Note that it is less impactful, on average, than the simple timer (which has no human-noticeable impact on performance), and much less peak impact than rojo's raw MutationObserver approach (which needs tuning and targeting). But this kind of code is also more complicated and brittle.
|
|
Jan 14, 2015 at 5:06 | history | edited | Brock Adams | CC BY-SA 3.0 |
added 1745 characters in body
|
Jan 14, 2015 at 1:32 | history | edited | Brock Adams | CC BY-SA 3.0 |
[Edit removed during grace period]
|
Jan 14, 2015 at 1:24 | history | edited | Brock Adams | CC BY-SA 3.0 |
[Edit removed during grace period]
|
Jan 11, 2015 at 13:57 | comment | added | rojo |
I use MutationObserver to watch the document root and reapply event handlers in my stuff. It's flawless as far as I can tell. MutationObserver is the correct answer I think.
|
|
Jan 10, 2015 at 21:00 | comment | added | Brock Adams |
You could try MutationObserver s, but I think you'll find that they get pretty fiddly/brittle for this kind of thing.
|
|
Jan 10, 2015 at 15:24 | comment | added | doppelgreener | This is definitely a reliable solution, though I'm hoping there's some more precise way to handle it. | |
Jan 10, 2015 at 10:31 | history | answered | Brock Adams | CC BY-SA 3.0 |