- From: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
- Date: Mon, 20 Feb 2012 08:49:41 +0100
- To: www-style@w3.org
Le 20/02/12 06:03, Charles Pritchard a écrit :
> A CSS generated and replaced content semantic, something like
> content(html) could be helpful with the <code> tag as well as
> @contentEditable.
> The idea is for innerHTML to be made visible to the user.
>
> Examples:
> <code><p>I am abusing the code tag</p></code>
> <div contentEditable><em>I know basic html</em></div>
>
> Something in CSS would it easier to flip on and off HTML source code
> examples.
>
> Something more heavy could display syntax highlighting, if it's not
> being set to a string.
> code { content: html(); }
This is, in my humble opinion, the wrong place to solve this.
in your <code> example above, you want <code> to behave like
a normal element on one hand, like a CDATA section on the other...
It's _NOT_ only a question of presentation, it's a question of
parsing.
</Daniel>
Received on Monday, 20 February 2012 07:50:11 UTC