Re[23]: css with attribues [hardware]

David,

>> DD> A new tag doesn't require any user agents to rewrite their entire
>> DD> parse engine to mix in data from multiple souce.
>> Since engine support JS, it is 'trigger' engine, isn't it ?
DD> Not all user agents support JS
+
DD> You would also need to account for how difficult it is to implement

UAs, not supporting JS [they are not browsers, not realtime UAs :) ],
should download css before parsing html.

---

>> DD> The reduction you say will be achieved
>> DD> will be so small as to not be worthwhile.
>> Many properties are used extremely seldom;
>> and many properties, proposed to standardizations,
>> will be used extremely seldom,
>> but manufactorer of browsers spend efforts to implement them.
DD> For example? In my experience, the seldom used features are those
DD> which browser vendors tend not to implement.

Different items (independently of their nature)
have different frequency.
Seldom used properties is only right part of frequency diagram.
Vendors do not carry responsibility for this nature.

>>>>>> User gets benefit (unnecessary to keep separation in brain),
>>>> DD> As mentioned, this is a disadvantage.
>>>> Excuse me, explain, how "unnecessary to keep separation in brain"
>>>> is "disadvantage".
>> DD> I've already explained how separating presentation from content
>> DD> is an advantage. Your proposal removes that.
>> Proposal withdraw possibilities neither in HTML, nor in CSS.
>> It only present new.
DD> So maintainers have to look in more places to find out what applies
DD> to an element.

What is the "more places" ? Only tag and css. Only css is added.
This is disadvantage, important to mention !?

>> DD> CSS contains presentation. You can discard the presentation  
>> DD> without losing any meaning. Your proposal moves ...
>> Not 'moves', but 'allows to move'.
>> Nothing disturb author to write in previous manner.
DD> Initial authors perhaps, but not maintainers who have to find out
DD> where the previous author decided to put the information.

Content of elements will remain in .htm,
proposal does not give possibility of put content into css.



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 Friday, 18 January 2008 13:21:15 UTC