Don't forget the most important thing: make sure that the page is fully
standards compliant to an xhtml specification, to make it future-proof. If a
menu breaks standards-compliance but supports NS4, then I wouldn't use it...
/H.
-------------------------------------------------------------
Hugo Ahlenius E-Mail: [EMAIL PROTECTED]
Project Officer Phone: +46 8 230460
UNEP GRID-Arendal Fax: +46 8 230441
Stockholm Office Mobile: +46 733 467111
WWW: http://www.grida.no
-------------------------------------------------------------
---- Original Message ----
From: "Rick Root" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Thursday, December 18, 2003 03:24
Subject: Re: text editor for content manag. systems
| Barney Boisvert wrote:
|
|| I generally take the approach that in IE6 (about 90% of our market),
|| sites
|| should kick ass. In IE5.0, Mozilla and Safari (about 9%) it should
|| be fully
|| functional, attractive, and easy to use, but not necessarily
|| posessing _all_
|| the bells and whistles. For NS4 and everyone else, it should be
|| functional,
|| and no more. Same goes for CSS and JS. Functional with out them,
|| but if
|| it's ugly hard to use, that's perfectly acceptable.
|
| I would agree mostly with this though I don't really concern myself
| with
| the tiny TINY percentage of paranoid people who turn _javascript_ and
| cookies off.
|
| I don't go out of my way to support Netscape 4 either, for that
| matter. I just thought it was cool that the DHTML Menu Builder app
| actually
| makes DHTML menus that WORK in NS 4 =)
|
|| And to tie back to the original topic of conversation, that means
|| showing
|| NS4 users a textarea full of HTML is perfectly legit, while the IE6
|| users
|| get soEditor.
|
| Granted.. my two CMS solutions both use the non-beta version of
| htmlArea
| so if they're using IE 5.5+ for Windows, they get it, But I am
| looking
| forward to being able to tell my Mac-friendly customers that they
| don't
| have to switch computers anymore to edit their sites. =)
|
| Someone else suggested that they don't design for Netscape. That's
| fine, neither do I. But I don't design for IE either. Hell, I'm a
| programmer... I do mostly backend stuff anyway. My typical designs
| look
| something like http://fans.bobguiney.com/ =)
|
| In my department at Duke, we're gonna solve some of the
| browser-compatibility issues by building web apps in Flash MX 2004 Pro
| (thank you, MAX conference!)
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
- Re: text editor for content manag. systems Dan Farmer
- Re: text editor for content manag. systems Dan Farmer
- Re: text editor for content manag. systems Rick Root
- Re:text editor for content manag. systems Irvin Gomez
- RE: text editor for content manag. systems cf-talk
- RE: text editor for content manag. systems Barney Boisvert
- Re: text editor for content manag. syst... Rick Root
- Re: text editor for content manag.... Hugo Ahlenius
- Re: text editor for content manag.... Kevin Graeme
- RE: text editor for content manag. systems Dan Farmer
- RE: text editor for content manag. systems [EMAIL PROTECTED]