proposed solution to the navigate, refresh, back button pushstate bug. the determination of the hash to be stored in the replaced state is done in a consistent fashion where, if there is no hash, its defaulted to the original load path by puting the logic in a central method. @scottjehl give it a try and let me know if this works for you
proposed solution to the navigate, refresh, back button pushstate bug. the determination of the hash to be stored in the replaced state is done in a consistent fashion where, if there is no hash, its defaulted to the original load path by puting the logic in a central method. @scottjehl give it a try and let me know if this works for you

npmcomponent/cbou-jquery-mobile,startxfr/jquery-mobile,hinaloe/jqm-demo-ja,npmcomponent/cbou-jquery-mobile,startxfr/jquery-mobile,rwaldron/jquery-mobile,arschmitz/uglymongrel-jquery-mobile,arschmitz/jquery-mobile,arschmitz/uglymongrel-jquery-mobile,hinaloe/jqm-demo-ja,arschmitz/jquery-mobile,hinaloe/jqm-demo-ja,arschmitz/jquery-mobile,rwaldron/jquery-mobile,arschmitz/uglymongrel-jquery-mobile,npmcomponent/cbou-jquery-mobile,startxfr/jquery-mobile