back

I want to alert() when browser's back or forward button is clicked or hash is changed in javascript. I have tried this solution and it is working but it is causing problems on other links in webpage and submit each request twice on any link click event. Is there any solution to capture it without using setInterval() function? So I need to capture hash change or back/forward button click event? I need a simple javascript code/function/property that should work in all modern browsers. Any solution ? Thanks Robert Koritnik Not a good idea Can you rather explain the reasoning behind this? We've

I have searched many posts here and elsewhere but can't seem to find a solution to my problem. I have a page which displays database entries: database.php. These entries can be filtered with a form. When I filter them and only display the ones I am interested in I can click an entry (as a link) which takes me to that entries page (via php GET). When I am on that entries page (i.e., "view.php?id=1") and hit the back button (back to database.php), the filter form requires to confirm the form resubmission. Is there any way to prevent this? here are some (simplified) code examples: Database.php:

I know how to take control of the back button. I have a VideoView embedded in a FrameLayout . My question is when the video pops up, the video controls are present for a few seconds. Hitting the back button while they are visible hides the video controls. Is there a way to ignore that function and do the next back action as if the video controls weren't visible? The reason I ask is if I really do want to go back, I must hit the back button twice; once to hide the controls and second to actually go back Based on the source code, this should work: Extend MediaController (for the purposes of this

I was browsing thought GitHub today and noticed that the individual repository navigation doesn't use hash-bangs in the URL /#! or /# and the back button still works. How do you think they are accomplishing this? How does this affect search engine crawling from Googlebot? I know it looks for # in the url. I'm really quite curious as I know using /# is quite debatable. Here's an example: https://github.com/mirah/pindah Thanks! They blogged about it a while back: https://github.com/blog/760-the-tree-slider The effect is implemented history.pushState() function and handlers on the popstate event

Enter/change something in a textarea Before submitting the form, leave the page (e.g. by clicking browser's back button) Go back to the edit page (e.g. by clicking the forward button) Expected result: the content entered in the textarea should still be there Actual result: with HTTPS : all changes are gone (bad!) with HTTP : the changes are still there (good!) Why is this happening when using HTTPS? How can I prevent this? Is the browser or the website responsible? You can consider the following solutions: The autocomplete Attribute (HTML5) This seems unrelated since autocomplete tells the