W3C home > Mailing lists > Public > www-html-editor@w3.org > October to December 2000

Many inconsistenf features in the last working draft of XHML 1.1 modularization

From: tapio1 <tapio1@nic.fi>
Date: Fri, 20 Oct 2000 18:34:04 +0300
Message-ID: <001401c03aab$2e9f8a00$88e126d4@f7n4x6>
To: <www-html-editor@w3.org>
I have found following inconsitent features. ALL inconsistencies are due that you have NOT noticed all additional modules.

'Name Identification Module'

If APPLET has 'name' as deprecated attribute, WHY 'OBJECT' doesn't have it too?

'Intrinsic Events Module'

FRAMESET doesn't have the possibility to add onload and onunload attributes.

'Legacy Module':

In addition that attribute list to the 'Legacy' module is inconsitent:

DL
WHY compact to this element doesn't belong to Legacy?

APPLET

WHY transitional attributes to this element doesn't belong to Legacy?
IF image can have with Legacy transitional attributes, WHY NOT APPLET?

The same could in principle ask concerning OBJECT, but it is not widely supported.

SELECT 
WHY align to this element doesn't belong to Legacy? SELECT is widely supported in old browsers.

LEGEND

Why it has 'align' - it is supported ONLY in NEW MS browsers - old browsers don't support it.

LEGACY module is for OLD browsers like NS 3.x or some other ONLY HTML 3.2 supporting browsers like some browsers of Sun Microsystems.
At this mean the module IS inconsistent. 

Attributes to elements, which can be added with the Legacy module should be follow HTML 3.2 
- all HTML 3.2 which are added, should be able to use ALL HTML 3.2 attributes (DL, APPLET, SELECT)
- no sense to put transitional attributes to elements, which belong only to HTML 4.0 (OBJECT, LEGEND), because HTML 4.0 capable browsers support CSS anyway (concerns primary MS IE ). IF LEGEND has transitional attributes THEN also OBJECT should have transtional attributes!

I put information about XHTML 1.1 according to 
Modularization of XHTML (W3C Working Draft4 October 2000)  with MANY question marks to following pages:

http://www.nic.fi/~tapio1/Teaching/AttributesXHTML11.html
http://www.nic.fi/~tapio1/Teaching/AttributesHTML40.html

+ notes to
http://www.nic.fi/~tapio1/Teaching/Attributes2a.html
http://www.nic.fi/~tapio1/Teaching/Attributes2b.html
http://www.nic.fi/~tapio1/Teaching/Attributes2c.html
http://www.nic.fi/~tapio1/Teaching/Attributes2d.html

The modularization is inconsistent! Could it be fixed?
Or do you want the modularization to be fully inconsitent. I just 
want that you create CONSISTENT system!
------------------------------------------------------
Tapio Markula
I like
__
____ Cascading 
______ Style
______   Sheets

I have made something also with XML and XSL
------------------------------------------------------
E:mail: tapio.markula@nic.fi
http://www.nic.fi/~tapio1/index.html (Finnish)
http://www.nic.fi/~tapio1/index_e.html (English)
http://www.nic.fi/~tapio1/Opetus/ (CSS2)
http://www.nic.fi/~tapio1/Teaching/ (CSS2)
http://www.nic.fi/~tapio1/Opetus/XSL-new.html (XML)
http://www.nic.fi/~tapio1/Teahing/XSL-new.html (XML)
------------------------------------------------------
Received on Friday, 20 October 2000 11:16:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:16:49 GMT