Re[2]: css with attribues

David,

>> But incremental rendering is already breaked by downloading
>> pictures and css-file after downloading html-document itself, right?
DW> That's why one should always explicitly specify the size of replaced
DW> content which has an intrinsic size.

But specification of size of replaced content is optional,
so browsers must (and are already capable) to work in "trigger" mode.

>>>> 1) values of which have visual effect (e.g. @cellspacing)
>>   <... style="presentational_attribute: value">
DW> verbatim inclusion of content
DW> from other web pages complete with its original styling

I'm objecting.
a) mentioned inclusion is really very seldom (at least in RuNet)
b) IFRAME makes un-necessary transformation .html+.css => .htm

All, whom i know, use <tag style="attribute: value">
for unique page and unique place in page.
It's absolutely reasonable to not bring this into css-file,
common for all pages of site.
And they say the same about people, which they know.
Thus i see, that several symbols (i.e. 'style=') is simply redundant.

>> And i propose to allow to specify attributes and properties
>> on equal rights in tag and in css:
>>   <p color="red">
>>   p[color="red"] {...}
DW> you should be styling them based on the reason for the colour
Absolutely agreed. This is only explanation of idea.
But let's return to possibility to specify attributes of similar places,
scattered on great number of pages.


Dmitry Turin
SQL5      (5.9.1)  http://sql50.euro.ru
HTML6     (6.5.1)  http://html60.euro.ru
Unicode7  (7.2.1)  http://unicode70.euro.ru
Computer2 (2.0.2)  http://computer20.euro.ru

Received on Tuesday, 15 January 2008 10:56:55 UTC