Safari does not work with TheTrainLine website

Contrary to what you were told, that web site fails W3C Validation. Safari is one of the least forgiving of browsers when it comes to non-standard, bad, or incorrect code. You can report this back to them along with the link to the validation.

In the meantime, you can try Firefox or Camino which are more forgiving of non-standard or bad code.

Safari has improved with the latest update and the cpu usage doesn't spike as often as it used to, but it still is not fixed completely. Firefox has some resource problems as well. As with Safari, I have seen cpu usage go to 100% on some pages and then seen it drop down to reasonable levels when the tab with one of those pages is closed. Both Safari and Firefox can end up with performance problems if you have them open long enough and open tons of tabs. I have not used Camino enough to see how it behaves for long sessions, but it starts out nice and snappy. Firefox and Camino are both good browsers and are worth looking at if you are interested in having an alternate or backup browser available.

The TrainLine URL problem looks a lot like my own URL problem. But TrainLine worked just fine two or three times in a row using my Safari browser and Google. This despite that this combination of browser and search engine frequently fails to summon URLs, producing error messages instead. The messages take various formats, all announcing that the site doesn't exist or isn't on the server, etc. Sometimes a message bears the Google logo, indicating it came from the search engine, other times it seems to come from the web site being summoned.

This problem of being unable to summon URLs did not exist with my previous Earthlink 58K dial-up service. It began when I went on Earthlink's DSL service last week. Now, web sites download rapidly, but Safari and to some extent Internet Explorer have frequent trouble connecting with them. Numerous clickings of the repeat icon may bring success when that happens. Earthlink technical people have had me put DNS server numbers in the appropriate System Preferences > Network window where before there were none, but the problem persists. I’ve downloaded Internet Explorer, and it seems to work more reliably than Safari.

iBook G4 Mac OS X (10.4.3)

iBook Mac OS X (10.4.3)

iBook Mac OS X (10.4.3)

iBook Mac OS X (10.4.3)

The trainline site comes up for me with no problems in Safari, but I have not tried to do anything on the site.

I would recommend almost any browser other than IE as an alternate browser. Microsoft stopped developing and updating it 3 years ago, they stopped support for it at the end of December, and you just squeezed in your download as they will be ending distribution this coming Tuesday, January 31. IE is 3-years behind the time in features and what it will support, whereas any of the other excellent browsers out there are up to date.

I appreciate the info regarding IE. I probably will replace it with a newer browser. I'm not sure how to dispose of the IE, however. I assume the first thing to do is trashcan any easily identified IE files, but such applications often seem to install here and there other files not so easily spotted.

That is good information, Tom. Are they perchance, as a result of their tolerance, less inclined than Safari to hog the whole CPU on a regular basis? That would be really useful...