Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option to automatically redirect to snapshot after archiving #133

Open
bnvk opened this issue Mar 5, 2018 · 2 comments
Open

Add option to automatically redirect to snapshot after archiving #133

bnvk opened this issue Mar 5, 2018 · 2 comments

Comments

@bnvk
Copy link
Contributor

bnvk commented Mar 5, 2018

As a user, I would like to be able to "jump" to a snapshoted URL immediately after the snapshot finishes. I believe this has multiple benefits:

  • Stops various trackers on a given page from recording time on page
  • Minimize CPU / mem use from JS heavy pages

Ideally this would be an option that could be enabled / disabled.

@Treora
Copy link
Collaborator

Treora commented Aug 6, 2018

Sounds like turning the tool in a sort of reader mode, interesting.. If this seems a broader desire (add a thumbs up if you want this) it may be worth adding, though to me personally I have found the two required clicks (open snapshot, close other tab) an acceptable effort so far when this behaviour is desired.

I suppose other UX design choices may also influence the behaviour still; perhaps clicking a listed snapshot date should open it in the same tab, thus reducing the effort to one click.

@bnvk
Copy link
Contributor Author

bnvk commented Aug 21, 2018

It is actually three clicks (1 take snapshot, 2 to visit snapshot, 3 to close previous tab). I'm proposing 1 click. Those additional 2 clicks add up over months, years. Yes,

perhaps clicking a listed snapshot date should open it in the same tab

Would be an improvement :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants