Log in again, go to your profile, then click anything that would reload the main content area (for example Info or Photos in the topnav) and you will see what I'm talking about. In my first post I said that Facebook only does it for some calls. The AJAX call they use for it is a POST request: http://www.facebook.com/ajax/location_refresh.php
Is this email group about helping eachother and producing solutions to problems or just about forcefully trying to prove the one who asked a question is stupid? Matt On Jul 9, 5:53 pm, Ryan Florence <[email protected]> wrote: > >> I have some big calls that > >> reload almost all the page (like Facebook, to say) > > I had to log in to facebook for the first time in forever to see what your'e > talking about. > > Facebook either has a little indicator next to the link you clicked (which is > completely sufficient user feedback), or, in the case of moving to a user's > profile, it reloads the whole page. > > But facebook doesn't try to act like it's reloading the whole page when it's > not. > > On Jul 9, 2010, at 10:47 AM, bootle wrote: > > > > > How about just setting the document.body's css cursor property to > > the progress icon and then set it back when you're done? > > > I'm doing it now + setting the page's <title> to "Loading...", that > > doesn't give the exact feel I want to achieve though > > > I'm with Ryan here, I don't know what you're after. Can you point us > > to a > > site that behaves the way you want? I also agree: if you're loading an > > entirely new document via Ajax, you're doing it wrong. Just load a new > > document like normal. > > > For example Gmail and Facebook do it this way (Facebook only for the > > main page loads though). Notice that when you load a 'new page' in > > either of these the site never actually reloads, header and the chat > > area stay intact, only the content is loaded - despite that, browser > > displays all the loading whistles as with a classic page load - hope > > I'm explaining it well enough > > > I have just one call that I want to handle this way, as I wrote to > > Ryan, I think iframe might actually be a thing to experiment with. > > > Thanks, > > Matt > > > On Jul 9, 4:37 pm, Aaron Newton <[email protected]> wrote: > >> On Fri, Jul 9, 2010 at 8:24 AM, Trevor Orr <[email protected]> wrote: > >>> If I understand correctly you have multiple requests firing that replace > >>> most of the content on the page? Then I would guess you would to create > >>> and > >>> display a spinner and then have some way to figure out when the last > >>> request > >>> has completed and remove the spinner. > > >> The Group class lets you do that. > > >> How about just setting the document.body's css cursor property to > >> the progress icon and then set it back when you're done? > > >> I'm with Ryan here, I don't know what you're after. Can you point us to a > >> site that behaves the way you want? I also agree: if you're loading an > >> entirely new document via Ajax, you're doing it wrong. Just load a new > >> document like normal.
