3 ms·
Very nice. Here’s just a small thing I’d change: You update the url using backbones router.navigate, right? If you pass {replace: true} in the options object, t
by benelsen 14y ago
Very nice.
Here’s just a small thing I’d change:
You update the url using backbones router.navigate, right?
If you pass {replace: true} in the options object, the browser won’t create a new entry in the history as it does right now but still update the URL.
http://documentcloud.github.com/backbone/#Router-navigate http://documentcloud.github.com/backbone/#Router-navigate
- muellerwolfram 14y agoyes, exactly, that's how i do it. maybe i'm missing something, but why do you suggest not making an entry in the history?
- burriko 14y agoThe user is scrolling one long page, not navigating between 'pages'. Having entries inserted into the history while scrolling seems very counter-intuitive to me.
- muellerwolfram 14y agomh yes that makes sense. i think the reason why i did this, was because initially the preview und market links didn't open in a new window. but you're right, if the user is staying on one page, he doesnt need a 'back' functionality. thanks for the feedback, i already changed it, going to push it later...