why aren't I resisting sticking my nose into this thread? Urrrgh!
> You're absolutely right...and it doesn't belong in this story because it
> isn't an issue...all of our sites worked fine with AOL BEFORE AND AFTER CF
> 4.5 so tell me where cross-platform browser compliancy enters the equation?
> You can't because it doesn't.
>
Using the same server you are, Bill, I have to differ with you on the above
statement. Lots of stuff didn't work the same for AOL clients before 4.5.
So much so that I went to the hassle of filtering for user agent on almost all
my pages and providing different scripts for AOL clients. That is a real
hassle and I normally use only the subset of html that does work cross-browser.
It's just that some things require a bit more than that subset of html.
I've found that doing the filtering and providing scripts for odd browsers
(like AOL) is the best way. I don't like doing it, but with CF it is fairly
easy.
(filter and cfinclude). My experience shows me that AOL is very broken
(for a fairly large value of 'broken') and that CF is [almost] blameless for
any problems. Go the extra distance and do the extra coding.
Identifying where and how AOL (or other browsers) is broken does allow
for code-arounds -- but CF works just fine once that is done. A lot of people
just don't take (or have) the time to robustly code for client differences, just
like a lot of people don't filter html tags in textarea inputs. It's worth doing
though.
Pan 'and lets' not mention NS & layers, IE and divs, DHMTL, CSS, etc. etc.'
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
