Discussions of secure PHP coding. Security in software is important, so don't be afraid to ask. And when answering: be anal. Nitpick. No security vulnerability is too small.
A PHP seal? That's so... pointless. Anyone that cares if it's in PHP can probably tell.
And Safari has a lot of rendering issues and such. And, last I heard, still has no support for transparency in PNG files.
Also, one of my higher-paying clients had a Mac and refused to switch browsers from Safari so she'd see errors none of us could because we didn't have a Mac. Her monitor was very large, but her resolution was not, so she noticed EVERYTHING.
She designed the site in Photoshop herself, but wanted us to tile an image that didn't repeat, and used gradient that didn't look good in Photoshop, but she assumed we could "spice up" in HTML.
Let's just say that my experience with Safari was not a good one.
he'd see errors none of us could because we didn't have a Mac
Hardly Safari's fault. If you are a serious web firm you should really have a Mac for testing. You should probably have a Mac to work on.
Generally Safari followed the standards rigidly but doesn't implement a great of the quirks mode stuff and for that it has my respect. I work on a PC in FireFox but I test on in Safari and to date I've never needed to alter anything to work with Safari.
Basically, the site was written in tables and such, and when they got stuck, they handed it over to me. I reproduced everything in the site into proper HTML and CSS except for these tables of links because changing them would cause me to have to re-slice them out of the Photoshop document, a tedious task they weren't willing to have me spend time on.
There was one of those tables on every portfolio page (of which they had a lot), and they all caused problems in IE and Safari. The differences of tables cross-browser are part of the reason I threw away tables without a second thought once I joined DevNetwork.
Also, they had a drop down which appeared over a gradient, so either we'd use gif images, png images, or jpg images that included the background. I opted for either using gif images or simple text, but the project leader wasn't on the same wavelength as me. She wanted the anti-aliasing. I made them jpegs, and they worked in FF, but not IE. In IE, they were off by a little. I hacked a quick fix, and soon discovered that Safari did the exact same thing. We switched over to png files (which was tedious), and tried again, but it didn't give her the anti-aliasing in Safari.
When it'd be fixed in Safari, it wouldn't work in IE and vice-versa. Eventually I moved on to the next project and our other employees worked on it. It's now got tables scattered all around, all of which look horrible in IE, but perfect in Safari.
Needless to say, I no longer work for the company. :-p
At risk of further derailing the topic, I find Safari annoying because usually, the rendering is different, and I don't have easy access to Macs I can test with. >.> Plus, testing older versions is practically impossible.