top | item 43843520 (no title) nexle | 10 months ago slightly off topic but it should be a crime for a website hijacking the back button discuss order hn newest pif|10 months ago It should be a crime for web browser letting the back button be hijacked in the first place! kazinator|10 months ago It shuld be a crime for web browsers to download and execute code as a matter of loading a page. arp242|10 months ago Nothing is "hijacked"; it just sets the hash to allow permalinks. It should probably actually load the state when pressing back (or replace the current entry instead of adding a new one). But that's just a bug and not malice, as some seem to assume. hoten|10 months ago It actually is augmenting the history so "hijack" is correct.Weird that back isn't restoring the state. Just stays the same for me.
pif|10 months ago It should be a crime for web browser letting the back button be hijacked in the first place! kazinator|10 months ago It shuld be a crime for web browsers to download and execute code as a matter of loading a page.
kazinator|10 months ago It shuld be a crime for web browsers to download and execute code as a matter of loading a page.
arp242|10 months ago Nothing is "hijacked"; it just sets the hash to allow permalinks. It should probably actually load the state when pressing back (or replace the current entry instead of adding a new one). But that's just a bug and not malice, as some seem to assume. hoten|10 months ago It actually is augmenting the history so "hijack" is correct.Weird that back isn't restoring the state. Just stays the same for me.
hoten|10 months ago It actually is augmenting the history so "hijack" is correct.Weird that back isn't restoring the state. Just stays the same for me.
pif|10 months ago
kazinator|10 months ago
arp242|10 months ago
hoten|10 months ago
Weird that back isn't restoring the state. Just stays the same for me.