RE: FRAMEBORDER attribute?

Since these questions about frames keep coming up, I think W3C should prepare an
article with the decision, an explanation and how to achieve similar results
with CSS, with samples.

If we want to move away from frames we must provide some guidance to the world
at large.

Jony

> -----Original Message-----
> From: www-html-request@w3.org [mailto:www-html-request@w3.org]On
> Behalf Of Nicolas Lesbats
> Sent: Friday, February 02, 2001 11:33 PM
> To: 'www-html@w3.org'
> Subject: RE: FRAMEBORDER attribute?
>
>
> On Fri, 2 Feb 2001, David Higgins wrote:
>
> > The *whole* reason these lists exist is to assist in the formulation of new
> > standards. To say that "frames don't exist in XHTML 1.0" does not make it
> > law, it simply means that perhaps XHTML 1.0 needs to be revised already!
>
> No, it means that W3C people spent a long, long time doing formal
> discussions about the future of this markup language. If they trash
> frames from XHTML 1.1 (frames do exist in XHTML 1.0), you shouldn't hope
> that you could have any influence on that because there are "good" reasons
> to do so.
>
> W3C allows people to discuss standards before they become
> recommandations, not to create them. If W3C decided to trash frames, never
> imagine you can change that.
>
> If authors use frames, then usual browsers will continue to implement
> them, and that's all. By the way, it is possible to avoid reload a page by
> using an OBJECT element combinating with CSS (presently it's not very well
> implemented so IFRAME can be used for training, although it's a deprecated
> element).
>
> Nicolas
>
> --
> Nicolas Lesbats - nlesbats@etu.utc.fr
> 1 rue des Capucins, Appt. 39, 60200 Compiegne
>  03 44 20 81 01
>
>
>

Received on Saturday, 3 February 2001 01:59:57 UTC