like world peace. It's just a concept not a reality. I think its best
not to code for browsers _or_ web standards, but better to code for the
users.
Having a site with un-selectable text may be traced back to an issue
with how IE renders HTML, but I feel it's irresponsible that the
developers of webstandards.org would knowingly put their ideals before
the user experience.
Adam Wayne Lehman
Web Systems Developer
Johns Hopkins Bloomberg School of Public Health
Distance Education Division
-----Original Message-----
From: Jochem van Dieten [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 25, 2003 4:37 PM
To: CF-Talk
Subject: Re: Safari Issues
Adam Wayne Lehman wrote:
> Aside from the title of that two paragraph article. What is that
> supposed to mean?
It is supposed to mean that you shouldn't code for the
idiosyncracies of a browser, but for standards.
HTML is a 2 way contract: browsers may expect a website to
deliver valid HTML, website builders may expect a browser to
understand valid HTML.
> If I wrote an article on that site it would be titled 'Dear Web
> Standards: Not Being Able To Select Text Is Retarded'
>
> (as I can't seem to be able to select text in IE, but can in Safari)
You need to file a bug with Microsoft. Good luck ;-)
Jochem
--
Who needs virtual reality
if you can just dream?
- Loesje
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
