Techsurvivors
Archives => 2003 => Topic started by: Xairbusdriver on March 12, 2003, 10:27:00 AM
-
No, I don't need help installing/using/unistalling/finding drivers/etc. on/about/for X. But I have been told that the site I work on crashes Safari, even after running the HTML and CSS through the validators. So...
Can any of you OS X user's give me a site check and tell me of any problems with your browser. I'd like to have a screen shot, the browser name and version, and, if possible, if using Classic helps.
TIA. Here's the URL.
Jim C.
-
Jim, No problem using 10.2.4, IE 5.2.2 on a DP 800. Classic was not running.
I randomly checked many (but not all) links and they all connected/appeared just fine.
As far as I can tell, your site is Jag and IE (shudder) friendly.
A screen shot of what I could capture is on the way.
Harv
[ 03-12-2003, 11:50 AM: Message edited by: pendragon ]
-
If it's any help, fine in IE5.1.6 on OS9.1 (loaded fast on dial-up too)
-
Crashes Safari instantly on loading.
10.2.4
-
...same as bobw.....
Crashes Safari instantly on loading.
10.2.4
-
Hi Airbusdriver,
I'm running Mozilla 1.3b (linux) and the page shows fine. I have a suggestion though. Can you post a couple of URLs to internal/subpages...the pages you link to from the main page?
If Safari users go to those pages first, do they still crash? If not, then compare the source code on the mail page to those and see what might be different.
I looked at the code and while I don't see anything wrong with it, it maybe that your version of CSS just isn't Safari friendly ...Safari not being fully fledged yet. Stating the version of CSS and tighting up your HTML so that it is "strict" not "loose" might help. For the best cross browser compatibility, stick to CSS1 although you might get away with a few things in CSS2
The one thing that I noticed that is broken is the links to e-mail at the bottom, where you have multiple people defined to get the message. In Mozilla, clicking there puts your e-mail address in the to: box, but all the others become part of the subject line along with the part you mean to be the subject.
-
In 9.1. Both Netscape (7.02) and I.E. (5.1.6) work fine, and on 10.2.4 the same results Netscape (7.02), I.E. (5.2.2) both load fine, now Safari, 1.0 Beta, crash! Hope it helps!
-
My trusty old G4 running 9.2.2 and NScape 4.75 shows your site perfectly, and fast, the pictures are great. Nice.
Me? OS X? Not yet,,,,,
-
IE 5.2.2. in OSX 10.2.4. loaded fine Jim but Safari quit so fast,not even sure it started to load the page.?.
I combined the Safari quit onto the IE snapshot.
Click Here
-
Jim; it looks great with Camino (Chimera), I havent tried it with safari yet but will also Omniweb.
Oky doky on Omniweb. Camino loaded slow (very unusual) one line near they top was overlapped 50% on the line above, but otherwise looked fine. Nice site.
[ 03-12-2003, 10:41 PM: Message edited by: gmann ]
-
10.2.4 and the Safari went down like a bolt of lightning hit it.
-
Hey, Jim:
Am sending you two screen shots from my Pismo, running 10.2.4 (w/Classic in the background) 640MB, 15+" display, 1024 x 768 and millions of colors . . .
1) NS 7.0.2
2) IE 5.2.2
Both loaded in a flash, literally, both stable.
I scrolled the site. NO prob-lem(s)
Yers truly
-
All I really wanted was reports of failures. But like he said, "It's hard not knowing!" That is it hard to know what the thing is supposed to look like if you can't see it!
It seems Safari is the only browser that crashes. Here are a couple of links to internal pages, but I'm not sure that will really help. Most og the pages are made from the same 'template.' But there are obviously differences. We'll see.
Been busy fixing those e-mail links and fixing the fixes after I got a little too fast with the copy and paste routine! (makes a good case for learning GREP!) Most should work correctly now, however, I also worked on the tax stuff today and I'm not completely recovered!
I'll consider your 'strict' suggestion, Diana, but have heard that can also lead to other problems with some browsers. The CSS is validated under version one, but even that doesn't help when a user has NS 4! All the pages vaidated as HTML (loose) and CSS1. Only 2 'warnings' in the CSS, and that is because of a 'hack' to get IE to work correctly. It is quite widely used and the only one I have in there. Apparently it is not causing problems for any version of IE. Safari may be another question!
Oh yeah the 'internal links':
The following pages are very similar -
Events (only table in the site)
About Us (mostly text)
Plans (a large animated gif)
Snapshots (oodles of thumnails/links)
Construction (more thumnails/links)
These pages have a much different 'page menu' (really none) which may be the Safari problem:
panorama view 1
panarma view 2
Jim C.
-
Jim, the mystery deepens...all the other pages load just fine in Safari - EXCEPT "About Us" - which causes the instant quits described by others for the index page. Hmmm....there is something in those two pages that Safari is NOT happy about. At least that narrows it down a bit...
-
Thanks Paddy! That really may help! Will take a closer look at them tomorrow!
I have also discovered another ASCII coding error that may slip by some e-mail clients but needs fixing. Apparently Eudora doesn't mind a "&" in place of a "?" for delimiting an e-mail header! Others may be more perskickerty (kbear/weldiger can spel cheque that wun)
Jim C.
-
Jim, you might want to check this page out:
http://diveintomark.org/safari/51.html
It describes a lot of the known problems with Safari - there may be something in there that corresponds to something in your pages. There are a couple of known issues that cause Safari crashes - don't know if they apply to you or not - probably a lot quicker for you to figure out than one of us who would have to plow through your code to see if any of it corresponds to the known issues.
One suggestion - you might try uploading your index page without the CSS (somewhere temporary...it will probably look very weird without it) and have us check it that way. Since CSS is Safari's weak spot, it might be the place to start.
I sent a bug report to Apple just in case it doesn't fall into the known issue category.
-
Great idea Paddy! Here you go:
MacOSphere site (no CSS, about what NS 4 'sees!')
Actually, the CSS is technically there, but the link to the style sheet file is commented out, so there should be no styling done. Even a beta browser should be able to handle/ignore tags it doesn't recognize.
I really appreciate all the help from TS!
And I will check that link tomorrow!
Jim C.
[ 03-13-2003, 09:46 PM: Message edited by: airbusdriver ]
-
Jim, that page loads just fine in Safari, so I think it is now safe to conclude that it's something in the CSS (just as Diana suspected)...though since you used the same CSS for other pages, it's got to be something in how it is used by that page in particular - or some aspect that is only used by that page (I did have a quick look at your style sheet, and you may have something in there that is only on the two pages that cause Safari to go belly-up...but again, you're going to be able to pin that down a lot faster than we can!!)
If you find it...let us know!
-
Another winner!
It should be a simple Find and Replace (or should that be Search and Destroy!). BTW, I couldn't keep from sneaking a look at that link, have it bookmarked for further study!
Thanks again! No further tests needed 'guys' let me work through these hints for a while. Just wish I had thought of doing this logical exercise before bothering everyone!
Jim C.
-
Loads fine on a Red Hat 8.0 Linux/Mozilla/Microtel box.
Unusually quickly, actually.
Nice site!
Epaminondas
-
Wow!...cool link Paddy,.. So much more interesting than that dry stuff I linked to.
Reading that gave me an idea too. The safari link indicated that they're working from the same base that Konqueror uses. I have Konqueror 3.0.3-14 Red Hat (Using KDE 3.0.3-8.3 Red Hat)(actually called while in gnome, not KDE), so I fired it up to visit airbusdriver's pages. I wondered if it would crash because it exhibits the same behaviors as Safari when playing around at that diveintomark site. Jim, it didn't crash. In fact the pages look quite nice, the front page and the about us page.
I would suggest looking at some way to fix your code for Safari, but as fast as they seem to be working to get Safari up to speed and the fact that Konqueror is a step or two ahead should mean that they'll have whatever bug Safari has all ironed out real soon.. I'm betting that Paddy's bug report will be the "fixer upper" that is needed...
-
I may not spend too much more time on this Safari problem. No one at the church uses it (much less a Mac! ) and it is bad enough trying to get the basics to NS 4!
I noticed the same 'relationship' with Konqueror at Paddy's link and since Diana says it can render the pages OK, I may just be trying to hit a moving target, anyway.
I did find a few things that showed up in a Source View in IE that were not actually showing in the display (it doesn't seem to handle comments correctly in the Source View?! ) so I just deleted those comments for the HTML. Plus themphill pointed out my miss-use of some comment tags (using too many hyphens and/or spaces), which have been corrected.
Time to move on! Like Safari?
Thanks again for all the help, suggestions, screenshots, and links! You have also encouraged me about the stability of X!
Gonna take a break and go to a Leo Kottke concert tonight!
Jim C.
-
quote:
Gonna take a break and go to a Leo Kottke concert tonight!
-
Even better in person! Even managed to get an autograph! There were at least 3 who brought their guitar for him to sign!
I would swear there was another performer somewhere in the auditorium! How does he get so much music out of 12 strings?
Couldn't help but think of my younger son who made his way into the Berkley School of Music with a guitar performance he created and recorded. Brought back memories of being with him when we saw Michael Hedges perform many years ago.
-
As for the Safari crashes, it may very well be in the use of CSS. In a couple of places I end up with 4 nested DIV's. Other places I have 3. Nesting can be dangerous for some browsers. Will have to see if that can be simplified!
-
Wow! Leo Kottke! I am so envious ... one day he'll come here to charleston.