The popstate only contains a state when there is one. When it goes like this: initial page loaded new page loaded, with state added via pushState back button pressed then there is no state, because the initial page was loaded regularly, not with pushState. As a result, the onpopstate event is fired with a state … Read more
Is pushState bad if you need search engines to read your content? No, the talk about pushState is geared around accomplishing the same general process to hashbangs, but with better-looking URLs. Think about what really happens when you use hashbangs… You say: With hashbangs, Google knows to go to the escaped_fragment URL to get their … Read more
Is pushState bad if you need search engines to read your content? No, the talk about pushState is geared around accomplishing the same general process to hashbangs, but with better-looking URLs. Think about what really happens when you use hashbangs… You say: With hashbangs, Google knows to go to the escaped_fragment URL to get their … Read more
While #2 might be “easier” for you as a developer, it only provides search engine crawling. And yes, if Google finds out your serving different content, you might be penalized (I’m not an expert on that, but I have heard of it happening). Both SEO and accessibility (not just for disabled person, but accessibility via … Read more
You must implement it yourself which is quite easy. When invoking pushState give the data object a unique incrementing id (uid). When onpopstate handler is invoked; check the state uid against a persistent variable containing the last state uid. Update the persistent variable with the current state uid. Do different actions depending on if state … Read more
Make sure you are following the Same Origin Policy. This means same domain, same subdomain, same protocol (http vs https) and same port. How does pushState protect against potential content forgeries? EDIT: As @robertc aptly pointed out in his comment, some browsers actually implement slightly different security policies when the origin is file:///. Not to … Read more
Probably the best site for browser compatibility information is CanIUse. Here’s the section on history. Summary – IE9: no, IE10: yes (as of platform preview 3) The first Release Candidate of IE9 (released 10th Feb 2011) does not support history.pushState or history.replaceState. Generally no new features are added after a product gets to RC stage … Read more
5.5.9.1 Event definitions The popstate event is fired in certain cases when navigating to a session history entry. According to this, there is no reason for popstate to be fired when you use pushState. But an event such as pushstate would come in handy. Because history is a host object, you should be careful with … Read more
For a great tutorial the Mozilla Developer Network page on this functionality is all you’ll need: https://developer.mozilla.org/en/DOM/Manipulating_the_browser_history Unfortunately, the HTML5 History API is implemented differently in all the HTML5 browsers (making it inconsistent and buggy) and has no fallback for HTML4 browsers. Fortunately, History.js provides cross-compatibility for the HTML5 browsers (ensuring all the HTML5 browsers … Read more
It’s very easy to solve it without url hacks, with CloudFront help. Create S3 bucket, for example: react Create CloudFront distributions with these settings: Default Root Object: index.html Origin Domain Name: S3 bucket domain, for example: react.s3.amazonaws.com Go to Error Pages tab, click on Create Custom Error Response: HTTP Error Code: 403: Forbidden (404: Not … Read more