W3C home > Mailing lists > Public > www-style@w3.org > November 2002

Re: Solving problems in future specs.

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Mon, 04 Nov 2002 05:27:21 -0600
Message-ID: <3DC65999.6040108@mit.edu>
To: Tapio Markula <tapio1@gamma.nic.fi>, www-style@w3.org

Tapio Markula wrote:

> The content can be in principle an entire document or a fragment.
> BOTH cause problems.

Both are also against the spirit of CSS, which is a way of _styling_ 
documents, not of inserting arbitrary content...

> content-url-type:fragment would behave like <? require ''; ?> - the content
> would be embedded as such and the default display type would be 'inline'.

Yep.  This is the perfect example of what CSS should _not_ support, IMO. 
  If you want content processing, use a content processing tool.

> The problem is that replaced element can in principle be a phrase

How does this situation arise?  What do you mean by "phrase" in this 
context, exactly?
Received on Monday, 4 November 2002 06:27:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:17 GMT