Re: [CSS21] response to issue 151

* Ian Hickson wrote:
>> What really matters in practice is how markup language definitions and
>> browsers define and describe exactly how markup is mapped to CSS (in
>> reality or conceptually). This won't be easy, but to make it more
>> feasible, the logic should be as simple as possible.
>
>HTML doesn't define presentational semantics (much). If you are trying to
>say that HTML should define exact mappings of deprecated HTML
>presentational syntax into CSS, then that is an issue for the HTMLWG to
>examine, not the CSSWG.

No, the HTML specifications do not require implementations to map
language elements to CSS rules, that is a requirement for CSS
implementations and it is thus up to the CSS specification to define
this mapping (or not, in which case any implementation whatsoever is
conforming anyway in which case the requirement should not be there in
the first place). Something like the following would probably be
slightly better though.

6.4.4.

  HTML user agents must ensure that the presentional effect of 
  attributes in HTML documents as defined below can be overridden
  in user and author style sheets. They must behave as if these
  attributes are mapped to CSS rules with the same effect and a
  specifity of zero and preceded all author style sheet rules. In
  a transition phase, this policy will make it easier for HTML's
  stylistic attributes to coexist with style sheets.

  For HTML, this applies to any attribute but the following: ...

  For other languages and document formats, the interaction of language
  elements and CSS is out of scope of this specification.

  [example]

Received on Tuesday, 17 February 2004 11:27:08 UTC