Post Archive

› January 7, 2003

oh no safari

  • Reported by Nate

Well, the browser is only minutes old, so this report is a little early, but Yikes this site doesn't look right in safari... But it's readable - which is what counts in a pinch.
Update: Mark Pilgrim has already put together a significant post on the subject, and this: Safari information for web designers.

Comments

1. January 7, 2003 02:35 PM

Quote this comment

Nate Posted…

um.. weird.. the whole comment form has gone missing in safari. From a quick browse of some other sites it appears to be something unique to the code here. Also weird, 2 different macs both running safari render this site differently (different font treatment).

2. January 7, 2003 02:42 PM

Quote this comment

Nate Posted…

Apparently I'm not the only one with safari issues.. see Mark Ps review

3. January 7, 2003 02:46 PM

Quote this comment

Nate Posted…

wow, cool - a little spider button on the top right makes reporting bugs to apple very simple.. I wonder if this will help speed up response time to rendering errors of various flavors.

4. January 7, 2003 04:52 PM

Quote this comment

Nate Posted…

From the safari page at apple:
Precision layout Rest assured, Safari renders Web pages properly according to the latest Internet standards . So pages that use advanced HTML, XHTML, DOM, CSS, JavaScript and Java specifications just look right.

I must admit that most sites I've visited today have rendered fine in Safari. There are some sites with a few minor tweaks to be made (assuming the authors want to support the beta level browser), and there are some that are have significant problems. Unfortunately this site is one with big problems. I've been thinking of re-doing some of the interface code anyways, so perhaps this would be a good excuse. I'd swear I saw CSS 2 listed as one of the supported technologies during the keynote address, some folks are noting that Safari is based on the KHTML rendering engine, which, in some form, is also used by Konqueror - and therefore it can be assumed that issues noted with Safari are likely to be inherited from that ilk of browser.

5. January 7, 2003 05:24 PM

Quote this comment

Keith Posted…

I think you did see CSS2 listed during the keynote address. I've noticed pretty much the same. Most sites look fine, some have minor problems and a few have really big problems. It is a beta so... I have to say I love the little spider thing as well. Used it a few times already.

6. January 7, 2003 08:10 PM

Quote this comment

Nate Posted…

Ok, a small (but weird and frustrating) tweak to the css for this site, and now the sub-pages are fully viewable in Safari. I'll have to do some more testing to be sure, but it seemed to have something to do with a particular combo of floating and margins. Oddly the CSS used on the homepage would seem more prone to weirdness, but no issue there. To describe the problem better: this sub-page content you are reading here is contained in two big divs (left and right), Safari was not showing even a hint of whichever column was longer. Removing the margin style seems to have fixed the problem, I've replaced it with padding. I would ramble on but this tiny textarea is getting on my nerves, time to give more typing room for comments... one last thing: Safari's form field spell checking feature makes my year.

7. January 7, 2003 08:45 PM

Quote this comment

CodeBitch Posted…

The MacEdition Guide to CSS2 support in Mac-only browsers has been updated for Safari. http://www.macedition.com/cb/resources/macbrowsercsssupport.html

8. January 7, 2003 08:55 PM

Quote this comment

Nate Posted…

Thanks CodeBitch! I'll make a seperate note of it so that the info is available through syndication.

9. January 8, 2003 12:59 PM

Quote this comment

Nate Posted…

I think the bug I mentioned before is the margin-top bug mentioned on Mark's safari page (number 11 at the moment). My bug was definitely related to margins, but not margin-top specifically. I'll recreate it on a test page this afternoon.