|
|
Posted by Len Philpot on 12/30/05 14:58
In article <ahu8r1d08268pmpvunbi05sjbhllv5e8a4
@news.spartanicus.utvinternet.ie>, invalid@invalid.invalid says...
> 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
Are you referring to IE?
> browser, and you know how to include code.
How? (see ** below, though for the conditions)
> What more do you need to figure out?
The way I see it, here's how it stands :
Frames CSS
Split view Yes Yes
Static/scrolling Yes Partially *
Single source Yes No **
Degrades OK Yes *** Yes
* IE doesn't support position: fixed, so that's an issue.
** That is, without scripting, SSI, etc.
*** Assuming sufficient info is included in <noframes>, which it is.
If I could fix * and **, then I see no reason to use frames. 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.
Whether I'd actually do that is questionable... :-)
I don't want this to look like I'm trying to sell frames over CSS. That
would be absurd; however, given what I want to accomplish within the
restrictions I have to operate, I've not yet been able to do it purely
with CSS. I'll still /use/ CSS though, no doubt.
--
-- Len Philpot -> len@philpot.org <--
------ ><> -----> http://philpot.org/ <--
Navigation:
[Reply to this message]
|