In article <1haweuz.154bfq21p82sflN%frank_perrey@[EMAIL PROTECTED]
>,
frank_perrey@[EMAIL PROTECTED]
(Frank Perrey) wrote:
> Sander Tekelenburg <user@[EMAIL PROTECTED]
> wrote:
>
> > It is not your job to hide a browser's bugs.
>
> tell your customers and loose them.
I inform my customers. Some choose to ignore browser bugs, some pay
extra for me to hide bugs.
Btw, whether this really is Safari's mistake remains to be seen:
<http://validator.w3.org/check?uri=http://www.crowdigitalmedia.com/>
and
<http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fwww.crowdi
gitalmedia.com%2Fcss-styles.css&usermedium=all>.
> I work on Macs and HAVE to check IE6
> as well and have to face bugs there on every corner.
Yes, but Win IE can be targeted safely through conditional comments.
Also it is unlikely that IE pre-7 will ever see any further development,
but it *is* likely that Safari will. Thus in a case where Safari chokes
on some CSS, I inform the Safari team, and I tell my customer that he
*can* of course pay me to hide the buig from Safari, but it is likely
the problem will be fixed in a future version of Safari so I consider it
a waste of his money to bother trying to hide that problem. (A real
world example is the overflow: hidden on <http://www.lotzofmusic.com/>,
which used to be ignored by Safari, until one day it started respecting
it.)
--
Sander Tekelenburg, <http://www.euronet.nl/%7Etekelenb/>
|
