Hacker News new | past | comments | ask | show | jobs | submit login

This page will wreck your browser history. The post explains the rationale at the end, but frankly speaking there should have been the warning for each checkbox.



Your comment made me realize that there are people who curate their browser history (other than just removing problematic stuff). Not criticizing, just never considered that was something anyone cared about.


If you curate your browser history, this is an easy fix. This is more of a problem for people like me who occasionally check their browser history because they want to revisit a site they were on recently.


It made the back button useless for me.


I didn't experience that using Chrome. What browser are you using?


Happened to me with Chrome on OS/X - no way back!


Chrome on Android for me. Had to close the tab.


I had this problem in Chrome on linux.


Same with Firefox on Android.


If you're using Firefox you can Control+H then right click on the site and select the option labeled "Forget About This Site". Done.


Wow, that took multiple minutes to run here.

Well done to the author of this hack on finding a way to dump massive amounts of data to firefox's sqlite store.


Not tackling the same problem but in the spirit of removing things and Firefox, you can bring up a url in the address bar, press down arrow, press Delete, and it'll go away

It only deletes that very specific url though, like foo.com, however foo.com/bar will still exist


I think that only works before Sync replicates all those crufts to every other device.


I’m on mobile. The checkboxes had no effect, the code run on its own by default. And I gave up on trying to go back to Lobsters by using the Back button.


It shouldn't. It uses history.replaceState(). https://developer.mozilla.org/en-US/docs/Web/API/History_API...


It actually just updates window.location.hash instead, which does cause a flood of history entries (looks like just one per distinct animation state, though, at least in Chrome). See the "One Last Thing" section near the bottom of the article for the rationale. See the inline code snippets in the article, or view source for wavyurl.com to see the actual code used.


At least in Safari, history.replaceState() still pollutes the browser history, all it does is avoid breaking the back button.


I think it also crashed LittleSnitch




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: