Message-ID: <321198F1.59E2B600@uk.fnx.com> Date: Wed, 14 Aug 1996 10:14:25 +0100 From: Abigail <firstname.lastname@example.org> To: email@example.com Subject: Re: Tag Soup. Arnoud Galactus Engelfriet wrote: > > In article <firstname.lastname@example.org>, > Charles Peyton Taylor <email@example.com> wrote: > > What exactly is the resistance to having many tags? I can see > > the problem with block elements not having line breaks, and I can > > see the problems with formatting elements as opposed to content-based > > elements. > > One reason is that every browser would have to support every tag we > can think of. With classes, you can ignore them safely, or only > rely on them to look up the rendering information in the style sheet. > This strikes me as a bit absurd. If we have thingy X, and X is expressed in elements, then it will be a problem if some browsers don't handle those elements, but if X is expressed using a style sheet, then it suddenly can be ignored safely? Like, the <IMG> tag is bad because some platforms can't display inline images, but if it would be done using a style sheet, than it suddenly doesn't matter? Djee, let's find a way to express tables in CSS, and we never have to worry about non-table aware browsers anymore. The bottom line is, any browser is limited, even style sheet aware ones. You can never do something beyond the limits of a browser, not even with style sheets. As for a tag explosion, that sure is going to come with stylesheets. With stylesheets, _anyone_ can make classes, and almost anyone will. Inventing new thingies will no longer be restricted to a handful of relatively clued-in browser programmers. With style sheets, you give a dangerous tool to thousands and thousands of clueless people. Abigail -- I don't think style sheets are a good thing.