>Yep, Firefox 3.6.24. The most up to date one on the version of Linux that I'm using at work. I'm not sure why you/backbone need to rewrite the URL though - surely a vanilla page would work just as well?
It's not really that simple, it has to do with how Backbone falls back when the pushState functionality is missing and how it interacts with the structure of our site. We're currently looking into better ways to shim/workaround this somewhat lackluster default functionality.
>I understand compliance, allergies etc. are a tricky issue. There a more narrow disclaimer and/or warning (eg. this recipe contains nuts/gluten/...) would be definitely appropriate, not to mention useful if it were on the actual recipe page.
I just listen to the lawyers (and my CEO) on these matters. My job is to build product to help people.
>In that case the disclaimers completely overstep the mark, and undermine any claims of competence. Would you trust an engineer who disclaimed all liability should their bridge fall down? Or a doctor who wanted you to waive the right to all negligence suits?
Would you refuse to work with a doctor because he had malpractice insurance or an engineer because he worked through an LLC? It would be irresponsible for either of them to do without.
You seem to act as if our terms of use is somehow extraordinary when it is anything but.
I'm not here to debate hypothetical circumstances, just make things to help people.
Let me know if you want a beta invite via my email address so you can decide for yourself.
One solution to the lack of pushState is to just offer the non-JS version of your website to such old browsers. Easiest way to do that is to have the JS bits disable themselves if pushState isn't found.
Or, you know, just use regular links. That part of the site isn't a web app, it's just a regular web page. Why make things more complicated than they have to be?
edit: Particularly when I just tried it at home in Chrome, and it ended up at http://www.nutrivise.com/terms/ anyway. Or did you come to the same conclusion re: links?
It's not really that simple, it has to do with how Backbone falls back when the pushState functionality is missing and how it interacts with the structure of our site. We're currently looking into better ways to shim/workaround this somewhat lackluster default functionality.
>I understand compliance, allergies etc. are a tricky issue. There a more narrow disclaimer and/or warning (eg. this recipe contains nuts/gluten/...) would be definitely appropriate, not to mention useful if it were on the actual recipe page.
I just listen to the lawyers (and my CEO) on these matters. My job is to build product to help people.
>In that case the disclaimers completely overstep the mark, and undermine any claims of competence. Would you trust an engineer who disclaimed all liability should their bridge fall down? Or a doctor who wanted you to waive the right to all negligence suits?
Would you refuse to work with a doctor because he had malpractice insurance or an engineer because he worked through an LLC? It would be irresponsible for either of them to do without.
You seem to act as if our terms of use is somehow extraordinary when it is anything but.
I'm not here to debate hypothetical circumstances, just make things to help people.
Let me know if you want a beta invite via my email address so you can decide for yourself.