michael.brocking...@bt.com wrote:
To my mind, that is the definition of a CSS hack - it is abuse of a
bug that is believed to only apply to the required browser(s)
Mmm. One exploits a bug to kill/fix another bug, and triggers an unknown
number of bugs in various browsers - present and future versions - in
the process. Before one knows it one has a complete bug-house :-)
There is almost never a direct correlation between the bug and the
'fix' that is being applied.
True. Not a problem if the hack is proven to only work in the
browser/version that needs the "fix", but few test and study progress in
standards and implementations in browsers well enough to make sure a
hack can't misfire and end up serving the "fix" to the wrong
browser/version.
Even many CC for IE are made "universal", and end up serving bogus fixes
to the wrong versions.
Regarding future editors: in my experience there's more of a chance that
they'll break the entire work while "tidying up", than that they'll
break just a hack or two.
regards
Georg
--
http://www.gunlaug.no
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
*******************************************************************
