W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2014

Re: innerText spec

From: Ian Hickson <ian@hixie.ch>
Date: Wed, 17 Sep 2014 02:35:54 +0000 (UTC)
To: Ryosuke Niwa <rniwa@apple.com>
cc: Ms2ger <ms2ger@gmail.com>, Simon Pieters <simonp@opera.com>, Webapps WG <public-webapps@w3.org>
Message-ID: <alpine.DEB.2.00.1409170231440.13180@ps20323.dreamhostps.com>
On Tue, 16 Sep 2014, Ryosuke Niwa wrote:
> 
> Is either one of you working on innerText specification? 
> (http://lists.w3.org/Archives/Public/www-archive/2014Mar/0008.html)
> 
> I think we need it for the selection API specification because the 
> concept of being “visually equivalent” and selection.toString need to be 
> defined in terms of it.

Last I checked, none of the browser vendors were interested in converging 
on a single definition, so I haven't look at it in a while. It appears 
that it depends on the current style sheets, at a minimum.

Seems we've filed at least two bugs on this:

   https://www.w3.org/Bugs/Public/show_bug.cgi?id=13145
   https://www.w3.org/Bugs/Public/show_bug.cgi?id=25159

As you say, Selection.toString() depends on this; the relevant bug is in a 
similar state:

   https://www.w3.org/Bugs/Public/show_bug.cgi?id=10583

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 17 September 2014 02:36:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:26 UTC