Now onScroll uses debounce on saveHistory

[diegonvs]

When CI run my tests on #232, it catches some errors that being shown below:

I've noticed that replaceState security error is caused by spamming scroll event when updating history state. Using debounce we can reduce the occurrence of replaceState event and solve this Security Error.

[eduardolundgren]

This will cause issues. The scroll snapshot must happen synchronously, adding a debounce will cause intermittent issues. In the past we've tried this approach.

[diegonvs]

Hey @eduardolundgren, which issues this modification will cause? I've noticed that people using others libs (e.g Ember, react-router, dom-to-img) are getting same errors[1][2][3] and they are getting some manners to solve this, but i think that reload page and emit warnings may be bad SPA experience to user.

• Fix these issues that will be caused by debouncing
• Emit a warning when we encounter this exception
• Provide an option that reloads the page when we encounter this exception
• Remove support for Safari (this is probably the worst manner to solve this)