W3C home > Mailing lists > Public > public-html-comments@w3.org > February 2008

Re: HTML 5: The l (line) element

From: Dave Hodder <dmh@dmh.org.uk>
Date: Mon, 18 Feb 2008 22:23:19 +0000
Message-ID: <47BA0557.7020600@dmh.org.uk>
To: public-html-comments@w3.org

Frank Ellermann wrote (with snippage):
> So far I thought XHTML 2 is designed to be transformed into
> something "visible" with browsers on the side of the server,
> while HTML5 wishes to *be* this client-"visible" something.  

I don't believe XHTML 2 was ever intended to be limited to use as a 
server-side technology; it's simply much easier to use it that way today.

>> instead of "<p>Line 1<br>Line 2</p>", one would type 
>> "<p><l>Line 1</l><l>Line 2</l></p>".
> IMO not compelling, and it won't work in almost all browsers.

With the CSS provided (specifically "l { display: block }") it works in 
Firefox, Safari, Opera, Camino, SeaMonkey, etc.  With the additional 
JScript it works in Internet Explorer too.  It obviously won't work in 
the current crop of browsers that don't utilise CSS, such as Lynx.  I've 
not tried it within any NetFront-based browsers (e.g. PlayStation 3).

Whilst the use of scripting to build in HTML 5 features isn't entirely 
ideal, it's a pragmatic way of supporting current browser 
implementations rather than abandoning them when fully HTML 5-compatible 
browsers become available.

> Could <ul><li>...</li><li>...</li></ul> do what you want ?
> validator.nu accepts <ul><li> instead of <p><l> for your
> example, claiming that size="50" is invalid in HTML5.

 From a CSS point of view, yes <ul> and <li> could be used to create the 
same visual effect.  From a semantic point of view, however, it doesn't 
feel quite right -- I want to express lines within a form, and I don't 
think of them as "list items" within an unordered list.  (Thanks for 
pointing out my use of the 'size' attribute.)

> I didn't look into many proposed new features for HTML5 so
> far, maybe a <section> is not much better than <l>.  IIRC 
> XHTML 2 has no <i>, but HTML5 does.  Having <i> *and* <l>
> is not nice.

If it proves to be a problem renaming it to <line> might be a solution.


Received on Monday, 18 February 2008 22:23:31 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:26:24 UTC