Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Page not viewable in Safari

Ok, I know that isn't earth shattering as a topic, but it gets weird.

First off, the page is a simple blogger page found at http://www.catalogueofships.com

Second, the page does appear in Foxfire (also, not earth shattering news, I know)

But here is the weird part. Immediately after I load it in Foxfire, it works in Safari for a limited time. Can anyone make heads or tails of that?

Also, this just started yesterday. No problems before. I did no upgrades to my computer or software this week.

Thanks.

mk

PowerBook 12 G4, Mac OS X (10.4.1)

Posted on Nov 24, 2005 9:28 AM

Reply
Question marked as Best reply

Posted on Nov 24, 2005 9:37 AM

My guess, based on the results of putting the page through the W3C Validator, that the problem is a combination of bad coding and using non-standard extensions. Safari is the least forgiving of browsers when it comes to pages with bad, incorrect, or non-standard coding. The W3C's own browser/editing tool, Amaya, also won't display the page.
304 replies
Question marked as Best reply

Nov 24, 2005 9:37 AM in response to Michael Kraskin

My guess, based on the results of putting the page through the W3C Validator, that the problem is a combination of bad coding and using non-standard extensions. Safari is the least forgiving of browsers when it comes to pages with bad, incorrect, or non-standard coding. The W3C's own browser/editing tool, Amaya, also won't display the page.

Nov 25, 2005 4:32 AM in response to Michael Kraskin

I suspect this has something to do with how Safari interacts with name servers.

The domain of the site you mentioned actually points to another domain:
http://www.catalogueofships.com/
http://www.michaelkraskin.com/catalogue/index.htm

Firefox is able to pick this up as you say but Safari ignores the domain referal until the domain exists in lookupd within OSX.

Use the bug reporter on Safari to give Apple a heads up although you'd hope there are enough posts by now for someone to realise something is not quite right.

Nov 25, 2005 7:18 AM in response to ibosie

Thanx for jumping in with your reply, ibosie. I believe you are correct and that a bug report should be sent to Apple. In case the original poster doesn't know the form is "Report Bugs to Apple" and it is under the Safari menu.

However, it is also the case that there are problems with the coding of the page which should be fixed so that it will appear correctly in any browser.

Nov 25, 2005 8:18 AM in response to Michael Kraskin

First off, I see you are not using a simple redirect, where you have the domain "http://www.catalogueofships.com/" and have your host redirect calls to that address to "http://www.michaelkraskin.com/". This being the case, there is nothing your hosting company can do for you - everything is being done within your web documents which are beyond the control of your host.

Also, you have three levels in your web site, which seems complex for what is accomplished.

"http://www.catalogueofships.com/" calls up "http://www.michaelkraskin.com/catalogue/index.htm".

"http://www.michaelkraskin.com/catalogue/index.htm" calls up two addresses in frames: "CoSleft.htm" and "blog.html".

"CoSleft.htm" is blank.
"blog.html", having been called by "http://www.michaelkraskin.com/catalogue/index.htm" now calls "http://www.michaelkraskin.com/catalogue/blog.html".

Additionally, W3C's Amaya is reporting errors on each of the three levels. Additionally, it won't automatically load the final blog.html. Instead, I get an error box saying "Not Well-Formed XML Document - Reload as HTML or showparsing (sic) errors?" As I mentioned before, Safari is very unforgiving of bad, sloppy, or incorrect code.

BTW, although the percentage of Safari users is still small, but it is growing and it is now the third most used browser on the web, behind IE and Firefox and ahead of Netscape and Opera. And note that it is the only platform-specific browser in the top five.

Nov 25, 2005 8:38 AM in response to Tom Graves

I actually changed that yesterday. the index.htm file is only a single page now, I elminated the cosleft file, so, if you are still willing to help me (thank you so much for this, BTW), check out the new version.

I will take another look at the index.htm code when I get a chance, thank you very much.

But I don't understand your first point.

"First off, I see you are not using a simple redirect, where you have the domain "http://www.catalogueofships.com/" and have your host redirect calls to that address to "http://www.michaelkraskin.com/". This being the case, there is nothing your hosting company can do for you - everything is being done within your web documents which are beyond the control of your host."

I don't have any control over the type of redirect my hosting company is using. They have a service called "forwarding" that in theory points a domain name to another web page. There doesn't seem to be any other way to do this. The main problem that is returned in the W3 report is that they do not include a DOCTYPE in the forwarding code, and this seems to lead to a bunch of "undefined" errors.

EDIT: Just W3'd my index.htm code. Wow. I have a lot of work to do! And I am guessing this is a Java problem now. Thanks for this, I had never heard of w3 before. It's great.

Nov 25, 2005 8:57 AM in response to Michael Kraskin

I actually changed that yesterday.


But I looked at your site in Amaya this morning, as I was writing my reply. However, I see Amaya needs its cache emptied to see changes, so I now see the new page.

"http://www.michaelkraskin.com/catalogue/index.htm" is still giving me the "Not Well-Formed XML document" error.

When you register a domain, you can have it point to something else. I set up a web site for a non-profit a few years ago. My account on the hosting service was something like "tegraves.tripod.com" (I forget exactly what it was - I passed the site on to someone else). I registered the domain "www.rotary7370.org" and had it point to "tegraves.tripod.com". That way, people could enter the Rotary address and they would be taken to my site. BTW, you could also get to my site using my actual account address of "tegraves.tripod.com".

Nov 26, 2005 7:24 AM in response to jowal

Can you explain the problem you are having, and with what browser, browser version has the problem?

I have no problems seeing your site in Safari 2.0.2, Firefox 1.5rc3, Camino 1.0b1, Opera 8.51, or OmniWeb 5.1.2. I can click on all the menu entries, see all the photographs, switch between pages: everything seems to work. I do find, however, that the ad-blocking extension for Firefox, Adblock, completely blocks your site, leaving only a blank, brown page (I suspect, however, that Adblock needs to be updated for Firefox 1.5). PithHelmet, an ad-blocker for Safari, does not block any of your site.

I would start by making sure your pages meet accepted html/xhtml standards. Both www. joelcadiou.com and webamab.free.fr have errors according to the W3C Validator. Some of the errors are that there are "illegal" characters in your captions. These errors will not break your page, they just make it so the page does not pass the validator with no errors or warnings.

BTW, very nice site, well laid out and pleasing to look at and use, plus, very nice photographs.

Nov 26, 2005 7:58 AM in response to Tom Graves

Ok, now I'm trying to load Joel's page, and I have EXACTLY the same problem. I just get a blank page, then I load it in Firefox and it works fine (for now) in Safari!

Anyway, I wanted to report back in. I had godaddy take off the "masking" feature" which maintains www.catalogueofships.com in the navigation bar, and now it seems to work fine. Unfortunately, I have an ugly url in the navigation bar.

I notice, Joel, that you have the same "masked" property. I'm guessing this is the source of our woes.

k

Page not viewable in Safari

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.