No, Safari didn’t crash on me. It’s just an attempt at a clever title.
I did, however, run across an inconvenience with Safari today. Jesse Ruderman’s Cryptogram Helper relies largely on the visual styling of input boxes to make it a useful tool. Safari doesn’t allow certain styling of input elements, however, and thus proves mostly useless when used with Jesse’s page.
I think Safari should allow styling of all input elements and simply render them according to the traditional OS X theme if no other styles are specified. Now that I think about it, I think this would qualify as a breach in CSS compliance. What’s up with that, Hyatt?
The crash part of the title comes with this classic that I’m bringing back for posterity: Audi A4 Crash.
Here’s a better solution: don’t use Safari.
Note that the CSS 2.1 candidate recommendation doesn’t require that user agents apply styles to form elements. The last paragraph of section 3.2:
CSS2.1 does not define which properties apply to form controls and frames, or how CSS can be used to style them. User agents may apply CSS properties to these elements. Authors are recommended to treat such support as experimental. A future level of CSS may specify this further.
The wording in the CSS3 Basic User Interface Module is a bit hard to interpret. It seems to suggest using the platform’s native look when the no custom properties are specified and to use CSS styling otherwise. But I’m not sure whether it’s a requirement or a suggestion. And of course it’s not set in stone yet.
Ah, thanks for the insight here. I guess my comment isn’t founded until CSS3 becomes mainstream. :)