- From: Jason Leyba <jleyba@google.com>
- Date: Thu, 25 Jun 2015 18:07:57 +0000
- To: "public-browser-tools-testing@w3.org" <public-browser-tools-testing@w3.org>
- Message-ID: <CA+ffpBzqtLANiZssLbM6asdWyS+7377JsA2onWUsSXf21WVwDQ@mail.gmail.com>
The original OperaDriver (for Presto) can take screenshots of single elements: https://github.com/operasoftware/operaprestodriver -- Jason On Thu, Jun 25, 2015 at 10:42 AM Luke Inman-Semerau <luke.semerau@gmail.com> wrote: > I believe the intention is that we'll be doing option 1) and will be > doing so in other language bindings as well. Keep in mind, there is > not one implementation (that I know of) that is currently doing > element based screen shots. > > On Thu, Jun 25, 2015 at 10:32 AM, John Jansen <John.Jansen@microsoft.com> > wrote: > > In section 15.3 [1] it talks about taking an element Screenshot. > > > > Currently (in the C# bindings ) the RemoteWebElement class does not > implement the ITakesScreenshot interface and hence we cannot take an > element screenshot. This means we have a choice to make: > > > > 1. Should we add the interface to the RemoteWebElement and then all > other C# browser bindings will benefit from it (assuming that the > respective drivers implement it)? > > Or > > 2. Should we implement this method in the our own class (which derives > directly from RemoteWebElement)? This would not affect the bindings for the > other browsers but has some the disadvantage of forcing people who want to > use this functionality to write specific code for Edge. Generally tests > that are executed remote, use the RemoteWebElement class. > > > > What do you think? > > > > -John > > [1] https://w3c.github.io/webdriver/webdriver-spec.html#element > > > >
Received on Thursday, 25 June 2015 18:08:36 UTC