Safari is, by and large, a browser with pretty good standards
support. However, it has a few missing features, a few bugs, and a fair
few things that are correct according to the spec but aren’t the same
interpretation as other standards-compliant browsers. This page
discusses the first two categories of issues: things that Safari should
be doing but isn’t, or tries to do but does incorrectly. See also “Safari Surprises” for the third
category of issues that are correct, but might not be what you expected.
Safari supports most HTML 4.0 features.
labeland (as previously mentioned)
acronym. This is an important accessibility feature. It was added in later release versions and is supported, for example, by version 1.2.
max-height, as well as less-used ones like
:after, at least for text strings and picture inclusion, but not for attribute extraction using the
attr()syntax, or inclusion of arbitrary text files [test case]. However, it should be noted that Safari renders these in a different way to Mozilla-based browsers:
text-decorationon the before and after text turns it off for Safari, but not for Mozilla, because it is part of the (underlined) link.
displayproperty on before and after text] are 'none', 'inline', 'block', and 'marker'. If the value of the 'display' has any other value, the pseudo-element will behave as if the value were 'block'.”. However, setting the before and after text to have the property
display:inlinedoesn’t fix the presentation.
column-span– but to be fair, only Mozilla supports
border-collapseproperly (Windows IE provides partial support) and no browser appears to support