- From: Simon Stewart <shs@rocketpoweredjetpants.com>
- Date: Tue, 18 Sep 2012 11:30:11 +0100
- To: Ms2ger <ms2ger@gmail.com>
- Cc: www-dom@w3.org
- Message-ID: <CAA+kcXzzhUpdjxL5hZ4SBX=MCoaebyJS_NirqBm_Kizrd+HNew@mail.gmail.com>
On Tue, Sep 18, 2012 at 11:21 AM, Ms2ger <ms2ger@gmail.com> wrote: > Hi Simon, > > > On 09/11/2012 04:25 PM, Simon Stewart wrote: > >> Hi, >> >> As part of the work we're doing on the WebDriver spec, we're attempting to >> identify properties or algorithms that may be better placed in other >> specs. >> We think that there are two obvious candidates for inclusion into future >> revisions of the DOM spec: "shown" and "shownText". >> >> The "shown" property describes whether a particular element could be made >> visible to a user. The algorithm we use to determine this is described in: >> >> http://www.w3.org/TR/**webdriver/#determining-**visibility<http://www.w3.org/TR/webdriver/#determining-visibility> >> >> The "shownText" property returns the user visible text that corresponds to >> what a user would see. The algorithm we use for this is described in: >> >> http://www.w3.org/TR/**webdriver/#rendering-text<http://www.w3.org/TR/webdriver/#rendering-text> >> > > Both of those look rather dependent on styling. As DOM is CSS-independent, > we are unlikely to specify these features in this specification. A better > place for such properties would probably be CSSOM or CSSOM View (discussed > on www-style@w3.org). > The CSSOM representative at Google suggested I present this here as textContent is described as part of the DOM spec. I'm happy to go back to that list and present the idea there, but (understandably) I'd rather not ping-pong between the two :) Simon
Received on Tuesday, 18 September 2012 10:30:39 UTC