Hugo Awards on Safari

[kevin_standlee]

We have run across a problem with the new Hugo Award web site that we could use some help fixing. The basic problem appears to be a bug in Safari (specifically 2.0.4 for the Mac, though it may be in other versions). The HTML is correct in View Source, but the page is incorrectly displayed causing broken links. The problem does not occur in IE or Firefox, or in Safari for Windows. We are looking for people with Macs who can check stuff for us. Specifically:

1. We need to know if the problem is fixed in Safari 3

2. We want to test some alternate ways of coding the site so as not to cause Safari 2 to fail.

3. If we are really lucky, someone reading this will have worked on issues like this before and be able to make suggestions.

Edit, 13:05: It's not the problem with actual site (we seem to be tracking it down, but I originally misspelled the domain name in the message above (there's an "s" on the end of "TheHugoAwards"), which was why those of you who tried to click through to it were getting "site not found." Whoops!

Comments

[whumpdotcom.livejournal.com]

It is behaving correctly in Safari 3.

Do you have a screen shot of the issue in Safari 2?

[(Anonymous)]

Aha, just the k/i/t/t/e/n man I needed. I'll email you. - Cheryl

[whumpdotcom.livejournal.com]

Okay, I have it open on my server mini running 2.0.4.

To confirm what I'm seeing is that any clicks in the top part of the page (above an imaginary line starting above 'Hugo Award History' on the right side bar) are being registered as clicks on the header.

Since the markup on the page is valid (according to the W3C validator) this would appear to be either a CSS or JavaScript issue.

Continuing to dig for a few minutes, but must leave for meetings around noon.

Javascript not responsible?

[ceemage.livejournal.com]

For what it's worth, saving the source to my desktop, and then deleting the Javascript in the page header, doesn't solve the problem. This doesn't necessarily completely absolve the Javascript, but would suggest the problem lies elsewhere.

Re: Javascript not responsible?

[whumpdotcom.livejournal.com]

We've chased it down to a CSS issue that the site's developers are working on now.

[dd-b.livejournal.com]

Right now, OpenDNS is saying the domain doesn't resolve at all, on 5 different root servers (they have a way to force a cache refresh). So I can't look at the HTML issues.

This might be OpenDNS weirdness, but I haven't seen that in the past.

[dd-b.livejournal.com]

I also get NXDOMAIN from another site I have an account at that isn't using OpenDNS.

[timill]

Similar here in the UK...

[kevin-standlee.livejournal.com]

Whoops, I typoed the URL, that's why.

[dd-b.livejournal.com]

Yep, site access is fine with the corrected URL. (I'm not running Safari so no comment on the other issues.)

[timill]

Oops...

As dd-b says, all OK now.

I'm seeing the problem as well

[ceemage.livejournal.com]

Using Safari Version 2.0.4 (419.3).

It appears that the links on the right, from "Introduction" to "Hugo Award FAQ" aren't working. Yet a quick View Source shows no real difference between these links and all the others in this section. Very frustrating.

Let me know if there's anything I can do to help out - even if it's just re-testing the pages once they're fixed...

[chocolatescifi.livejournal.com]

It the site down at the moment? I just tried clicking on the link, and all I got was a page that said "The page could not be found."

[kevin-standlee.livejournal.com]

Whoops, no, my bad: I left the "s" off the end of "TheHugoAwards" in the URL.