documentcloud/backbone — Issue #799: pushState difference in iframe between Chrome and FF
Author: cmaxo
Created: 2011-12-19 16:50:34+00:00
State: open

I've noticed a difference in the ability to use the pushState feature of Backbone.history. I'm running an application inside Facebook which means it's running inside of an iframe. When the application is running in Firefox the browser's back button works correctly given what the History's navigate function adds to window.history.pushState. However, when the application runs in Chrome the browser's back button does not respond to what History's navigate function adds to window.history.pushState.

This issue does not manifest itself when running as a standalone application, outside of the iframe. The same issue is seen using Safari so I'm guessing it's a webkit browser issue. My question then is this: Is this a browser bug or is there some way I can use Backbone's history to get the correct correct back button response in webkit browsers while the application is running in an iframe?

Thanks,
cmaxo