Er yeh... Same webkit rendering engine. Why does this surprise you?
I didn't say it surprises me BUT it surprises me that this bug is "brushed away" with a flick of the wrist (other browsers work) instead of being tackled - or did I miss something essential here?

Safari is not really all new PLUS it's the default browser for MAC users. So the question arises if it is wise to lock out MACs from a site by just going the "let's wait and see approach" ?