Posted by Spartanicus on 12/30/05 17:27

Len Philpot <len@philpot.org> wrote:

>> browsers, you know the options for providing a fall back for the OS
>> component that tries to fool people into thinking that it's a web browser
>
>Are you referring to IE?

Obviously.

>> and you know how to include code.
>
>How? (see ** below, though for the conditions)

> ** That is, without scripting, SSI, etc.

Again: preprocessor, S&R, building static files locally using a
database.

>The way I see it, here's how it stands :
>
> Frames CSS
>
>Split view Yes Yes
>Static/scrolling Yes Partially *

You are blaming CSS for not providing fixed positioning, this is
nonsense, blame the OS component or provide a work around for IE using
another technology.

>Single source Yes No **

Frames using multiple source files.

>But,
>another argument in favor of frames (which I personally don't care for,
>but some users might) is that frames _can_ be made to be resizable.

If by that you mean that a user can resize a pane by dragging a border,
you can do that with CSS layouts to by using JS. But a CSS pane layout
that needs to be resized in that manner has been poorly constructed,
there should be no need for that. IIRC frames cannot be sized to scale
to the user's font setting which makes the option to drag frame borders
a necessity, fortunately CSS layouts can and should scale to the user's
font setting.

--
Spartanicus

[Back to original message]