[Transmogrify]

Originally Posted by herkalees

I have a folder that I've called "Initial Site", in it is a single html-ready file, a few style sheets, an oft-used IE6 PNG fix, etc.

In fact, here it is (attached)

Disclaimer: I work in an ASP/.NET firm... and I'm not proud of it. Change the file-extensions to .php and be on your way, smiling.

Cheers for offering out this! There's a few quite nice/useful little things there (such as the Safari stylesheet). I'm going to make a few small changes to suit the projects I work on and use this. Nice one fella!

[herkalees]

Originally Posted by Transmogrify

Cheers for offering out this! There's a few quite nice/useful little things there (such as the Safari stylesheet). I'm going to make a few small changes to suit the projects I work on and use this. Nice one fella!

Yar. It should have, even, a 'Firefox only on OS X' style-sheet too.

[pgo]

I'm curious as to why you're using JavaScript browser detection to feed stylesheets to Safari and OSX Firefox?

Also, does that JavaScript PNG Fix work better than the .htc file thing I've been using?

[herkalees]

Originally Posted by pgo

I'm curious as to why you're using JavaScript browser detection to feed stylesheets to Safari and OSX Firefox?

Believe me, if I was in charge of anything where I work, I wouldn't use 'em at all. I embrace slight browser differences... it gives it character. As for my choice of JS over anything else... it was a matter of "DO IT NOW" and I never bothered to change what worked. For those people with JS turned off... I'll refer them to my boss.

Originally Posted by pgo

Also, does that JavaScript PNG Fix work better than the .htc file thing I've been using?

I've used 'em all man, and the JS one is the only one I've seen work in every scenario - the .htc version has let me down once or twice.

[Transmogrify]

Originally Posted by pgo

I'm curious as to why you're using JavaScript browser detection to feed stylesheets to Safari and OSX Firefox?

Never really noticed any issues with firefox on os x vs. firefox on windows so not worried about that but Safari does occasionally have a few differences and there's no real way to hack Safari styles or use conditional comments so I can't imagine there's any other way other than to use javascript for Safari.

[Bill Posters]

On the issue of targeting Safari CSS…

I'd be interested to know how consistently the Safari CSS filters mentioned below perform x-platform.

CSS hacks series

Anyone able to comment/confirm/deny?

[BTreeHugger]

What do you mean by cross-platform? I have a CSS mastergrid on that blog page if you are wondering about a more thorough breakdown of what applies certain hacks. Also, the doctype they are tested for is XHTML Strict if that is what you are wondering. The last time I tested them, they were working in Safari 3 on Windows and the versions on OSX each variant of the hack is meant to work with.

[Bill Posters]

By x-platform, I simply mean how (e.g.) Safari's rendering on Win compares to that on OS X.

I've been using the dithered reference up until now in which there's no mention (or clarification) of Saf/Win. I'll definitely give your grid a proper look over at some point.
Cheers.

[BTreeHugger]

Ah, well then personally I have found that aside from some Javascript event issues (keys without codes, etc) the browsers are nearly identical. Although my experiences have been almost 100% subjective, I haven't seen any appreciable difference between OSX and Windows versions, although I haven't tried the Linux (GTK/QT) ports of WebKit yet. So far the parsers and rendering seem identical, although I haven't tested anything very low-level like antialiasing behaviour or SVG pixel-precision and such.

[websearcher]

I use DW, it inserted it for me.

[mattyod]

Does copy and paste not count as "hand coding"?