Site Feedback

Snooth User: kevchan

Search Refresh

Posted by kevchan, May 30, 2007.

Can you get the screen to refresh blank when I click on search (it always tries to conduct the last search)

Your "good with beef" example search string returns no results when I try it

I think you have you "all wines" and "wines in stock" buttons mixed up


Reply by Philip James, May 30, 2007.

all wines and in stock is getting fixed now - thanks.

"good with beef" is on our list to fix! its a bit embarrassing as its one of our main examples, so we need to fix that asap

the saved search is something that people asked for - its purpose is if you view a wine you can page back and see the results still. after 2 hours the search does get cleared, so if you log in the next day youre ok.

any thoughts on how that can be handled better?

one thing is we will implement some better back button support which may negate the need to do this at all. thats probably 1 month out still though.

Thanks Kevin

Reply by gr, May 30, 2007.

Two thoughts.

First, when I click the back button in my browser, I should get the page as I viewed it previously on my own, maybe being asked whether I'm sure I want to resubmit the data I did last time. That's the point of the back button. Please don't re-invent the back button. When I click a "search" button in a web page, I want to do a new search. I don't want to see some search I did a couple of hours ago, I want to do a new search. If I wanted to go back to that other search, I'd have used the back button (or, really, switched to the tab out of which I opened the detail pages, but whatever).

Second, I can see how this is a fundamental difference of opinion. I think it should be an option on a user preferences page and the way I describe should be the default with the behavior you've got now as an option, not just because I like it better my way but because my way is a common denominator with the way most of the rest of the web pages in the world work.

Reply by Mark Angelillo, May 30, 2007.

Our intention is to have full back button support. The cookie (saved search) solution is a stop-gap measure I have put in place until we can (next month) implement the more robust back button solution we all know and love.

If you're curious as to how AJAX messes with the back button, you can definitely email me. If not, it should work as you expect in just a few weeks.

Reply by gr, May 30, 2007.

Um... I think I know what AJAX does, just didn't think it was the issue here.

I thought this was "left the page and went to a wine detail page" not "redrew the span on the existing page".

Or are they just always the same thing for (As mentioned elsewhere, I can't so much LOOK for myself right now.)

In any case: "Okay."

Reply by Mark Angelillo, May 31, 2007.

That's half of it. Basically when AJAX loads a bit of data that specific chunk of data is not stored in the browser's history (which drives the back button). It logically follows that when I first built the site, the default behavior was such that every time a user back-buttoned from the wine details page the search was blank. A user clicks into a blank search page and the searches he/she does are all asynchronous.

I've implemented this cookie based solution to fix this. Any previous search preferences are stored in cookies and executed again when the back button is used from the details page. This, to us, is clearly better than having to re-search every time you leave a product page.

The problem still remains that each search step is not saved in the history as the user navigates through the site (and also that our search cookie timeout is 2 hours, which means your old searches resurrect themselves). It is definitely fixable, and is in the queue to do so as soon as we have prioritized it as "next". We are spending most of our time building pages and fixing bugs right now as we prepare for launch.

The problem is irritating, but we feel we can put off fixing it for a few weeks while we concern ourselves with more pressing matters.

Reply by Philip James, Jun 6, 2007.

Mark just added this - its a real pain with ajax, but i think it works really well now.

Reply by gr, Jun 6, 2007.

Does it even work in IE6? ;^>

Reply by Mark Angelillo, Jun 6, 2007.

IE6, IE7 and FF should be supported. Unfortunately, Safari users are left out in the cold for now as far as AJAX back button support goes. You can see for yourself by logging into Gmail and trying to use the back button. This is a limitation of Safari and AJAX trying to work together.

I will make sure to keep up with the news on Safari's development. Hopefully Apple will make this available soon!

Reply by gr, Jun 6, 2007.

Is that worth a FAQ?

(Does gmail bother?)

Reply by gr, Jun 6, 2007.

Okay, the back button works like I expect it to except that if it actually needs to load a search the screen appears and then AJAX actually rerenders the main frame, meaning the loading window and the blackout. I'd call that Good Enough.

I'm sure you tested (because, you know we were talking on AIM at the time) but Works for Me in:

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv: Gecko/2007051502 Firefox/
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/2007051502 Firefox/
IE 6.0.2900.2180.xpsp_sp2_gdr.070227-2254

As for Safari... it appears to actually work just fine in the simple cases (click something, read it, hit Back). What's still broken there? In fact, I can't find a use case in which the Safari I'm using is broken. That's "Version 2.0.4 (419.3)". I search for a wine, I follow it, I click back, I get the same search. I open a wine in a new tab. I click on search there, it's blank. I back up to the wine description, search from the sidebar, get the right search results, follow them to a wine. Back in the original tab works. Back in the new tab works (for the correct, second search). What's broke here?

I see that it kind of ignores state (like, if I login in another tab, then click a link from a search result in the first tab, I'm logged in, then click back, and I'm not logged in), but I guess I don't see in what way it doesn't work Good Enough.

Back to Categories

Popular Topics

Top Contributors This Month

127503 Snooth User: rckr1951
17 posts
1464471 Snooth User: William Djubin
1464471William Djubin
9 posts
847804 Snooth User: EMark
7 posts


View All

Snooth Media Network