- From: Daniel Glazman <glazou_2000@yahoo.fr>
- Date: Tue, 8 Aug 2000 18:54:10 +0200 (CEST)
- To: webmaster@richinstyle.com, www-style@w3.org
--- Matthew Brealey <webmaster@richinstyle.com> a écrit : > BeCSS is a proposal to turn style sheets into a script dump. Matthew, I wonder how can you seriously write this comment in this mailing-list. Even if it is a surprise for you, people in the css+fp wg always think about security issues. Some people even disagree with BECSS !-) Every W3C Rec results from consensus and we don't have reached this step for the moment. BECSS does not turn CSS in a script dump. Try to see it as a new thing, that uses exactly the CSS grammar and format, and that deals only with behaviours. And that's why it is discussed in this wg. It is easy (for document providers) to agregate BECSS rules and CSS rules in a single file and that's why it has been proposed to design BECSS as a CSS 3 draft. That's a-l-l. BECSS is a proposal that tries to address a problem that dozens and dozens of people expressed during the Future of HTML Workshop, some years ago : the componentization of the Web. BECSS is *a* possible solution, maybe not *the* solution. If you think that something can be saved from the current draft, say it. If you think everything must be thrown away, say it. If you have a counter-proposal in mind, please say it *now*. But please don't say that the CSS+FP WG wants to turn CSS into a script dump. Oh, by the way, I remember to the subscribers of this mailing-list that the web would never have reached the tremendous succes we all know ***without scripts coded in the document instance***. In the real world, the best solution is not always the purest. (Tantek, do you agree with that ?-) </Daniel> ___________________________________________________________ Do You Yahoo!? Achetez, vendez! À votre prix! Sur http://encheres.yahoo.fr
Received on Tuesday, 8 August 2000 12:54:50 UTC