If you click on Amazon.com's Auction tab or the Help/YourAccount graphic, Mozilla M4 reports "Imagemap Error: Your client did not send any coordinates. Either your client doesn't support imagemap or the map file was not accessed as a map." If you hit the Back button to go back the the Amazon.com front page, the mouse pointer will correctly turn into a pointing hand icon when hovering over the Auctions tab and Help/YourAccount GIF. If you now click on the Autcions tab or the Help/YourAccount graphic, the imagemap works correctly. This "fix" also happens if you reload the page.

Tom -- Here's one you'll like...

I tested this with M7 Apprunner also with Windows 98. I got the imagemap error descirbed above sometimes, but other times the console got the following error and nothing happened at all. Loading url http:// in WEbshell 5155e50 nsDocumentBindInfo::OnStopBinding: Load of URL 'http://' failed. Error code: 1 Error loading URL http:// Document: Done (0.22 secs) Got a handle to forward menu item Setting forward menu item disabled Obtained MenuItem Back Setting Back menuitem to enabled

Testing this with M7(Win32), I never got any sort of image map error, but did get the "Load of URL 'http://' failed" problem that kberk mentions above. This bug seems to be tied to the URL format Amazon uses to call its redirect script. None of the links on Amazon's homepage that are in this form work: http://www.amazon.com/exec/obidos/redirect-to-external-url/002-2000822-6704610?p ath=http://auctions.amazon.com/exec/varzea/subst/home/home.html/ref=a_ob_tab The links that have this problem are the "eCards" and "Auction" tabs in the top image map, as well as the corresponding text links at the bottom of the page, and also the "Amazon.co.uk" and "Amazon.de" links at the bottom of the page. However, the three links that use the redirection script under the heading "More to Explore" towards the bottom of the page ("Shop the Web," "Amazon.co.uk," and "Amazon.de") do work. I noticed that in those three links the colon of the "http://" that's passed in the query string has been encoded as "%3a" where as the other links are just raw colons. (Don't you just hate a raw colon?) The bug also seems to be tied to the URL of the page that contains the links. When I posted a page with the same URL as the Auctions link at http://www.serve.com/apg/bugzilla/5820.html it worked without a problem. Also, if you go directly to the URL http://auctions.amazon.com all of the redirect script links (which point back over to www.amazon.com, instead of auctions.amazon.com) work.

CORRECTION: I should have said, "When I posted a page with A LINK TO the same URL as the Auctions link ..."

I think I've tracked down the problem here. M7 balks at relative URLs with "http://" in the query string. All the links on Amazon's homepage are relative links which is why the redirection links with "http://" in them have this problem while the ones that encode the colon as "http%3A//" don't. Absolute URLs do not seem to have this problem at all. I've updated the testcase at http://www.serve.com/apg/bugzilla/5820.html to include both a relative and an absolute link with "http://" in their query strings. Numbers 3 and 4 are the new links. I don't know if this will help or not, but I decided to check this possibility out after getting a report that a similar thing I was doing with some JavaScript (passing absolute URLs in the query string of a relative link) caused a similar error in Navigator 4.08(Win32). I'm not even sure if the protocol allows "http://" to exist in the URL without being encoded. If not, this may just be a matter of Seamonkey being more strict than people are used to, rather than a bug.

There seem to be three issues here: 1) The cursor not changing when over the auction tab 2) The image map not sending coordinates to the server 3) The URL not being formed correctly 1 and 2 are fixed. From what I can tell, 3 is also no longer a problem. Clicking on the Auctions and zShops tabs at Amazon.com works (the urls are still relative url's containing ...http://, as indicated above) I'm closing this bug as FIXED. Please reopen if you are able to reproduce the bug still, and include specific directions on how. Thanks.

Verified fixed with the Nov 10th build.