> > I _know_ that STTS can do all this, but STTS is not going to be > > implemented in the big browsers. CSS3 on the other hand IS, so it's > > just waiting until the functionality of STTS is incorporated in > > CSS3. > > So why not just push for STTS to a CSS3 module? From my STTS author's perspective, for at least one reason : STTS is not cascading. All rules and all declarations are applied, first read first applied. A cascading transformation language using the CSS general syntax would generate a completely different solution, and IMHO dramatically complexify the whole thing. STTS does not need at all to be a CSS3 module. It will refer to some CSS3 parts/modules (selectors, syntax, error handling) and will adopt any profiling system CSS could propose in the future. I think it is enough to make a coherent system, companion of CSS, w/o co-evolution problems. </Daniel>Received on Monday, 4 October 1999 22:26:07 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:00 GMT