Anyone notice anything different?...

[foraloysius]

Yes, I use the back button often, but I use IE8 which works fine most of the time. Only sometimes I have to refresh the page. I find this easier to navigate especially when I am reading threads lower on a page. Otherwise I have to scroll down again to the threads I was reading.

 

[Unimatic1140]

Yup, using the BACK button on most browsers will not refresh the page, it just takes you back to where you last left off with old data. Doing this is fine if you want to go back to the last line you left off on, but you will want to hit refresh the next time you return to get the lastest posts and also to update your WASH/RINSE/SPIN button.

 

[foraloysius]

Somehow I get the impression that IE8 renewed easier with the back button than now with the system on the server. Could that be correct?

I see the "Mark all threads..." option is back. Yay!

 

[Unimatic1140]

Somehow I get the impression that IE8 renewed easier with the back button

 

No I believe IE8 does re-do its Java-script, but using the back button doesn't reload data from the server.  That's why the old wash/rinse/spin buttons appear to update with the back button on IE8.  No other browser did this.  IE8 had other problems with cookies, like it could only remember about 350 threads and since we have 500 active threads (100 in Imperial, 100 in Deluxe, 100 in Super, etc) the threads at the bottom that had been seen would start turning back to WASH.  The only browser that was able to remember all 500 threads was Firefox.  With the data being stored on the sever we don't have this issue anymore, everyone will have all 500 threads remembered.

 

From my experience in using IE, FF, Chrome, Opera and Safari  Firefox is the best browser with the smallest chance of having issues across the board.

 

So with that said I'm going to assume that WASH/RINSE/SPIN buttons are working properly until we find otherwise.

 

[a440]

Very cool Robert. You think of everything!

 

[sudsmaster]

Thanks Robert.

I only recently noticed the cookie based aspect when I started using my notebook to double check some forum features you and I have discussed. At that time I noticed that my buttons had not been saved on the server, and I wondered why. Now I don't even need to think about it at all!

 

[DADoES]

I see that server-side Wash/Rinse/Spin also no longer uses . I routinely turn off on the ancient NT system, and the buttons are appearing there now when they didn't previously.

 

[foraloysius]

Firefox

I have used Firefox in the past. It was a good browser, but if froze way too often. When that lead to a crash I de-installed Firefox. No more Firefox for me. I went back to IE for this site.

 

[countryguy]

Thanks Robert for the new feature with saving the Wash, Rinse and Spin buttons - saves a lot of time!

 

Gary

 

[mayguy]

Seems like I have to log in everytime I come here. I'm using firefox, and did clear the cookie and what not.

 

[sudsmaster]

Notice Anything Different?

 

<span style="font-family: arial,helvetica,sans-serif; font-size: medium;">Why, yes!</span>

 

<span style="font-family: arial,helvetica,sans-serif; font-size: medium;">I feel suddenly full of new found vim and vigor!</span>

<span style="font-family: arial,helvetica,sans-serif; font-size: medium;">Is that to be expected? </span>

 

 

[Unimatic1140]

Seems like I have to log in everytime I come here. I'm using firefox, and did clear the cookie and what not.

Jay please see this thread...

Loading…

www.automaticwasher.org

 

[Unimatic1140]

An Experiment

Ok I recieved quite a few emails yesterday from Internet Explorer users who were used to seeing the WASH/RINSE/SPIN buttons update when they click on their BACK BUTTON.  Since I implemented the code change to store the WASH/RINSE/SPIN data now on the sever that would have stopped and IE would now behave like all the other browsers, you must hit refresh to see the updated WASH/RINSE/SPIN buttons.

 

I just happen to find a small bit of Java-script that will automatically refresh IE when you use the back arrow.  I just implemented this code.  It will work in IE7, IE8 and IE9 ONLY.  Please let me know how this works for you Internet Explorer users or if it seems to screw anything up for anyone.

 

ps to Glenn: btw you can't use the "J" word in posts as I strip it for security reasons.  You can however type it as Java-script.

 

[westie2]

It is working in IE with the new script. I just tried it. It sure is nice to be able to go from one login toanother and see where the last read is.

Thanks once again Robert.

 

[foraloysius]

Works like a charm, I can now easily use the back button and the thread's button goes automatically to spin. Again, you're a genius!

 

[DADoES]

 

LOL, I hadn't noticed the word was missing!

 

[DADoES]

 

I rarely use the Back button.  Heavy user of tabs.  When hitting AW.org or any other message board, I go down each index page in turn, middle-clicking (or CTRL-LeftClick) on each thread of interest which opens the threads in new tabs.  They're all loaded and ready to read.  Peruse a thread/tab, close it, on to the next.

 

Louis, you might try Firefox again.  I haven't used IE in several years other than for a few sites that require it (Windows Updates, for example).  There was some instability in a few previous version of Firefox and I ran into a conflict with AVG for a while (got rid of AVG for Avast).  I often have two or three Firefox windows open at the same time, and often 10 or 15+ tabs in a window and don't have any problem with crashes or freezes.  Flash player occasionally crashes (running a YouTube clip for example) but Firefox itself doesn't.

 

I'm using Forefox 2 on the ancient WinNT system.  YouTube protests that it no longer supports the old version (of both Firefox and Flash) but clips do still run.  When a YouTube video clip is opened, it's "dead" but there's a link to view the page in an alternate format that works ... can't predict if YouTube may do away with the alternate at some point.

 

[foraloysius]

Glenn,

I will stick to IE8 for now, it works actually very good for this site and a lot of other sites. I'm glad to hear though that Firefox has worked the problems out.