For keeping the events, the easiest solution would be to store the events in local storage.
For reinjecting the script… This can get messy. Would be extremely nice if Selenium driver had a page refresh event or something, but don't think so. In this case we could ask the user to reinject the events detection script manually, but that's a bit much overhead for my taste.
Also need to consider the time taken to switch pages. Assuming there are stuff to load, this is non-deterministic. In most cases putting a live screenshot point before and after clicking works, but it's not 100% reliable. Edit: there seems to be a WebDriverWait for Selenium; this could be extremely handy providing that there's the node counterpart. Really wish they could start documenting their code because plowing through it wasn't fun.
Formal ideas to solve #7.
For keeping the events, the easiest solution would be to store the events in local storage.
For reinjecting the script… This can get messy. Would be extremely nice if Selenium driver had a page refresh event or something, but don't think so. In this case we could ask the user to reinject the events detection script manually, but that's a bit much overhead for my taste.
Also need to consider the time taken to switch pages. Assuming there are stuff to load, this is non-deterministic. In most cases putting a live screenshot point before and after clicking works, but it's not 100% reliable. Edit: there seems to be a
WebDriverWaitfor Selenium; this could be extremely handy providing that there's the node counterpart. Really wish they could start documenting their code because plowing through it wasn't fun.