[WEB4LIB] Re: FP2000

[Thomas Dowling]

> >
> >Do you run a Frontpage MS Server? How do you train your staff not to go
> >straight for the bright shiny non-compliant stuff in FrontPage?
> >
>
> FP2000 has a set of options that allow you to configure the editor to
restrict which functions are available by browser (e.g, only v4 browsers,
only IE browsers, etc.) and you can further control these by allowing (or
disallowing) for ASP, DHTML and other "features" within the allowed
functions.  This is terrific because, as you indicate, in the past there
was no way from stopping a person from plugging in the "marquee" feature
that is browser-specific.
>

Marvy.  IMO browser sniffing is one of the quickest routes to a bad site
full of bad, bloated pages.  It inevitably makes wrong guesses about any
browser outside the Big Two, and even for IE and NC it is typically
incapable of detecting or handling non-default configuration settings, the
most common being the assumption that all 4.x browsers have Javascript
enabled.  It's disappointing (though not surprising, of course) to see
such a widely used product encouraging this hack.

Thomas Dowling
OhioLINK - Ohio Library and Information Network
tdowling at ohiolink.edu