Back button on third step won't go back

[ayounis90]

I've copied the code from your simple example directly into my app along with the JS and CSS files and everything works fine aside from the very last step the Go Back button doesn't seems to work . I'd greatly appreciate it if you were to lend some insight into this.

[mingliangfeng]

You need to post your code to some place like JSFiddle or give more detail, otherwise on one knows what "doesn't seems to work" means.

[ayounis90]

I can post the code but it would be a copy and paste of your code from your sample app at http://mingliangfeng.me/github%20project/2013/08/02/bs-wizard-demo/

and copy and paste of your CSS and JS files. I copied and pasted only because I wanted to make sure I don't miss something.

More detail I can give about my project is that I have a Ruby on Rails 4.2.5 app, put the SCSS file in stylesheets directory, js.coffee file under the Javascript directory. Initialized the script in my view that has the HTML.

I haven't changed even a single character of code that's supplied from this github repo so I felt it might be redundant to post what you have here already and that's why I did not post it.

[mingliangfeng]

The demo is working there; if it is not working in you app, you better use a debug tool like Chrome Developer Tools to see if there is any javascript error when the JS is loaded.

[ayounis90]

I've done a couple things so far...

1. Created a brand new blank project and copied & pasted the code in there with the same results
2. Tried making sure I have the latest version of JQuery in my Rails application
3. Used the chrome developers console to make sure there are no errors being thrown. I've installed a plugin (chrome javascript errors notifier) into chrome which catches errors on load and both come back with no errors being raised for Javascript at all.

This is really perplexing. I just thought maybe posting the question here someone might have ran into a similar issue and could give suggestions.

[mingliangfeng]

It is better you still create a jsfiddle for that, at least you can identify if the issue is the code or your local browser/env settings.