3 ms·
Sure -- it depends where you draw the line for "acceptable", and how much you care about the experience of your IE users. In any single-page web app of signific
by jashkenas 15y ago
Sure -- it depends where you draw the line for "acceptable", and how much you care about the experience of your IE users. In any single-page web app of significant size, I'd argue that it's never acceptable to do a full page refresh. Would you really want to go back to a GMail that refreshed when you clicked around between labels?
Regarding (2): hash-based URLs also work perfectly well for older browsers.
- catshirt 15y agoyou're right, "acceptable" is subjective. but it doesn't seem unreasonable that if you are using an outdated version of a program, it will not perform optimally. to that end, managing both pushState and hashchange adds overhead and complexity. personally, i don't think enhancing old browsers is worth said overhead. that said, if it was part of a framework i was using anyway, overhead and complexity are much less of an issue, so the question becomes "why not".