Re: Solving problems in future specs.

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 UTC