Re: css with attribues

Dmitry Turin wrote:

> But incremental rendering is already breaked by downloading
> pictures and css-file after downloading html-document itself, right?

That's why one should always explicitly specify the size of replaced 
content which has an intrinsic size.

>>> 1) values of which have visual effect (e.g. @cellspacing)

> DW> As far as possible, attributes of the second type, generally called
> DW> presentational attributes,
> 
> Maybe "attributes of first type" ?

Yes.  My mistake.


> What's about (1), sometimes it's needed to use properties as
> presentational attributes, i.e. it's needed to write:
>   <... style="presentational_attribute: value">

Although there is some controversy about this, this is also discouraged, 
because it is often used to get round the deprecation of presentational 
attributes, without actual using the deprecated attributes.  The 
controversy relates to "transclusion", the verbatim inclusion of content 
from other web pages complete with its original styling.


> And i propose to allow to specify attributes and properties
> on equal rights in tag and in css:
>   <p color="red">
>   p[color="red"] {...}

color is one of the deprecated attributes.  You should not, normally, be 
styling things based on their colour, you should be styling them based 
on the reason for the colour, so that example should be:

<p class="danger">...</p>
.danger {color: red; .....}

or more likely to be correct:

<p><strong class=danger>,,,,</strong></p>
.danger {color: red; ......}

-- 
David Woolley
Emails are not formal business letters, whatever businesses may want.
RFC1855 says there should be an address here, but, in a world of spam,
that is no longer good advice, as archive address hiding may not work.

Received on Tuesday, 15 January 2008 08:46:52 UTC