Write code that is easy to delete, not easy to extend (2016)

Re:Write code that is easy to delete, not easy to extend (2016) by anuila on Wednesday November 04, 2020 @12:07PM (#24990848)

I’d have another suggestion: Don’t break the back button on your CSS-free blog.

This is arguably easy to avoid, yet people manage to do it.

[ Parent | on HN ]

Re:Write code that is easy to delete, not easy to extend (2016) by hundchenkatze on Wednesday November 04, 2020 @12:48PM (#24991281)

In what way is it broken? I was able to follow several links on their site and then use the browser's back button to get back to HN.

[ Parent | on HN ]

Re:Write code that is easy to delete, not easy to extend (2016) by Jtsummers on Wednesday November 04, 2020 @12:53PM (#24991324)

In Safari (iPadOS), I couldn’t get out of the site using the back button (unless I hit it fast enough to get past whatever it was doing to the browser history).

[ Parent | on HN ]

Re:Write code that is easy to delete, not easy to extend (2016) by hundchenkatze on Wednesday November 04, 2020 @02:23PM (#24992164)

Interesting, it works fine on Firefox. I was able to reproduce it using Safari. After poking around I noticed it's a tumblr blog, so I tried some other tumblr blogs with the same result. It seems Tumblr's nav code does not get along with Safari/Webkit.

[ Parent | on HN ]

Re:Write code that is easy to delete, not easy to extend (2016) by Jtsummers on Wednesday November 04, 2020 @02:43PM (#24992360)

Thanks. That's good to know for the future, at least when I can easily identify something as a Tumblr blog. At least this wasn't one of the more egregious browser history hijacking situations. I've been on some sites that polluted the browser history as I scrolled through the page (each subheading coming into view got an entry). Two quick taps of the back button was enough to get around this one.

[ Parent | on HN ]