W3C home > Mailing lists > Public > public-html@w3.org > November 2007

Re: The section element

From: James Graham <jg307@cam.ac.uk>
Date: Mon, 12 Nov 2007 17:09:27 +0000
Message-ID: <473888C7.2010709@cam.ac.uk>
To: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
CC: public-html@w3.org

Daniel Glazman wrote:
> 
> Hello guys,
> 
> With my Nvu hat on, the section element is a problem to me. It does not
> give me enough power or flexibility and requires exactly the same amount
> of JS code ol-plain-flat-html code required in the past. Let me give you
> a concrete example seen a zillion times on the web :
> 
>    <section>
>      <h4><img src="l.gif" alt="T">he raise of a new standard</h4>
>      <p>bla bla bla</p>
>    </section>
> 
> First I would like the DOM interface for section to retrieve for me the
> title of the section if any. When I say the title, I am not saying that
> the result here should be
> 
>    he raise of a new standard
> 
> I need and want
> 
>    The raise of a new standard
> 
> See what I mean ?

There was some talk at the f2f about defining a .textEquivalent DOM attribute 
which would return the textual equivalent of an element rather than just its 
.textContent.

There was also a discussion in the data tables session about whether the DOM 
should expose cell-headers relationships in an analogous manner to the 
section-headers proposal above. I guess one objection to this might be 
performance; maybe browser implementors have an opinion on this?


-- 
"Eternity's a terrible thought. I mean, where's it all going to end?"
  -- Tom Stoppard, Rosencrantz and Guildenstern are Dead
Received on Monday, 12 November 2007 17:09:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:09 GMT