zlacker

[parent] [thread] 5 comments
1. dylan6+(OP)[view] [source] 2020-11-29 01:04:56
>make me click the back button

I forget about the back button. By default, I always open links in new tabs which means back button has no data. Also, SPAs have hijacked the back button or just broken it completely, so I've been trained to not count on it behaving as expected. There's also mobile experience where getting to the back button itself is often painful after the UI hides navigation from you.

Otherwise, I am 100% in agreement. If a page is so user hostile to not making a friendly non-JS page, the tab gets closed

replies(2): >>dragon+31 >>ehutch+J51
2. dragon+31[view] [source] 2020-11-29 01:16:20
>>dylan6+(OP)
> By default, I always open links in new tabs which means back button has no data.

I really wish, even if it was an optional setting, browsers would copy the past history of the source tab when you did that. If it hit back in a tab I opened that way, I still want “where I got here from” not “stay here” or “new tab page" or especially “close the tab” (thanks a lot Android Chrome).

replies(2): >>abhina+h2 >>deergo+r5
◧◩
3. abhina+h2[view] [source] [discussion] 2020-11-29 01:31:16
>>dragon+31
That sounds like an amazing idea that they should implement!
◧◩
4. deergo+r5[view] [source] [discussion] 2020-11-29 02:07:31
>>dragon+31
Safari does this, at least on iOS. If you open a new tab, then hit back, it just closes the tab and takes you back to the origin tab. If you’ve closed the origin tab, it leaves the active tab open but goes back to what the origin tab was.
replies(1): >>kitsun+yi
◧◩◪
5. kitsun+yi[view] [source] [discussion] 2020-11-29 05:42:19
>>deergo+r5
The macOS version has this behavior as well.
6. ehutch+J51[view] [source] 2020-11-29 16:47:02
>>dylan6+(OP)
If an SPA is hijacking your back button it is poorly coded and the coders should be ashamed.
[go to top]