4 ms·

This spams your browser history something fierce. Can that be optional?

• Orou 6y ago
  Agreed, it's a neat little app but having URL parameters work like this is very anti-user.
  • neolog 6y ago
    Disagree. The app's url scheme is stateless, which is great. Linear views of browser history is the problem.
    • javawizard 6y ago
      The problem is not so much that it stores state in the URL as that it uses window.history.pushState instead of window.history.replaceState.
    • quickthrower2 6y ago
      Do we really want to push the Git way of thinking onto joe-average web user.
      • deleted 6y ago
        [deleted]
    • Orou 6y ago
      How something functions is more important that how it is implemented. I'll take a stateful app that doesn't break history over a stateless app that does any day of the week.
• lol768 6y ago
  It's not implemented correctly: function t() { b().then(function (e) { n.search('borders', e) }) } o.$watch('map.borders', t, !0), triggers a pushState instead of a replaceState. The fix is straight-forward, I think: function t() { b().then(function (e) { n.replace() n.search('borders', e) }) } o.$watch('map.borders', t, !0),