it works fine. On very large pages, the timeout actually has to be a
second or two. Any idea why this is happening? I don't know much
about JS, but my thought is that it's trying to move to that bookmark
before it has actually been loaded in the page; the timeout forces it
to wait for the rest of the page to load before going to the bookmark.
Here is my relevant code for an arbitrary page (let's call it PAGE_B): <body onload="window.location.hash='anchor'">
With this code, if the user goes from PAGE_A to PAGE_B, he will jump to PAGE_B#anchor after PAGE_B has fully loaded. BUT... if he clicks the back button, instead of returning to PAGE_A (which is what I want), he will return to PAGE_B (without the anchor).
Is there any way to change this behavior... perhaps to replace the anchor of page without touching the history stack?
A page I have shows a different background colour depending on the hash portion of the url as it is first loaded. For example a link to mysite/mypage#0000FF would result in a page with a blue background. But another link, this one to mysite/mypage#FF0000, would not give me a red background if directed to the window where mypage#0000FF was loaded just one moment ago. This is normally to be expected, because the browser thinks same page, no load event, basta.
If I use the search portion, for obvious reasons, that is treated a new page load, even when it is from the cache, but I need the hash here. So how do I detect in mypage the moment when the hash string is changed by a user click event on another page in another window, perhaps even from another domain?
I am trying to make sense of the location hash etc. However, I have a few issues that I need to overcome in the process.I have 3 tabs, which need to create a hash and then allow return to that tab on page reload.This is what I need doing: firstly, I need to check the filename accessed and if it is the correct filename (say 'testing.php' or 'testing') then I need to check the GET parameters to see which ones have been called and exist, THEN I need to check the hash to see which tab to load.
I have a problem with IE and location.hash. If I change the hash, the history doesn't "update" and it only keeps one record of the URL. This whole website is AJAX-driven and I need the user to be able to use the forward and back buttons in the browser. Everything works fine and dandy, tested on all the major browsers on PC and Mac, except for IE (both 6 and 7).
In case I wasn't clear, here's a way to reproduce in IE6/7:
Go to google.com Go to yahoo.com#one Go to yahoo.com#two Click back. You'll be back to google.com instead of yahoo.com#one
Is it possible to notice a change of window.location.hash without polling?
I'm working on a Ajax-platform (yes, inventing the wheel again) and have finished almost everything except the support for back/forward-buttons. The track I'm working on is "hidden frames" to keep state in window.location.hash. I've seen some solutions along this way that includes polling window.location for a change... which doesn't comply with my otherwise strict event-driven design...
What I want is a textbox that the user can enter information into. When they press a key the onkeyup event will simulate a function. All that I can do. The function needs to automatically scroll down the page to the anchor that corresponds to the number the user entered. The web page is a factor finding program. You can enter 2 numbers and it finds all the factors of all the numbers between the 2 you entered. Here is the link: [URL] As you can see, when you try to find factors of numbers a new window opens and there is a search box in the top left. Unfortunately, it doesn't work. If you want to check out the code look at the web page but here is the bit that creates the new window
I'm attempting to implement some deep-linking in my simple AJAX application by setting location.hash, and I've run into two problems:
1) Sometimes setting location.hash seems to send the window on both IE and FF to scroll to the top of the page. I do not want any scrolling to occur. The location.hash change happens in a function which is triggered in an onclick event.
2) Changing location.hash creates a history entry on FF (not on IE)... that's pretty cool for FF, but in this case I do not want a history entry created. How can this be avoided?
I found an example which seems to have avoided both these problems, but cannot decipher the pertinent code: [URL]
I am writing a modification to Invision Power Board that makes replying to post via Ajax.
The "Submit" button is being overrun by Prototype's observe function. When the custom function is executed, I run Event.stop(e) to prevent the actual form from being submitted and reload the page.
I have developed and tested on Safari but users began to report bugs in IE, after investigation I discovered that the line
Is making IE execute all the code after it, and then execute its own onclick() function as if Event.stop(e) was not there. Commenting this line fixes the problem, the page is not reloaded, but this line is vital to the code.
So why do I need to set the anchor? To support the back button function after a user makes an ajax reply, pressing Back should hide the new content, and pressing Forward should make it visible. (e.g. every time the anchor is changed) This all works nicely. But not in IE.
This only happens the first time the page is visited ever, or clearing cache and visiting it again. Reloading the page fixes the problem but this is not normal behavior and users shouldn't have to reload to use the Ajax fast reply...
I don't like the way that a link to page top leaves the location bar with something like '#top' appended to it.
So, I'm hooking a listener to the link click event, doing a window.scroll and stopping default action. This is fine as long as the location doesn't already have a hash portion. When it does, I'd like to clean that up without causing a page reload or any server requests.
Is this possible? The closest I got with MSIE is to remove the tail end, but I can't get rid of the actual '#'.
What's wrong with this code? It works in IE and FireFox, but Chrome does not work. The idea is that the function fnTimeOut will be triggered in 5 seconds after onmousemove (fnTimeOut was attach in onmousemove in document). It�s ok. But when, in Chrome, I click on the button "ok" to function fnAlert is triggered instantly. It should be shot just 5 seconds after I move the mouse
Anyone have any ideas or alternative solutions? I thought maybe I was using an IE only thing but it is a version of IE on the IPAQ. I thought maybe it was not standards compliant but I haven't found anyone having a similar problem.
Any idea or advice? TIA, BG.
PS Ignore that I am using a reset button to do this - I have also tried it in the body tag like this:
1) window.location directly with timeout 2)window.location.href. 3) kept sleep function to sleep for 1,2 seconds
but when i removed the set timeout and placed alert, it successfully navigated to new page in firefox.
I have a popup that contains a form. When I submit that form, I need 1) the data to get saved into my database, 2) the popup to close, and 3) the parent window to refresh and display the updated data.
I found the following code in an old thread, but the parent window still shows the old data after it appears to reload. The data is saved in the database, but the parent window only shows the updated data when I manually refresh it by hitting F5.
I have the following function that's supposed to say "Please make a guess" 20 seconds after an initial confirmation is displayed. However, it's immediately displayed as soon as someone hits "Cancel". If I change it's time to 40000 (20 seconds after the initial function is called), it does do it 40 seconds total, so it kind of does what I want. So it seems that the second setTimeout is initiated from the time the script is called generally, but I'm looking for a way specifically to have the 20 seconds start only after the "cancel" button is hit.