W3C home > Mailing lists > Public > www-style@w3.org > January 2008

Re[8]: css with attribues (was: Re[2]: [CSS] Would be nice if...)

From: Dmitry Turin <sql4-en@narod.ru>
Date: Mon, 14 Jan 2008 10:38:39 +0200
Message-ID: <4211419671.20080114103839@narod.ru>
To: www-style@w3.org

David,
>> DD> It also needs to implement media types
>> Strongly disagreed !
>> Now we don't assign or not assign attributes depending media types.
DD> Well, that is one way to make error checking difficult.

I don't understand, you said about:
1) errors of author of browser, or
2) errors of author of html-document

I propose, that attbitutes are considered as assigned by css
_for all media_. Clarify, how is this proposal make barrier
for debug.

>> Re-rendering during downloading.
DD> I don't understand what you are trying to say here.

  Imagine, that you adjust browser to not download pictures.
Than you download an html-document (without pictures).
Browser draw special image in each place, where picture could be.
After that, you press button "show pictures" in browser.
Browser display actual pictures instead of mentioned special images.
Size of special image and sizes of actual pictures are different.
So you see, that alignment was changed.
  Imagine, that html-document itself is downloading faster,
than its (usual) css-file. Css-file specifies, for example,
bigger size of font. During downloading (primary) html-document,
you see, that alignment was changed.
  I'm imagining changing of layout diring downloading ccas-file
(css with attributes) in similar way (let's name places in document,
where changes will happen, as 'plattr').

>> I'm sure,
>> that very small quantity of attributes will be migrated to CSS
>> (because author will specify such attributes in CSS,
>> which attributes he use in suppressing majority of documents),
DD> I don't understand what you are trying to say here.

  There exist at least two types of attributes:
1) values of which have visual effect (e.g. @cellspacing)
2) values of which change functionality (e.g. INPUT/@type)
  Attributes of first type are not differ from properties.
Attributes of second type are small part of document objects,
and they are not burden for browser.

>> DD> It is significantly more complicated then simply parsing HTML.
>> This depend of nature of browser engine - to what is it more similar:
>> to end-to-end linear transformation of html-text into screen image;
DD> Screen image? There are plenty of user agents which don't output to
DD> the screen. GoogleBot springs to mind.

I expect, that we are saying about browser.
In general case, phrase sounds
"end-to-end linear transformation of html-text into database of UA".


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 Monday, 14 January 2008 08:41:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:57 GMT