Thanks for the responses so far. The problem seems to be well understood. The solution I'm after is ideally a fix to the root cause. I'm sure one or two of the suggestions may work but they seem to be workarounds.
Have you tried updating the dependencies? Give that a shot . 
Topic: Developers - I need a Javascript bug fixed - $10 bounty (Read 519 times)
Thanks for the responses so far. The problem seems to be well understood. The solution I'm after is ideally a fix to the root cause. I'm sure one or two of the suggestions may work but they seem to be workarounds.
Javascript Quickfix
To be added in body somewhere:
1Aswr8vXivfate2vbKKtZHtLisFAVFfqqe
Code:
To be added in body somewhere:
Code:
1Aswr8vXivfate2vbKKtZHtLisFAVFfqqe
Try to add these headers to the page:
header("Cache-Control: no-store, must-revalidate, max-age=0");
header("Pragma: no-cache");
header("Expires: Sat, 26 Jul 1997 05:00:00 GMT");
?>
I believe the problem you are having is because of content cache by the browser.
This will force all browsers not to cache the page and so even when back button is clicked, all should be reloaded as if it is the first request.
Btw, your issue doesn't happen only on the back button, if you click on some other page and then you click on the logo, you will have the same issue.
header("Cache-Control: no-store, must-revalidate, max-age=0");
header("Pragma: no-cache");
header("Expires: Sat, 26 Jul 1997 05:00:00 GMT");
?>
I believe the problem you are having is because of content cache by the browser.
This will force all browsers not to cache the page and so even when back button is clicked, all should be reloaded as if it is the first request.
Btw, your issue doesn't happen only on the back button, if you click on some other page and then you click on the logo, you will have the same issue.
Yes I can fix this error. There are multiple ways of doing it. Setting the delay for the carousel on the landing page would work too. There could be a minor bug in the code as well. Can we have access to the code to see what exactly is happening? I think I can fix this.
//Interval is the delay at which the slides change.
If you're using css to animate then this could work
Furthermore ,there could be a slight possibility you need to update the versions of Jquery and Angular stuff (Angular.animate/angular.route etc) because your're using the old versions.Try updating them,might help.
Code:
$('#mainCarousel').carousel({
interval: 4000
});
interval: 4000
});
//Interval is the delay at which the slides change.
If you're using css to animate then this could work
Code:
.carousel-inner > .item {
position: relative;
display: none;
-webkit-transition: 0.5s ease-in-out left;
-moz-transition: 0.5s ease-in-out left;
-o-transition: 0.5s ease-in-out left;
transition: 0.5s ease-in-out left;
}
position: relative;
display: none;
-webkit-transition: 0.5s ease-in-out left;
-moz-transition: 0.5s ease-in-out left;
-o-transition: 0.5s ease-in-out left;
transition: 0.5s ease-in-out left;
}
Furthermore ,there could be a slight possibility you need to update the versions of Jquery and Angular stuff (Angular.animate/angular.route etc) because your're using the old versions.Try updating them,might help.
I think I won't help much, but it looks like your problem shows up as soon as you leave your homepage, it's just not noticeable because your images don't cycle in the other pages. If you set a breakpoint on the last instruction of your setInterval, you will notice it cycles every 5s, as expected. But when you change page, it seems it gets triggered after 2 or 3s, like if it had 2 instances running simultaneously.
on firefox also like that too
Hi Bitcointalk,
I know a bunch of you on here are very talented developers. I have a small bug that needs fixing for those that are familiar with Javascript. This should be fairly straightforward if you know front-end web dev.
Here's how to replicate the bug.
*edit*
Offer over.
Thanks for looking everyone!
I know a bunch of you on here are very talented developers. I have a small bug that needs fixing for those that are familiar with Javascript. This should be fairly straightforward if you know front-end web dev.
Here's how to replicate the bug.
*edit*
Offer over.
Thanks for looking everyone!
Jump to: