- From: Chris Wilson <cwilso@MICROSOFT.com>
- Date: Mon, 9 Aug 1999 09:31:30 -0700
- To: "'jelks@jelks.nu'" <jelks@jelks.nu>, "'www-style@w3.org'" <www-style@w3.org>
In discussions with the CSS WG, it was generally agreed that integrating the ideas in Action Sheets into CSS was a better idea that writing yet another format - which is why, contrary to your statement that BECSS sounds like it came straight out of Redmond, BECSS contains things like event handler definitions in CSS and embedded scripts. BECSS is a combination and improvement of Action Sheets, DHTML behaviors and HTML Components. And incidentally, of the three editors, I probably did the least work. Daniel Glazman deserves much credit for pulling all this together and making it consistent. -Chris Wilson -----Original Message----- From: Jelks Cabaniss [mailto:jelks@jelks.nu] Sent: Sunday, August 08, 1999 11:49 PM To: www-style@w3.org Subject: RE: New Working Draft : BECSS > I am *very* pleased to announce a new Working Draft : > > Behavioral Extensions to CSS > 04 Aug 1999 > http://www.w3.org/TR/becss > > Have a nice time reading it and don't forget to give > feedback !-) I am curious as to what has happened to Action Sheets. The first editor of BECSS mentioned is Vidur Apparao of Netscape (who also submitted CAS), yet BECSS reads like it popped right out of Redmond. I thought CAS a superior mechanism than using CSS style sheets to bring in scripts. What were the reasons for dropping CAS in favor of "CSS behaviors"? /Jelks
Received on Monday, 9 August 1999 12:39:12 UTC