Re:Lossless Web Navigation with Trails
by DennisP on Monday January 30, 2017 @08:01AM
(#13520754)
That's what I was thinking. Don't need fancy graphics, just make the back button work further back than the tab creation. Doesn't even have to be a copy, if they make the history a tree structure in memory.
[ Parent
| on HN ]
Re:Lossless Web Navigation with Trails
by tschneidereit on Monday January 30, 2017 @09:54AM
(#13521609)
That last part doesn't work, unfortunately. We looked into doing exactly that, but the way history navigation works is specified quite strictly - and relied upon by existing web content - making this infeasible.
I don't see how this could be true. From the perspective of a web page, it'd be exactly the same as if the user's new-tab clicks were regular clicks instead.
From a user perspective, my main pain point is the prior history running out at the point where I opened a new tab. In many cases I've already closed the tab it came from, and if it's not closed I have to go looking for it.
Re:Lossless Web Navigation with Trails
by gm-conspiracy on Monday January 30, 2017 @08:28AM
(#13520930)
This seems like the most simple solution.
Are there any disadvantages to this approach?
Re:Lossless Web Navigation with Trails
by tschneidereit on Monday January 30, 2017 @09:52AM
(#13521586)
See my reply in another conversation thread: https://news.ycombinator.com/item?id=13520978